CVE-2025-39792 Details
Description
In the Linux kernel, the following vulnerability has been resolved: dm: Always split write BIOs to zoned device limits Any zoned DM target that requires zone append emulation will use the block layer zone write plugging. In such case, DM target drivers must not split BIOs using dm_accept_partial_bio() as doing so can potentially lead to deadlocks with queue freeze operations. Regular write operations used to emulate zone append operations also cannot be split by the target driver as that would result in an invalid writen sector value return using the BIO sector. In order for zoned DM target drivers to avoid such incorrect BIO splitting, we must ensure that large BIOs are split before being passed to the map() function of the target, thus guaranteeing that the limits for the mapped device are not exceeded. dm-crypt and dm-flakey are the only target drivers supporting zoned devices and using dm_accept_partial_bio(). In the case of dm-crypt, this function is used to split BIOs to the internal max_write_size limit (which will be suppressed in a different patch). However, since crypt_alloc_buffer() uses a bioset allowing only up to BIO_MAX_VECS (256) vectors in a BIO. The dm-crypt device max_segments limit, which is not set and so default to BLK_MAX_SEGMENTS (128), must thus be respected and write BIOs split accordingly. In the case of dm-flakey, since zone append emulation is not required, the block layer zone write plugging is not used and no splitting of BIOs required. Modify the function dm_zone_bio_needs_split() to use the block layer helper function bio_needs_zone_write_plugging() to force a call to bio_split_to_limits() in dm_split_and_process_bio(). This allows DM target drivers to avoid using dm_accept_partial_bio() for write operations on zoned DM devices.
A vulnerability exists in the Linux kernel's handling of Block I/O (BIO) for zoned devices, specifically within the Device Mapper (DM) framework. When DM target drivers emulate zone append operations, they must not split BIOs in a way that could lead to deadlocks during queue freeze operations. This issue primarily affects the 'dm-crypt' and 'dm-flakey' target drivers, which support zoned devices but handle BIO splitting differently. The vulnerability arises because large BIOs can exceed the limits of the mapped device, potentially causing incorrect write operations and invalid sector value returns.
The vulnerability has been addressed by modifying the BIO handling functions to ensure that large BIOs are properly split before being mapped to the target, thus preventing deadlocks and incorrect write operations. Users should update to the latest version of the Linux kernel where this patch is applied.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Oct 15, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/2df7168717b7d2d32bcf017c68be16e4aae9dd13 | kernel.org | Patch |
| https://git.kernel.org/stable/c/4e9fef1cf0243d665d75c371cc80be6156cd30a2 | kernel.org | Patch |
| https://git.kernel.org/stable/c/d10bf66d9f9335ffc7521b3029b114f50604cabe | kernel.org | Patch |
| https://git.kernel.org/stable/c/f5dd256333c08ab44b5aec4a8118cb04c0f20c54 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.10, < 6.12.43 >= 6.13, < 6.15.11 >= 6.16, < 6.16.2 |
CPE
Remediation
| |
Change History
7 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 19, 2026 | CVE Translated | [email protected] |
| Oct 15, 2026 | CVE Modified | CISA-ADP |
| Oct 15, 2026 | CVE Modified | kernel.org |
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 25, 2025 | Initial Analysis | [email protected] |
| Sep 12, 2025 | New CVE Received | kernel.org |