iommu/arm-smmu: Defer probe of clients after smmu device bound
In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu: Defer probe of clients after smmu device bound Null pointer dereference occurs due to a race between smmu driver probe and client driver probe, when of_dma_configure() for client is called after the iommu_device_register() for smmu driver probe has executed but before the driver_bound() for smmu driver has been called. Following is how the race occurs: T1:Smmu device probe T2: Client device probe really_probe() arm_smmu_device_probe() iommu_device_register() really_probe() platform_dma_configure() of_dma_configure() of_dma_configure_id() of_iommu_configure() iommu_probe_device() iommu_init_device() arm_smmu_probe_device() arm_smmu_get_by_fwnode() driver_find_device_by_fwnode() driver_find_device() next_device() klist_next() /* null ptr assigned to smmu */ /* null ptr dereference while smmu->streamid_mask */ driver_bound() klist_add_tail() When this null smmu pointer is dereferenced later in arm_smmu_probe_device, the device crashes. Fix this by deferring the probe of the client device until the smmu device has bound to the arm smmu driver. [will: Add comment]
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.231, 5.15.174, 6.1.120, 6.12.4, 6.6.66
- CVEs
- CVE-2024-56568
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 23:09 UTC · Revision 1
Source evidence
iommu/arm-smmu: Defer probe of clients after smmu device bound
core-osv · Original sourcePublished 27 Dec 2024, 14:23 UTC
In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu: Defer probe of clients after smmu device bound Null pointer dereference occurs due to a race between smmu driver probe and client driver probe, when of_dma_configure() for client is called after the iommu_device_register() for smmu driver probe has executed but before the driver_bound() for smmu driver has been called. Following is how the race occurs: T1:Smmu device probe T2: Client device probe really_probe() arm_smmu_device_probe() iommu_device_register() really_probe() platform_dma_configure() of_dma_configure() of_dma_configure_id() of_iommu_configure() iommu_probe_device() iommu_init_device() arm_smmu_probe_device() arm_smmu_get_by_fwnode() driver_find_device_by_fwnode() driver_find_device() next_device() klist_next() /* null ptr assigned to smmu */ /* null ptr dereference while smmu->streamid_mask */ driver_bound() klist_add_tail() When this null smmu pointer is dereferenced later in arm_smmu_probe_device, the device crashes. Fix this by deferring the probe of the client device until the smmu device has bound to the arm smmu driver. [will: Add comment]
osv:CVE-2024-56568
Kernel
Fixed versions: 5.10.231, 5.15.174, 6.1.120, 6.6.66, 6.12.4
Complete source record
{
"id": "aaf9416f1767f053794971701228558d1769f8d37d3c24253190ff24aacbafb7",
"url": "https://osv.dev/vulnerability/CVE-2024-56568",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "iommu/arm-smmu: Defer probe of clients after smmu device bound",
"summary": "In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu: Defer probe of clients after smmu device bound Null pointer dereference occurs due to a race between smmu driver probe and client driver probe, when of_dma_configure() for client is called after the iommu_device_register() for smmu driver probe has executed but before the driver_bound() for smmu driver has been called. Following is how the race occurs: T1:Smmu device probe T2: Client device probe really_probe() arm_smmu_device_probe() iommu_device_register() really_probe() platform_dma_configure() of_dma_configure() of_dma_configure_id() of_iommu_configure() iommu_probe_device() iommu_init_device() arm_smmu_probe_device() arm_smmu_get_by_fwnode() driver_find_device_by_fwnode() driver_find_device() next_device() klist_next() /* null ptr assigned to smmu */ /* null ptr dereference while smmu->streamid_mask */ driver_bound() klist_add_tail() When this null smmu pointer is dereferenced later in arm_smmu_probe_device, the device crashes. Fix this by deferring the probe of the client device until the smmu device has bound to the arm smmu driver. [will: Add comment]",
"evidence": "osv:CVE-2024-56568",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.231",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.174",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.120",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.66",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.4",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "CVE-2024-56568",
"aliases": [
"CVE-2024-56568"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "021bb8420d44cf56102d44fca9af628625e75482"
},
{
"fixed": "c2527d07c7e9cda2c6165d5edccf74752baac1b0"
},
{
"fixed": "dc02407ea952e20c544a078a6be2e6f008327973"
},
{
"fixed": "f8f794f387ad21c4696e5cd0626cb6f8a5f6aea5"
},
{
"fixed": "4a9485918a042e3114890dfbe19839a1897f8b2c"
},
{
"fixed": "5018696b19bc6c021e934a8a59f4b1dd8c0ac9f8"
},
{
"fixed": "229e6ee43d2a160a1592b83aad620d6027084aad"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-56568.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.9.0"
},
{
"fixed": "5.10.231"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.174"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.120"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.66"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.4"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-56568.json"
}
}
],
"modified": "2026-10-28T02:30:40.433337763Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/229e6ee43d2a160a1592b83aad620d6027084aad",
"https://git.kernel.org/stable/c/4a9485918a042e3114890dfbe19839a1897f8b2c",
"https://git.kernel.org/stable/c/5018696b19bc6c021e934a8a59f4b1dd8c0ac9f8",
"https://git.kernel.org/stable/c/c2527d07c7e9cda2c6165d5edccf74752baac1b0",
"https://git.kernel.org/stable/c/dc02407ea952e20c544a078a6be2e6f008327973",
"https://git.kernel.org/stable/c/f8f794f387ad21c4696e5cd0626cb6f8a5f6aea5",
"https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html",
"https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/56xxx/CVE-2024-56568.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-56568",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/56xxx/CVE-2024-56568.json"
}
},
"related_cves": [
{
"value": "CVE-2024-56568",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 507869,
"published_at": "2024-12-27T14:23:11.733+00:00"
}