null_blk: serialize configfs attribute stores with the lock
Summary
| CVE | CVE-2026-90185 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-17 17:17:12 UTC |
| Updated | 2026-10-19 09:19:08 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 45919fbfe1c487c17ea1d198534339a5e8abeae3 8e839ed5210399a0330a8a6c5885c1d40a537c6d git |
Not specified |
| CNA |
Linux |
Linux |
affected 45919fbfe1c487c17ea1d198534339a5e8abeae3 88d806d0e1d36246208386a8e55b511c1b3d647c git |
Not specified |
| CNA |
Linux |
Linux |
affected 45919fbfe1c487c17ea1d198534339a5e8abeae3 3945ce8cbce4e328e6fdf0b522dc71e340de19db git |
Not specified |
| CNA |
Linux |
Linux |
affected 45919fbfe1c487c17ea1d198534339a5e8abeae3 65cae82fd3c39b53430672cb9e3ecd267471a6ce git |
Not specified |
| CNA |
Linux |
Linux |
affected 45919fbfe1c487c17ea1d198534339a5e8abeae3 c70994c2862b05e44728912b2ea9487d31e2aea7 git |
Not specified |
| CNA |
Linux |
Linux |
affected 45919fbfe1c487c17ea1d198534339a5e8abeae3 7e7fff51808237703a3a1df6dd5cae1dfd1db86d git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.5 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.5 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.188 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.157 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.110 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.52 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.6 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/88d806d0e1d36246208386a8e55b511c1b3d647c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/65cae82fd3c39b53430672cb9e3ecd267471a6ce |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/3945ce8cbce4e328e6fdf0b522dc71e340de19db |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/7e7fff51808237703a3a1df6dd5cae1dfd1db86d |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/8e839ed5210399a0330a8a6c5885c1d40a537c6d |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/c70994c2862b05e44728912b2ea9487d31e2aea7 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.