Kernel memory corruption via stale DAMON call control
Published Jan 25, 2026 · Updated Jan 25, 2026
Use-after-free in Linux Kernel 6.17 allows local users with DAMON sysfs write permission to corrupt kernel memory through crafted writes. The damon_call() error path leaves a damon_call_control linked to an inactive context, so a later request traverses a freed list entry. Root-owned 0600 sysfs permissions normally restrict the trigger to uid 0, bounding exposure to privileged local contexts.
Summary
What happened
Use-after-free in Linux Kernel 6.17 allows local users with DAMON sysfs write permission to corrupt kernel memory through crafted writes. The damon_call() error path leaves a damon_call_control linked to an inactive context, so a later request traverses a freed list entry. Root-owned 0600 sysfs permissions normally restrict the trigger to uid 0, bounding exposure to privileged local contexts.
The record
- CVE
- CVE-2026-23012
- Published
- Jan 25, 2026
- Updated
- Jan 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 25, 2026CVE publishedPublication date reported by the CVE source.
- Jan 25, 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=004ded6bee11b8ed463cdc54b89a4390f4b64f6d <23b061f421eef03647b512f3df48861706c87db3
- Affected versionversion=004ded6bee11b8ed463cdc54b89a4390f4b64f6d <f9132fbc2e83baf2c45a77043672a63a675c9394
- Affected versionversion=6.17
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.
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