CVE-2026-90185
CVE CVE-2026-90185EUVD EUVD-2026-81778Published 2026-09-17T16:07:08.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 45919fbfe1c487c17ea1d198534339a5e8abeae3 <65cae82fd3c39b53430672cb9e3ecd267471a6ce; 45919fbfe1c487c17ea1d198534339a5e8abeae3 <7e7fff51808237703a3a1df6dd5cae1dfd1db86d; 45919fbfe1c487c17ea1d198534339a5e8abeae3 <88d806d0e1d36246208386a8e55b511c1b3d647c; patch: 6.12.110; patch: 6.1.188; 45919fbfe1c487c17ea1d198534339a5e8abeae3 <c70994c2862b05e44728912b2ea9487d31e2aea7; patch: 6.18.52; 45919fbfe1c487c17ea1d198534339a5e8abeae3 <3945ce8cbce4e328e6fdf0b522dc71e340de19db; 45919fbfe1c487c17ea1d198534339a5e8abeae3 <8e839ed5210399a0330a8a6c5885c1d40a537c6d; patch: 0; patch: 7.2.6; 5.5; patch: 7.3-rc1; patch: 6.6.157
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.