CVE-2026-23148nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference There is a race condition in nvmet_bio_done() that can cause a NULL pointer dereference in blk_cgroup_bio_start(): 1. nvmet_bio_done() is called when a bio completes 2. nvmet_req_complete() is called, which invokes req->ops->queue_response(req) 3. The queue_response callback can re-queue and re-submit the same request 4. The re-submission reuses the same inline_bio from nvmet_req 5. Meanwhile, nvmet_req_bio_put() (called after nvmet_req_complete) invokes bio_uninit() for inline_bio, which sets bio->bi_blkg to NULL 6. The re-submitted bio enters submit_bio_noacct_nocheck() 7. blk_cgroup_bio_start() dereferences bio->bi_blkg, causing a crash: BUG: kernel NULL pointer dereference, address: 0000000000000028 #PF: supervisor read access in kernel mode RIP: 0010:blk_cgroup_bio_start+0x10/0xd0 Call Trace: submit_bio_noacct_nocheck+0x44/0x250 nvmet_bdev_execute_rw+0x254/0x370 [nvmet] process_one_work+0x193/0x3c0 worker_thread+0x281/0x3a0 Fix this by reordering nvmet_bio_done() to call nvmet_req_bio_put() BEFORE nvmet_req_complete(). This ensures the bio is cleaned up before the request can be re-submitted, preventing the race condition.
- CVSS
- 7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Modified
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 431e58d56fcb5ff1f9eb630724a922e0d2a941df before ee10b06980acca1d46e0fa36d6fb4a9578eab6e4; from 190f4c2c863af7cc5bb354b70e0805f06419c038 before 68207ceefd71cc74ce4e983fa9bd10c3122e349b; 190f4c2c863af7cc5bb354b70e0805f06419c038 builds before 0fcee2cfc4b2e16e62ff8e0cc2cd8dd24efad65e; 2e2028fcf924d1c6df017033c8d6e28b735a0508; from 6.12.37 before 6.12.69; from 6.15.6 before 6.16 | CNA record |
linux linux_kernel linux:linux_kernel | from 6.12.37 before 6.12.69; from 6.15.6 before 6.16; from 6.16.1 before 6.18.9; 6.16; 6.16; 6.16; 6.16; 6.19; and 6 more ranges | NVD |
References
- https://git.kernel.org/stable/c/ee10b06980acca1d46e0fa36d6fb4a9578eab6e4patch
- https://git.kernel.org/stable/c/68207ceefd71cc74ce4e983fa9bd10c3122e349bpatch
- https://git.kernel.org/stable/c/0fcee2cfc4b2e16e62ff8e0cc2cd8dd24efad65epatch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.