{ "dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": { "cveId": "CVE-2025-39792", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2025-04-16T07:20:57.132Z", "datePublished": "2025-09-12T15:59:29.477Z", "dateUpdated": "2026-08-05T12:05:12.947Z" }, "containers": { "cna": { "providerMetadata": { "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-05T12:05:12.947Z" }, "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndm: Always split write BIOs to zoned device limits\n\nAny zoned DM target that requires zone append emulation will use the\nblock layer zone write plugging. In such case, DM target drivers must\nnot split BIOs using dm_accept_partial_bio() as doing so can potentially\nlead to deadlocks with queue freeze operations. Regular write operations\nused to emulate zone append operations also cannot be split by the\ntarget driver as that would result in an invalid writen sector value\nreturn using the BIO sector.\n\nIn order for zoned DM target drivers to avoid such incorrect BIO\nsplitting, we must ensure that large BIOs are split before being passed\nto the map() function of the target, thus guaranteeing that the\nlimits for the mapped device are not exceeded.\n\ndm-crypt and dm-flakey are the only target drivers supporting zoned\ndevices and using dm_accept_partial_bio().\n\nIn the case of dm-crypt, this function is used to split BIOs to the\ninternal max_write_size limit (which will be suppressed in a different\npatch). However, since crypt_alloc_buffer() uses a bioset allowing only\nup to BIO_MAX_VECS (256) vectors in a BIO. The dm-crypt device\nmax_segments limit, which is not set and so default to BLK_MAX_SEGMENTS\n(128), must thus be respected and write BIOs split accordingly.\n\nIn the case of dm-flakey, since zone append emulation is not required,\nthe block layer zone write plugging is not used and no splitting of BIOs\nrequired.\n\nModify the function dm_zone_bio_needs_split() to use the block layer\nhelper function bio_needs_zone_write_plugging() to force a call to\nbio_split_to_limits() in dm_split_and_process_bio(). This allows DM\ntarget drivers to avoid using dm_accept_partial_bio() for write\noperations on zoned DM devices." } ], "metrics": [ { "cvssV3_1": { "version": "3.1", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "baseScore": 7.8, "baseSeverity": "HIGH" }, "scenarios": [ { "lang": "en", "value": "AV:L - The defect is reached by submitting write I/O to a local device-mapper (dm-crypt) target stacked on a zoned block device, via ordinary write()/pwrite()/mmap or direct block-device access. No network protocol handler is involved.\nAC:L - dm-crypt's max_write_size defaults to 128 KB, so any write larger than that on a zoned dm-crypt target deterministically takes the unsplit/mis-split path — no race to win and no memory layout to groom; the attacker simply issues a large write.\nPR:L - Only an unprivileged local user with write access to a filesystem residing on the zoned dm-crypt device is needed to issue the triggering BIOs; root is required only to have configured the device beforehand, which is the deployment scenario, not an attack prerequisite.\nUI:N - The attacker's own write operations trigger the flaw; no victim must open a file, mount a filesystem, or take any other action.\nS:U - The deadlock and the data corruption are confined to the kernel and the storage stack of the same system; no VM, IOMMU, or other security-authority boundary is crossed.\nC:H - Emulated zone append returns an invalid written sector, so the filesystem records extents at locations other than where the data actually landed; subsequent reads of those extents return unrelated on-disk content (no data checksums on xfs), exposing other files'/users' data on a shared volume.\nI:H - The incorrect written-sector reporting causes persistent on-disk data corruption in xfs and btrfs on zoned dm-crypt volumes, with writes and metadata landing at wrong sectors and clobbering data outside the attacker's own files.\nA:H - A split write BIO's remainder is re-plugged and calls blk_queue_enter() from the zone write plug work, deadlocking against a concurrent queue freeze while DM submission still holds the BIOs the freeze is waiting for — an unrecoverable I/O hang requiring reboot." } ] } ], "affected": [ { "product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "drivers/md/dm.c" ], "versions": [ { "version": "f211268ed1f9bdf48f06a3ead5f5d88437450579", "lessThan": "d10bf66d9f9335ffc7521b3029b114f50604cabe", "status": "affected", "versionType": "git" }, { "version": "f211268ed1f9bdf48f06a3ead5f5d88437450579", "lessThan": "f5dd256333c08ab44b5aec4a8118cb04c0f20c54", "status": "affected", "versionType": "git" }, { "version": "f211268ed1f9bdf48f06a3ead5f5d88437450579", "lessThan": "4e9fef1cf0243d665d75c371cc80be6156cd30a2", "status": "affected", "versionType": "git" }, { "version": "f211268ed1f9bdf48f06a3ead5f5d88437450579", "lessThan": "2df7168717b7d2d32bcf017c68be16e4aae9dd13", "status": "affected", "versionType": "git" } ] }, { "product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "drivers/md/dm.c" ], "versions": [ { "version": "6.10", "status": "affected" }, { "version": "0", "lessThan": "6.10", "status": "unaffected", "versionType": "semver" }, { "version": "6.12.43", "lessThanOrEqual": "6.12.*", "status": "unaffected", "versionType": "semver" }, { "version": "6.15.11", "lessThanOrEqual": "6.15.*", "status": "unaffected", "versionType": "semver" }, { "version": "6.16.2", "lessThanOrEqual": "6.16.*", "status": "unaffected", "versionType": "semver" }, { "version": "6.17", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix" } ] } ], "cpeApplicability": [ { "nodes": [ { "operator": "OR", "negate": false, "cpeMatch": [ { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.10", "versionEndExcluding": "6.12.43" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.10", "versionEndExcluding": "6.15.11" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.10", "versionEndExcluding": "6.16.2" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.10", "versionEndExcluding": "6.17" } ] } ] } ], "references": [ { "url": "https://git.kernel.org/stable/c/d10bf66d9f9335ffc7521b3029b114f50604cabe" }, { "url": "https://git.kernel.org/stable/c/f5dd256333c08ab44b5aec4a8118cb04c0f20c54" }, { "url": "https://git.kernel.org/stable/c/4e9fef1cf0243d665d75c371cc80be6156cd30a2" }, { "url": "https://git.kernel.org/stable/c/2df7168717b7d2d32bcf017c68be16e4aae9dd13" } ], "title": "dm: Always split write BIOs to zoned device limits", "x_generator": { "engine": "bippy-1.2.0" } } } }