Kernel crash via stale CAN BCM proc pointer
Published Oct 21, 2024 · Updated May 23, 2026
Improper cleanup in the Linux CAN BCM subsystem allows local users to crash affected kernels through a crafted socket lifecycle. bcm_notify removes the socket's proc entry after its connected CAN device is unregistered but leaves bo->bcm_proc_read set, so bcm_release removes the entry again when the socket closes. Exploitation requires local low-privileged access, a CAN BCM socket connected to a device that is later unregistered, and closure without a second connect call.
Summary
What happened
Improper cleanup in the Linux CAN BCM subsystem allows local users to crash affected kernels through a crafted socket lifecycle. bcm_notify removes the socket's proc entry after its connected CAN device is unregistered but leaves bo->bcm_proc_read set, so bcm_release removes the entry again when the socket closes. Exploitation requires local low-privileged access, a CAN BCM socket connected to a device that is later unregistered, and closure without a second connect call.
The record
- CVE
- CVE-2024-47709
- Published
- Oct 21, 2024
- Updated
- May 23, 2026
- Vendor
- Siemens
- Product
- SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 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
- syzbot C and syz reproducers for WARNING in remove_proc_entryproof of concept · demonstrated
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