CVE-2026-90185null_blk: serialize configfs attribute stores with the lock
- —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: serialize configfs attribute stores with the lock The NULLB_DEVICE_ATTR _store takes no lock: apply_fn attributes (submit_queues, poll_queues) get dev->NAME written again after apply_fn returns, outside its lock; APPLY=NULL attributes are entirely lockless. configfs only serializes stores per-open-file, so concurrent stores on separate fds race. For apply_fn attributes, once one store's apply_fn has reconfigured the hardware, a second (losing) store can still overwrite dev->NAME afterwards. This leaves dev->submit_queues out of sync with the live queue count, which is later caught by the WARN_ON_ONCE() in null_map_queues(). For !apply_fn attributes, power_store()'s null_add_dev() validates and builds the device under "lock" but only sets CONFIGURED afterwards. A store slipping in during this window can change a field mid-setup -- for example, zone_nr_conv can be pushed above nr_zones after it has already been clamped, leading to an out-of-bounds dev->zones[] access. Take "lock" in the macro around the apply_fn call, the CONFIGURED test and the field write, and move it out of nullb_apply_submit_queues()/ nullb_apply_poll_queues() so both paths are covered once. This serializes stores with power_store's setup and with each other.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 32 days later
· 32 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 45919fbfe1c487c17ea1d198534339a5e8abeae3 – < 8e839ed5210399a0330a8a6c5885c1d40a537c6d
- affected 45919fbfe1c487c17ea1d198534339a5e8abeae3 – < 88d806d0e1d36246208386a8e55b511c1b3d647c
- affected 45919fbfe1c487c17ea1d198534339a5e8abeae3 – < 3945ce8cbce4e328e6fdf0b522dc71e340de19db
- affected 45919fbfe1c487c17ea1d198534339a5e8abeae3 – < 65cae82fd3c39b53430672cb9e3ecd267471a6ce
- affected 45919fbfe1c487c17ea1d198534339a5e8abeae3 – < c70994c2862b05e44728912b2ea9487d31e2aea7
- affected 45919fbfe1c487c17ea1d198534339a5e8abeae3 – < 7e7fff51808237703a3a1df6dd5cae1dfd1db86d
- affected 5.5
- unaffected < 5.5
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 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/8e839ed5210399a0330a8a6c5885c1d40a537c6d (opens in a new tab)
- https://git.kernel.org/stable/c/88d806d0e1d36246208386a8e55b511c1b3d647c (opens in a new tab)
- https://git.kernel.org/stable/c/3945ce8cbce4e328e6fdf0b522dc71e340de19db (opens in a new tab)
- https://git.kernel.org/stable/c/65cae82fd3c39b53430672cb9e3ecd267471a6ce (opens in a new tab)
- https://git.kernel.org/stable/c/c70994c2862b05e44728912b2ea9487d31e2aea7 (opens in a new tab)
- https://git.kernel.org/stable/c/7e7fff51808237703a3a1df6dd5cae1dfd1db86d (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-81778 (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-90185)Record last updated .