CVE-2025-39791

一、漏洞信息
 漏洞编号：[CVE-2025-39791](https://nvd.nist.gov/vuln/detail/CVE-2025-39791)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,6.4.0,6.6.0
 CVSS V3.0分值：
  BaseScore：N/A None
  Vector：CVSS：3.0/
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:dm: dm-crypt: Do not partially accept write BIOs with zoned targetsRead and write operations issued to a dm-crypt target may be splitaccording to the dm-crypt internal limits defined by the max_read_sizeand max_write_size module parameters (default is 128 KB). The intent isto improve processing time of large BIOs by splitting them into smalleroperations that can be parallelized on different CPUs.For zoned dm-crypt targets, this BIO splitting is still done but withoutthe parallel execution to ensure that the issuing order of writeoperations to the underlying devices remains sequential. However, thesplitting itself causes other problems:1) Since dm-crypt relies on the block layer zone write plugging to   handle zone append emulation using regular write operations, the   reminder of a split write BIO will always be plugged into the target   zone write plugged. Once the on-going write BIO finishes, this   reminder BIO is unplugged and issued from the zone write plug work.   If this reminder BIO itself needs to be split, the reminder will be   re-issued and plugged again, but that causes a call to a   blk_queue_enter(), which may block if a queue freeze operation was   initiated. This results in a deadlock as DM submission still holds   BIOs that the queue freeze side is waiting for.2) dm-crypt relies on the emulation done by the block layer using   regular write operations for processing zone append operations. This   still requires to properly return the written sector as the BIO   sector of the original BIO. However, this can be done correctly only   and only if there is a single clone BIO used for processing the   original zone append operation issued by the user. If the size of a   zone append operation is larger than dm-crypt max_write_size, then   the orginal BIO will be split and processed as a chain of regular   write operations. Such chaining result in an incorrect written sector   being returned to the zone append issuer using the original BIO   sector.  This in turn results in file system data corruptions using   xfs or btrfs.Fix this by modifying get_max_request_size() to always return the sizeof the BIO to avoid it being split with dm_accpet_partial_bio() incrypt_map(). get_max_request_size() is renamed toget_max_request_sectors() to clarify the unit of the value returnedand its interface is changed to take a struct dm_target pointer and apointer to the struct bio being processed. In addition to this change,to ensure that crypt_alloc_buffer() works correctly, set the dm-cryptdevice max_hw_sectors limit to be at mostBIO_MAX_VECS << PAGE_SECTORS_SHIFT (1 MB with a 4KB page architecture).This forces DM core to split write BIOs before passing them tocrypt_map(), and thus guaranteeing that dm-crypt can always accept anentire write BIO without needing to split it.This change does not have any effect on the read path of dm-crypt. Readoperations can still be split and the BIO fragments processed inparallel. There is also no impact on the performance of the write pathgiven that all zone write BIOs were already processed inline instead ofin parallel.This change also does not affect in any way regular dm-crypt blockdevices.
 漏洞公开时间：2025-09-12 01:15:45
 漏洞创建时间：2025-09-12 02:09:57
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2025-39791
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
|  | https://git.kernel.org/stable/c/8864616719b6bbf92356bc89ff544b0cd484c656 |  |
|  | https://git.kernel.org/stable/c/52a2c4c60470352acf9cde7a2dfa661c1e67e796 |  |
|  | https://git.kernel.org/stable/c/e549663849e5bb3b985dc2d293069f0d9747ae72 |  |
|  | https://lore.kernel.org/linux-cve-announce/2025091153-CVE-2025-39791-0f3d@gregkh/T/#u |  |
|  | https://security-tracker.debian.org/tracker/CVE-2025-39791 |  |
|  | https://www.cve.org/CVERecord?id=CVE-2025-39791 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-39791 |  |
|  | https://lore.kernel.org/linux-cve-announce/2025091153-CVE-2025-39791-0f3d@gregkh/T |  |
|  | https://bugzilla.redhat.com/show_bug.cgi?id=2394613 |  |
|  | https://docs.bell-sw.com/security/cves/CVE-2025-39791 |  |
|  | https://ubuntu.com/security/CVE-2025-39791 |  |
|  | https://www.cve.org/CVERecord?id=CVE-2025-39791 |  |
|  | https://git.kernel.org/linus/e549663849e5bb3b985dc2d293069f0d9747ae72 |  |
|  | https://git.kernel.org/stable/c/52a2c4c60470352acf9cde7a2dfa661c1e67e796 |  |
|  | https://git.kernel.org/stable/c/8864616719b6bbf92356bc89ff544b0cd484c656 |  |
|  | https://git.kernel.org/stable/c/e549663849e5bb3b985dc2d293069f0d9747ae72 |  |
|  | https://git.kernel.org/stable/c/52a2c4c60470352acf9cde7a2dfa661c1e67e796 |  |
|  | https://git.kernel.org/stable/c/8864616719b6bbf92356bc89ff544b0cd484c656 |  |
|  | https://git.kernel.org/stable/c/e549663849e5bb3b985dc2d293069f0d9747ae72 |  |
|  | http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-39791 |  |
|  | https://git.kernel.org/stable/c/52a2c4c60470352acf9cde7a2dfa661c1e67e796 |  |
|  | https://git.kernel.org/stable/c/8864616719b6bbf92356bc89ff544b0cd484c656 |  |
|  | https://git.kernel.org/stable/c/e549663849e5bb3b985dc2d293069f0d9747ae72 |  |
|  | http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-39791 |  |
|  | https://git.kernel.org/stable/c/52a2c4c60470352acf9cde7a2dfa661c1e67e796 |  |
|  | https://git.kernel.org/stable/c/8864616719b6bbf92356bc89ff544b0cd484c656 |  |
|  | https://git.kernel.org/stable/c/e549663849e5bb3b985dc2d293069f0d9747ae72 |  |

