Kernel invalid read via dangling histogram references
Published Oct 4, 2025 · Updated Oct 4, 2025
Use-after-free in Linux kernel trace histograms allows local users to read freed kernel memory through tracefs trigger writes. The histogram setup path omits action-only variable references from hist_vars, so removal fails to detect a dependent trigger and frees state that resolve_var_refs later reads. Access requires local permission to write tracefs trigger files, and the published reproducer demonstrates a KASAN-detected invalid read in kernel context.
Summary
What happened
Use-after-free in Linux kernel trace histograms allows local users to read freed kernel memory through tracefs trigger writes. The histogram setup path omits action-only variable references from hist_vars, so removal fails to detect a dependent trigger and frees state that resolve_var_refs later reads. Access requires local permission to write tracefs trigger files, and the published reproducer demonstrates a KASAN-detected invalid read in kernel context.
The record
- CVE
- CVE-2023-53560
- Published
- Oct 4, 2025
- Updated
- Oct 4, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- 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=067fe038e70f6e64960d26a79c4df5f1413d0f13 <1576f0df7b4d1f82db588d6654b89d796fa06929
- Affected versionversion=067fe038e70f6e64960d26a79c4df5f1413d0f13 <4815359056083c555f97a5ee3af86519be5166de
- Affected versionversion=067fe038e70f6e64960d26a79c4df5f1413d0f13 <4a540f63618e525e433b37d2b5522cda08e321d7
- Affected versionversion=067fe038e70f6e64960d26a79c4df5f1413d0f13 <4ffad1528e81c91769d9da1f8436080861c8ec67
- Affected versionversion=067fe038e70f6e64960d26a79c4df5f1413d0f13 <5fd32eb6fa0ac795aa5a64bc004ab68d7b44196a
- Affected versionversion=067fe038e70f6e64960d26a79c4df5f1413d0f13 <6018b585e8c6fa7d85d4b38d9ce49a5b67be7078
- Affected versionversion=067fe038e70f6e64960d26a79c4df5f1413d0f13 <97f54b330c797ed27fba8791baeaa38ace886cbd
- Affected versionversion=4.17
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