Local kernel crash via bonding XFRM race
Published Sep 4, 2024 · Updated May 12, 2026
NULL pointer dereference in Linux kernel bonding allows local users to crash affected Linux and Siemens device kernels through XFRM traffic. Bonding code clears a slave's real_dev while packets remain in transit, allowing xdo_dev_offload_ok() to invoke a callback that dereferences the null device pointer. Exploitation requires low-privileged local access and a race between bond slave changes and in-transit XFRM processing; the bounded consequence is a kernel crash.
Summary
What happened
NULL pointer dereference in Linux kernel bonding allows local users to crash affected Linux and Siemens device kernels through XFRM traffic. Bonding code clears a slave's real_dev while packets remain in transit, allowing xdo_dev_offload_ok() to invoke a callback that dereferences the null device pointer. Exploitation requires low-privileged local access and a race between bond slave changes and in-transit XFRM processing; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2024-44989
- Published
- Sep 4, 2024
- Updated
- May 12, 2026
- Vendor
- Siemens
- Product
- SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 4, 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 <V3.2
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