Service interruption via leaked CAN BCM proc entries
Published Sep 18, 2024 · Updated Aug 5, 2026
Resource exhaustion in affected Linux kernel releases allows local users to interrupt service through crafted CAN BCM socket operations. bcm_notify() clears the socket's bound flag when its network device is removed, so a second bcm_connect() duplicates the proc name, clears bcm_proc_read, and leaks the original entry. Exploitation requires local low-privileged access and control of the CAN device-and-connect sequence; repetition consumes kernel resources and interrupts service.
Summary
What happened
Resource exhaustion in affected Linux kernel releases allows local users to interrupt service through crafted CAN BCM socket operations. bcm_notify() clears the socket's bound flag when its network device is removed, so a second bcm_connect() duplicates the proc name, clears bcm_proc_read, and leaks the original entry. Exploitation requires local low-privileged access and control of the CAN device-and-connect sequence; repetition consumes kernel resources and interrupts service.
The record
- CVE
- CVE-2024-46771
- Published
- Sep 18, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=2.6.25
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <10bfacbd5e8d821011d857bee73310457c9c989a
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <33ed4ba73caae39f34ab874ba79138badc2c65dd
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <3b39dc2901aa7a679a5ca981a3de9f8d5658afe8
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <4377b79323df62eb5d310354f19b4d130ff58d50
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <5c680022c4e28ba18ea500f3e29f0428271afa92
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <76fe372ccb81b0c89b6cd2fec26e2f38c958be85
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <abb0a615569ec008e8a93d9f3ab2d5b418ea94d4
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <aec92dbebdbec7567d9f56d7c9296a572b8fd849
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