Inconsistent BPF LRU reference state via data race
Published Dec 30, 2025 · Updated Dec 30, 2025
A race condition in the BPF LRU list in affected Linux kernel versions allows local users to produce inconsistent node reference state. Concurrent map-update and list-rotation paths access node->ref without READ_ONCE and WRITE_ONCE synchronization, allowing its value to change across the read and write. Triggering requires concurrent updates to an affected BPF per-CPU LRU hash map; published material reports a KCSAN warning and inaccurate reference state but no concrete confidentiality, integrity, or availability consequence.
Summary
What happened
A race condition in the BPF LRU list in affected Linux kernel versions allows local users to produce inconsistent node reference state. Concurrent map-update and list-rotation paths access node->ref without READ_ONCE and WRITE_ONCE synchronization, allowing its value to change across the read and write. Triggering requires concurrent updates to an affected BPF per-CPU LRU hash map; published material reports a KCSAN warning and inaccurate reference state but no concrete confidentiality, integrity, or availability consequence.
The record
- CVE
- CVE-2023-54283
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6e5e83b56f50fbd1c8f7dca7df7d72c67be25571
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6eaef1b1d8720053eb1b6e7a3ff8b2ff0716bb90
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <819ca25444b377935faa2dbb0aa3547519b5c80f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a89d14410ea0352420f03cddc67e0002dcc8f9a5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b6d9a4062c944ad095b34dc112bf646a84156f60
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c006fe361cfd947f51a56793deddf891e5cbfef8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e09a285ea1e859d4cc6cb689d8d5d7c1f7c7c0d5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ee9fd0ac3017c4313be91a220a9ac4c99dde7ad4
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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
No sourced classifications are available.
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