Vulnerability · Published Feb 14, 2026 · Assigned by Linux
CVE-2026-23148nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference
High 7.5
In plain English
A high-severity race condition in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 23% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:13 | linux | 6.12.69-1 | DEBIAN-CVE-2026-23148 |
| Debian:14 | linux | 6.18.9-1 | DEBIAN-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux | 6.8.0-117.117 | UBUNTU-CVE-2026-23148 |
| Ubuntu:25.10 | linux | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1055.58 | UBUNTU-CVE-2026-23148 |
| Ubuntu:25.10 | linux-aws | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1057.60~22.04.1 | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1056.62 | UBUNTU-CVE-2026-23148 |
| Ubuntu:25.10 | linux-azure | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | 6.17.0-1021.21~24.04.1 | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1059.65~22.04.1 | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1058.65 | UBUNTU-CVE-2026-23148 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1058.65~22.04.1 | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1058.61 | UBUNTU-CVE-2026-23148 |
| Ubuntu:25.10 | linux-gcp | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1021.24~24.04.1 | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1060.63~22.04.1 | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1054.60 | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1041.44 | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | 6.17.0-41.41~24.04.1 | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-124.124~22.04.1 | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1055.56 | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1055.56~22.04.1 | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-117.117.1 | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-117.117.1~22.04.1 | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1054.57 | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1031.31 | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1054.57~22.04.1 | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1054.57.1 | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1024.24 | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1030.30 | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1054.55 | UBUNTU-CVE-2026-23148 |
| Ubuntu:25.10 | linux-oracle | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | 6.17.0-1019.19~24.04.3 | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1054.55~22.04.1 | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1056.60 | UBUNTU-CVE-2026-23148 |
| Ubuntu:25.10 | linux-raspi | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:25.10 | linux-realtime | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:25.10 | linux-riscv | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-117.117~22.04.1 | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-23148 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1032.33 | UBUNTU-CVE-2026-23148 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 431e58d56fcb5ff1f9eb630724a922e0d2a941df – before ee10b06980acca1d46e0fa36d6fb4a9578eab6e4190f4c2c863af7cc5bb354b70e0805f06419c038 – before 68207ceefd71cc74ce4e983fa9bd10c3122e349b190f4c2c863af7cc5bb354b70e0805f06419c038 – before 0fcee2cfc4b2e16e62ff8e0cc2cd8dd24efad65e2e2028fcf924d1c6df017033c8d6e28b735a05086.12.37 – before 6.12.696.15.6 – before 6.16 |
| Linux | Linux | 6.16 |
Weakness: CWE-362 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H