Kernel memory disclosure via stale BCM procfs entry
Published Nov 28, 2024 · Updated Aug 5, 2026
Use-after-free in the CAN BCM subsystem in affected Linux kernels allows local users to read freed memory through a procfs race. bcm_release() frees a bcm_op object before removing its procfs entry, so a concurrent bcm_proc_show() call dereferences the stale object. Local users must create a CAN BCM operation and race socket closure against reading its procfs entry, exposing reclaimed kernel data and risking a kernel crash.
Summary
What happened
Use-after-free in the CAN BCM subsystem in affected Linux kernels allows local users to read freed memory through a procfs race. bcm_release() frees a bcm_op object before removing its procfs entry, so a concurrent bcm_proc_show() call dereferences the stale object. Local users must create a CAN BCM operation and race socket closure against reading its procfs entry, exposing reclaimed kernel data and risking a kernel crash.
The record
- CVE
- CVE-2023-52922
- Published
- Nov 28, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 28, 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 <11b8e27ed448baa385d90154a141466bd5e92f18
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <3c3941bb1eb53abe7d640ffee5c4d6b559829ab3
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <55c3b96074f3f9b0aee19bf93cd71af7516582bb
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <9533dbfac0ff7edd77a5fa2c24974b1d66c8b0a6
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <995f47d76647708ec26c6e388663ad4f3f264787
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <9b58d36d0c1ea29a9571e0222a9c29df0ccfb7ff
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <cf254b4f68e480e73dab055014e002b77aed30ed
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <dfd0aa26e9a07f2ce546ccf8304ead6a2914e8a7
What conditions does exploitation require?
What is affected?
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.
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