CVE-2024-56568
iommu/arm-smmu: Defer probe of clients after smmu device bound
We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
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]
Reserved 2024-12-27 | Published 2024-12-27 | Updated 2025-01-20 | Assigner Linuxgit.kernel.org/...c/c2527d07c7e9cda2c6165d5edccf74752baac1b0
git.kernel.org/...c/dc02407ea952e20c544a078a6be2e6f008327973
git.kernel.org/...c/f8f794f387ad21c4696e5cd0626cb6f8a5f6aea5
git.kernel.org/...c/4a9485918a042e3114890dfbe19839a1897f8b2c
git.kernel.org/...c/5018696b19bc6c021e934a8a59f4b1dd8c0ac9f8
git.kernel.org/...c/229e6ee43d2a160a1592b83aad620d6027084aad
Support options
