Kernel crash path via NULL SVA handle
Published Jul 12, 2024 · Updated May 12, 2026
Incorrect error handling in Linux 5.2 and later contains an apparent kernel NULL-dereference path in SVA device binding. The iommu_sva_bind_device() stub returns NULL when CONFIG_IOMMU_SVA is disabled, while idxd and uacce callers test only for error pointers before dereferencing the handle. The path is unreachable in practice because SVA feature enablement fails first, so no attacker-triggered crash is established.
Summary
What happened
Incorrect error handling in Linux 5.2 and later contains an apparent kernel NULL-dereference path in SVA device binding. The iommu_sva_bind_device() stub returns NULL when CONFIG_IOMMU_SVA is disabled, while idxd and uacce callers test only for error pointers before dereferencing the handle. The path is unreachable in practice because SVA feature enablement fails first, so no attacker-triggered crash is established.
The record
- CVE
- CVE-2024-40945
- Published
- Jul 12, 2024
- Updated
- May 12, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-393
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 12, 2024CVE publishedPublication date reported by the CVE source.
- May 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo