Vulnerability · Published Dec 24, 2025 · Assigned by Linux
CVE-2025-68348block: fix memory leak in __blkdev_issue_zero_pages
Unrated
In plain English
A security flaw 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.2% (higher than 10% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: block: fix memory leak in __blkdev_issue_zero_pages Move the fatal signal check before bio_alloc() to prevent a memory leak when BLKDEV_ZERO_KILLABLE is set and a fatal signal is pending. Previously, the bio was allocated before checking for a fatal signal. If a signal was pending, the code would break out of the loop without freeing or chaining the just-allocated bio, causing a memory leak. This matches the pattern already used in __blkdev_issue_write_zeroes() where the signal check precedes the allocation.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:13 | linux | 6.12.63-1 | DEBIAN-CVE-2025-68348 |
| Debian:14 | linux | 6.17.13-1 | DEBIAN-CVE-2025-68348 |
| Ubuntu:25.10 | linux | 6.17.0-19.19 | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:25.10 | linux-aws | 6.17.0-1009.9 | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | 6.17.0-1009.9~24.04.2 | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:25.10 | linux-azure | 6.17.0-1010.10 | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | 6.17.0-1010.10~24.04.1 | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:25.10 | linux-gcp | 6.17.0-1009.9 | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1009.9~24.04.3 | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | 6.17.0-19.19~24.04.2 | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1018.18 | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1017.17 | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:25.10 | linux-oracle | 6.17.0-1009.9 | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | 6.17.0-1009.9~24.04.1 | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:25.10 | linux-raspi | 6.17.0-1010.10 | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:25.10 | linux-realtime | 6.17.0-1008.9 | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:25.10 | linux-riscv | 6.17.0-19.19.1 | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | 6.17.0-19.19.1~24.04.1 | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2025-68348 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2025-68348 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | bf86bcdb40123ee99669ee91b67e023669433a1a – before 453e4b0c84d0db1454ff0adf655d91179e6fca3abf86bcdb40123ee99669ee91b67e023669433a1a – before 7957635c679e8a01147163a3a4a1f16e1210fa03bf86bcdb40123ee99669ee91b67e023669433a1a – before 7193407bc4457212fa38ec3aff9c640e63a8dbefbf86bcdb40123ee99669ee91b67e023669433a1a – before f7e3f852a42d7cd8f1af2c330d9d153e30c8adcf |
| Linux | Linux | 6.11 |