Kernel warning via tracing_map write reordering
Published Mar 26, 2024 · Updated May 11, 2026
Race condition in the Linux kernel tracing_map implementation allows local users to trigger duplicate histogram entries and a kernel warning. In __tracing_map_insert(), the key copy and entry pointer publication can become visible in reverse order on another CPU, so a concurrent lookup compares an incompletely published key and inserts a duplicate. Reproduction requires writable tracefs controls and concurrent workload execution on a multiprocessor AArch64 system; the demonstrated consequence is a kernel warning.
Summary
What happened
Race condition in the Linux kernel tracing_map implementation allows local users to trigger duplicate histogram entries and a kernel warning. In __tracing_map_insert(), the key copy and entry pointer publication can become visible in reverse order on another CPU, so a concurrent lookup compares an incompletely published key and inserts a duplicate. Reproduction requires writable tracefs controls and concurrent workload execution on a multiprocessor AArch64 system; the demonstrated consequence is a kernel warning.
The record
- CVE
- CVE-2024-26645
- Published
- Mar 26, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 26, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=4.17
- Affected versionversion=c193707dde77ace92a649cd59a17e105e2fbeaef <2b44760609e9eaafc9d234a6883d042fc21132a7
- Affected versionversion=c193707dde77ace92a649cd59a17e105e2fbeaef <5022b331c041e8c54b9a6a3251579bd1e8c0fc0b
- Affected versionversion=c193707dde77ace92a649cd59a17e105e2fbeaef <a1eebe76e187dbe11ca299f8dbb6e45d5b1889e7
- Affected versionversion=c193707dde77ace92a649cd59a17e105e2fbeaef <aef1cb00856ccfd614467cfb50b791278992e177
- Affected versionversion=c193707dde77ace92a649cd59a17e105e2fbeaef <bf4aeff7da85c3becd39fb73bac94122331c30fb
- Affected versionversion=c193707dde77ace92a649cd59a17e105e2fbeaef <dad9b28f675ed99b4dec261db2a397efeb80b74c
- Affected versionversion=c193707dde77ace92a649cd59a17e105e2fbeaef <ef70dfa0b1e5084f32635156c9a5c795352ad860
- Affected versionversion=c193707dde77ace92a649cd59a17e105e2fbeaef <f4f7e696db0274ff560482cc52eddbf0551d4b7a
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