CVE-2026-90187null_blk: free zones array on device power-off
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: null_blk: free zones array on device power-off null_init_zoned_dev() allocates dev->zones when a zoned device is powered on, but null_del_dev() never frees it on power-off; dev->zones is only freed later in null_free_dev(), when the configfs directory is removed. If the device is powered off and then on again, null_init_zoned_dev() allocates a new array and overwrites the dev->zones pointer, leaking the previous allocation each power cycle. Free dev->zones in null_del_dev() via null_free_zoned_dev() to solve it. And calling null_free_zoned_dev() in null_free_dev() is no longer necessary because every caller already invokes null_del_dev() first: via nullb_group_drop_item() before nullb_device_release(), in the null_add_dev() error path of null_create_dev(), and in null_destroy_dev(). Remove the redundant call. And take &lock around zone_cond_store() in the two store wrappers to serialize dev->zones check-and-deref against its alloc/free, which already run under &lock. The reason there was no problem before is that only nullb_device_release() or null_exit() frees the dev->zones, which guarantees that subsequent users won't access the configfs interface.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 43 days later
· 43 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected ca4b2a011948fae4e4d31490107db4926385a983 – < 26d21585caa61c30d0f3044a1e6d172456148c9f
- affected ca4b2a011948fae4e4d31490107db4926385a983 – < 08a31a2cc3d1cea67ccd292d01511cd0a72d4656
- affected ca4b2a011948fae4e4d31490107db4926385a983 – < 056be41932c95aabdb3c2967d1ef4978f17a0225
- affected ca4b2a011948fae4e4d31490107db4926385a983 – < b2437d37fcc31fce8a5da1cc1739e284814d2491
- affected ca4b2a011948fae4e4d31490107db4926385a983 – < 0a3afab87124171022fb3579502fa38ef5b311c9
- affected ca4b2a011948fae4e4d31490107db4926385a983 – < 2a6357a9b935a34f5508618fee8a7fffbf7722a8
- affected 4.19
- unaffected < 4.19
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/26d21585caa61c30d0f3044a1e6d172456148c9f (opens in a new tab)
- https://git.kernel.org/stable/c/08a31a2cc3d1cea67ccd292d01511cd0a72d4656 (opens in a new tab)
- https://git.kernel.org/stable/c/056be41932c95aabdb3c2967d1ef4978f17a0225 (opens in a new tab)
- https://git.kernel.org/stable/c/b2437d37fcc31fce8a5da1cc1739e284814d2491 (opens in a new tab)
- https://git.kernel.org/stable/c/0a3afab87124171022fb3579502fa38ef5b311c9 (opens in a new tab)
- https://git.kernel.org/stable/c/2a6357a9b935a34f5508618fee8a7fffbf7722a8 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-81780 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90187)Record last updated .