</details>

漏洞分析指导链接：
  https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
 漏洞数据来源:
  七彩瞬析开源风险感知平台
 漏洞补丁信息：
  <details>
<summary>详情(点击展开)</summary>

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
|  |  | https://git.kernel.org/stable/c/8864616719b6bbf92356bc89ff544b0cd484c656 |  | cvelistv5 |
|  |  | https://git.kernel.org/stable/c/52a2c4c60470352acf9cde7a2dfa661c1e67e796 |  | cvelistv5 |
|  |  | https://git.kernel.org/stable/c/e549663849e5bb3b985dc2d293069f0d9747ae72 |  | cvelistv5 |
|  |  | https://git.kernel.org/linus/e549663849e5bb3b985dc2d293069f0d9747ae72 |  | osv |
|  |  | https://git.kernel.org/stable/c/52a2c4c60470352acf9cde7a2dfa661c1e67e796 |  | osv |
|  |  | https://git.kernel.org/stable/c/8864616719b6bbf92356bc89ff544b0cd484c656 |  | osv |
|  |  | https://git.kernel.org/stable/c/e549663849e5bb3b985dc2d293069f0d9747ae72 |  | osv |
|  |  | https://git.kernel.org/stable/c/52a2c4c60470352acf9cde7a2dfa661c1e67e796 |  | circl |
|  |  | https://git.kernel.org/stable/c/8864616719b6bbf92356bc89ff544b0cd484c656 |  | circl |
|  |  | https://git.kernel.org/stable/c/e549663849e5bb3b985dc2d293069f0d9747ae72 |  | circl |
|  |  | https://git.kernel.org/stable/c/52a2c4c60470352acf9cde7a2dfa661c1e67e796 |  | snyk |
|  |  | https://git.kernel.org/stable/c/8864616719b6bbf92356bc89ff544b0cd484c656 |  | snyk |
|  |  | https://git.kernel.org/stable/c/e549663849e5bb3b985dc2d293069f0d9747ae72 |  | snyk |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  Reserved.
 openEuler评分：
  5.5
 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 受影响版本排查(受影响/不受影响)：
  1.master(6.12.33):不受影响
2.openEuler-20.03-LTS-SP4(4.19.90):不受影响
3.openEuler-22.03-LTS-SP3(5.10.0):不受影响
4.openEuler-22.03-LTS-SP4(5.10.0):不受影响
5.openEuler-24.03-LTS(6.6.0):不受影响
6.openEuler-24.03-LTS-Next(6.6.0):不受影响
7.openEuler-24.03-LTS-SP1(6.6.0):不受影响
8.openEuler-24.03-LTS-SP2(6.6.0):不受影响

修复是否涉及abi变化(是/否)：
  1.master(6.12.33):否
2.openEuler-20.03-LTS-SP4(4.19.90):否
3.openEuler-22.03-LTS-SP3(5.10.0):否
4.openEuler-22.03-LTS-SP4(5.10.0):否
5.openEuler-24.03-LTS(6.6.0):否
6.openEuler-24.03-LTS-Next(6.6.0):否
7.openEuler-24.03-LTS-SP1(6.6.0):否
8.openEuler-24.03-LTS-SP2(6.6.0):否

原因说明：
  1.master(6.12.33):不受影响-漏洞代码不能被攻击者触发
2.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发
3.openEuler-20.03-LTS-SP4(4.19.90):不受影响-漏洞代码不存在
4.openEuler-22.03-LTS-SP3(5.10.0):不受影响-漏洞代码不存在
5.openEuler-22.03-LTS-SP4(5.10.0):不受影响-漏洞代码不存在
6.openEuler-24.03-LTS(6.6.0):不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-SP1(6.6.0):不受影响-漏洞代码不存在
8.openEuler-24.03-LTS-SP2(6.6.0):不受影响-漏洞代码不存在

src-openEuler/kernel
Closed

Content Risk Flag

Comments (5)

src-openEuler/kernelClosed .gitee-modal { width: 500px !important; }

Content Risk Flag

CVE-2025-39791

Comments (5)

Search

src-openEuler/kernel
Closed