Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2024-56568 — kernel

🟡 CVSS 4.7 — Medium ✅ No Known Exploit NVD
4.7
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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]

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is high, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: None.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2024-56568 is recorded against 2 packages.

  • kernel (from 6.7.0 up to 6.12.4)
  • linux-kernel (from 6.7 up to 6.12.4)

Timeline and source

Published on 27 December 2024 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
lists.debian.org (Web)
lists.debian.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

Other advisories for this package

kernel has other advisories on record. If you are patching this one, these are worth checking on the same host:

CVE-2024-56568 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 4.7
CVSS Vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2024-12-27
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 6.7.0 6.12.4
linux-kernel 6.7 6.12.4

References

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2024-56568 is rated CVSS 4.7 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2024
✓