Interface-scope bypass via torn socket binding reads
Published Aug 15, 2026 · Updated Aug 15, 2026
Race condition in Linux kernel CAN BCM since 2.6.25 allows local users to bypass interface scoping or disrupt receive operations. In bcm_sendmsg(), bo->bound and bo->ifindex are read before lock_sock() while concurrent notification, connect, and release paths update both under the lock. A local user sharing the socket or racing CAN-device removal can produce a torn binding that matches any interface, while bcm_rx_setup() can leave a broken receive operation registered after device loss.
Summary
What happened
Race condition in Linux kernel CAN BCM since 2.6.25 allows local users to bypass interface scoping or disrupt receive operations. In bcm_sendmsg(), bo->bound and bo->ifindex are read before lock_sock() while concurrent notification, connect, and release paths update both under the lock. A local user sharing the socket or racing CAN-device removal can produce a torn binding that matches any interface, while bcm_rx_setup() can leave a broken receive operation registered after device loss.
The record
- CVE
- CVE-2026-72122
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-367
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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 <0f6f9f95294b4cbb26ba02209e893e3bd91237c3
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <35f0ac19efb1a3f6c5e12c00e475a9ec2d9c3a6d
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <6bcc5cd247c2934373bc2a1cdf8bf12321169543
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <9e60c586faeaed80d55ab8ce2a4b8e56133bc395
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <b70f1a15533afeeec5d07f20bec3f3867ab1c7b6
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <b9c6ac6fb4e01b34575816066e5d3890a57b3c86
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <d9b091d9d22fee81ec53fb55d2032951993ceadb
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <ffa80a2af27c97453861a5128e537214a31cd18a
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