CVE-2025-68348
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A memory leak in the Linux kernel's __blkdev_issue_zero_pages is fixed by moving the fatal signal check before bio_alloc() to prevent leaked bio allocations.
Vulnerability
A memory leak vulnerability exists in the Linux kernel's block layer function __blkdev_issue_zero_pages. The root cause is that the code allocated a bio via bio_alloc() before checking for a pending fatal signal when BLKDEV_ZERO_KILLABLE is set. If a fatal signal was pending, the function would break out of the loop without freeing or chaining the newly allocated bio, leading to a memory leak. This pattern was already corrected in the similar function __blkdev_issue_write_zeroes(), where the signal check precedes allocation [1][2].
Exploitation
Exploitation requires local access and the ability to trigger a zero-page write operation while a fatal signal is pending. No special privileges are needed beyond the ability to issue block I/O, making it accessible to unprivileged users on systems where the affected kernel is in use. The bug is triggered during normal operation when a process receives a fatal signal (e.g., SIGKILL) while performing a zero-fill block device operation.
Impact
An attacker can repeatedly trigger the leak to exhaust kernel memory, potentially leading to denial of service conditions or resource starvation for other processes. The leak is per-iteration under the specific signal condition, so sustained exploitation can degrade system performance or cause crashes.
Mitigation
The vulnerability is patched in updated Linux kernel versions. The fix has been backported to stable kernels; the commits referenced in the kernel repository (e.g., commits 453e4b0c84d0 and f7e3f852a42d) apply to various stable branches [1][2]. Users should update their kernel to include the fix or apply the patch manually.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
4News mentions
0No linked articles in our index yet.