Kernel-memory disclosure via uninitialized discard payload
Published Sep 11, 2026 · Updated Sep 11, 2026
Information disclosure in the Linux NVMe host driver allows attackers to send uninitialized kernel memory to a controller through a discard request. nvme_setup_discard() maps a 4,096-byte DSM payload but initializes only the declared ranges after its atomic allocation fails because the per-controller fallback page is allocated without zeroing. Triggering the leak requires local discard activity during memory pressure, and the exposed tail can contain prior kernel-page data such as vmemmap pointers.
Summary
What happened
Information disclosure in the Linux NVMe host driver allows attackers to send uninitialized kernel memory to a controller through a discard request. nvme_setup_discard() maps a 4,096-byte DSM payload but initializes only the declared ranges after its atomic allocation fails because the per-controller fallback page is allocated without zeroing. Triggering the leak requires local discard activity during memory pressure, and the exposed tail can contain prior kernel-page data such as vmemmap pointers.
The record
- CVE
- CVE-2026-89483
- Published
- Sep 11, 2026
- Updated
- Sep 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 11, 2026CVE publishedPublication date reported by the CVE source.
- Sep 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.19.92 <4.20
- Affected versionversion=530436c45ef2e446c12538a400e465929a0b3ade <67551d8430df94c827e1830bd3a5fae1f66a5219
- Affected versionversion=530436c45ef2e446c12538a400e465929a0b3ade <bededeaaeff404978a5a8e2a605a6c3017cddd3e
- Affected versionversion=530436c45ef2e446c12538a400e465929a0b3ade <dc4d4b70a863f7e39ef8bd137634be4e6db8b084
- Affected versionversion=530436c45ef2e446c12538a400e465929a0b3ade <f5827817b4fc7feeabf4f53fb4b626e6edc52fef
- Affected versionversion=5.4.7 <5.5
- Affected versionversion=5.5
- Affected versionversion=8b0acb768a06083b0d28bace1481c1f6679e76f4
- Affected versionversion=ffa56cbdd2409b522b4cb56461bea1c45889417b
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
- KMSAN fault-injection reproduction procedureproof of concept · demonstrated
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