Kernel memory exhaustion via histogram reference leak
Published Sep 25, 2026 · Updated Sep 25, 2026
Memory leak in Linux kernel tracing allows local users to consume kernel memory by repeatedly removing crafted histogram triggers. The shared var_refs array owns each reference once, but __destroy_hist_field() decrements a count raised for every reuse and leaves objects allocated after three or more references. Writing tracefs trigger files requires elevated local privileges; repeated trigger creation and removal exhausts memory and interrupts service.
Summary
What happened
Memory leak in Linux kernel tracing allows local users to consume kernel memory by repeatedly removing crafted histogram triggers. The shared var_refs array owns each reference once, but __destroy_hist_field() decrements a count raised for every reuse and leaves objects allocated after three or more references. Writing tracefs trigger files requires elevated local privileges; repeated trigger creation and removal exhausts memory and interrupts service.
The record
- CVE
- CVE-2026-97922
- Published
- Sep 25, 2026
- Updated
- Sep 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 25, 2026CVE publishedPublication date reported by the CVE source.
- Sep 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=4.19.100 <4.20
- Affected versionversion=5.4.16 <5.5
- Affected versionversion=5.5
- Affected versionversion=8bcebc77e85f3d7536f96845a0fe94b1dddb6af0 <4bddcb346a6cf4615ca77f69a589623b877ca267
- Affected versionversion=8bcebc77e85f3d7536f96845a0fe94b1dddb6af0 <4cff53bb19412c6f2d90b50678de5c3903f7f96a
- Affected versionversion=8bcebc77e85f3d7536f96845a0fe94b1dddb6af0 <94bbd65da4ae26592fa1977a74ee94218ab02a26
- Affected versionversion=8bcebc77e85f3d7536f96845a0fe94b1dddb6af0 <e7b6d67b43caee9183a4374d23641578ea556e6c
- Affected versionversion=bf470f051556b610265ea02ad2102de75e8e619c
- Affected versionversion=ce28d664054df01997baace61d1defca77689798
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started