Memory leakage via unreleased zone arrays
Published Sep 17, 2026 · Updated Sep 17, 2026
Memory leakage in Linux kernel null_blk allows local users to consume kernel memory by repeatedly cycling zoned-device power. null_del_dev() leaves dev->zones allocated on power-off, and null_init_zoned_dev() overwrites its pointer on the next power-on, losing the previous allocation. Triggering the leak requires privileged access to a zoned device's configfs power control; the disclosed consequence is cumulative kernel memory consumption, not a demonstrated crash.
Summary
What happened
Memory leakage in Linux kernel null_blk allows local users to consume kernel memory by repeatedly cycling zoned-device power. null_del_dev() leaves dev->zones allocated on power-off, and null_init_zoned_dev() overwrites its pointer on the next power-on, losing the previous allocation. Triggering the leak requires privileged access to a zoned device's configfs power control; the disclosed consequence is cumulative kernel memory consumption, not a demonstrated crash.
The record
- CVE
- CVE-2026-90187
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started