Kernel crash via undersized BTT lane arrays
Published Sep 16, 2026 · Updated Sep 16, 2026
Out-of-bounds write in the Linux kernel BTT driver allows local users to crash the kernel via a crafted or foreign BTT arena. The driver sizes freelist and read-tracking arrays from the unvalidated on-media nfree field, then indexes them with a lane value bounded by a larger region lane count. Reaching the overwrite requires local control of BTT arena metadata and BTT I/O; the demonstrated consequence is a kernel panic.
Summary
What happened
Out-of-bounds write in the Linux kernel BTT driver allows local users to crash the kernel via a crafted or foreign BTT arena. The driver sizes freelist and read-tracking arrays from the unvalidated on-media nfree field, then indexes them with a lane value bounded by a larger region lane count. Reaching the overwrite requires local control of BTT arena metadata and BTT I/O; the demonstrated consequence is a kernel panic.
The record
- CVE
- CVE-2026-89965
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 16, 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.2
- Affected versionversion=5212e11fde4d40fa627668b4f2222d20db488f71 <59d5cd1f42b4bab3609512c3cb3d3540d3d21da7
- Affected versionversion=5212e11fde4d40fa627668b4f2222d20db488f71 <6a1f2e5ed9267ca19187038ac635393c165213ac
- Affected versionversion=5212e11fde4d40fa627668b4f2222d20db488f71 <6b1faf1f099f7060b5f1f2f0d024132581f1726e
- Affected versionversion=5212e11fde4d40fa627668b4f2222d20db488f71 <6f79d1a5f2611a3d36e9312be5425cd9cb397c51
- Affected versionversion=5212e11fde4d40fa627668b4f2222d20db488f71 <9dfa11cef4750b67591307f2c62e47a23d60e4b7
- Affected versionversion=5212e11fde4d40fa627668b4f2222d20db488f71 <eb491343d2d1784121ad9af91c25b338c28913c3
- Affected versionversion=5212e11fde4d40fa627668b4f2222d20db488f71 <f6c5313aae794ecca8f762c1a3493de5c266f120
- Affected versionversion=5212e11fde4d40fa627668b4f2222d20db488f71 <f9bf05c63b77d000e9c01f3e47af36973887d350
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