Kernel crash via unsynchronized ring-buffer teardown
Published Oct 4, 2025 · Updated Oct 4, 2025
Use-after-free in the Linux kernel ring buffer from 3.10 allows local users to crash the kernel during buffer teardown. The teardown path in kernel/trace/ring_buffer.c frees per-CPU buffers without synchronizing pending IRQ work, which later reads freed memory. Triggering requires data to be written immediately before destruction and winning the IRQ-work race; the CNA reproduced it under User-Mode Linux time-travel and did not establish practical exploitation on a conventional system.
Summary
What happened
Use-after-free in the Linux kernel ring buffer from 3.10 allows local users to crash the kernel during buffer teardown. The teardown path in kernel/trace/ring_buffer.c frees per-CPU buffers without synchronizing pending IRQ work, which later reads freed memory. Triggering requires data to be written immediately before destruction and winning the IRQ-work race; the CNA reproduced it under User-Mode Linux time-travel and did not establish practical exploitation on a conventional system.
The record
- CVE
- CVE-2023-53587
- Published
- Oct 4, 2025
- Updated
- Oct 4, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 2025CVE publishedPublication date reported by the CVE source.
- Oct 4, 2025Record 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=15693458c4bc0693fd63a50d60f35b628fcf4e29 <0a65165bd24ee9231191597b7c232376fcd70cdb
- Affected versionversion=15693458c4bc0693fd63a50d60f35b628fcf4e29 <1c99f65d6af2a454bfd5207b4f6a97c8474a1191
- Affected versionversion=15693458c4bc0693fd63a50d60f35b628fcf4e29 <2399b1fda025e939b6fb1ac94505bcf718534e65
- Affected versionversion=15693458c4bc0693fd63a50d60f35b628fcf4e29 <2702b67f59d455072a08dc40312f9b090d4dec04
- Affected versionversion=15693458c4bc0693fd63a50d60f35b628fcf4e29 <372c5ee537b8366b64b691ba29e9335525e1655e
- Affected versionversion=15693458c4bc0693fd63a50d60f35b628fcf4e29 <675751bb20634f981498c7d66161584080cc061e
- Affected versionversion=15693458c4bc0693fd63a50d60f35b628fcf4e29 <c63741e872fcfb10e153517750f7908f0c00f60d
- Affected versionversion=15693458c4bc0693fd63a50d60f35b628fcf4e29 <d9834abd8b24d1fe8092859e436fe1e0fd467c61
- Affected versionversion=15693458c4bc0693fd63a50d60f35b628fcf4e29 <fc6858b7f8e1221f62ce8c6ff8a13a349c32cd76
- Affected versionversion=3.10
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