CVE-2025-38349

一、漏洞信息
 漏洞编号：[CVE-2025-38349](https://nvd.nist.gov/vuln/detail/CVE-2025-38349)
 漏洞归属组件：[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.x分值：
  BaseScore：7.8 High
  Vector：CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
 漏洞简述：
  In the Linux kernel, a vulnerability exists in the eventpoll module where the epoll reference count (ep refcount) is decremented while still holding the epoll mutex (ep->mtx). This can lead to a race condition where another user may drop their reference to the epoll and free the epoll structure while the current user is still unlocking the mutex, resulting in a use-after-free issue. The correct approach is to move the reference count decrement operation outside the mutex.
 漏洞公开时间：2025-07-18 16:15:27
 漏洞创建时间：2025-07-18 17:21:19
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2025-38349
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40204 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40200 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-38705 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40055 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-22020 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40141 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-37828 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-39694 |  |
|  | https://git.kernel.org/stable/c/605c18698ecfa99165f36b7f59d3ed503e169814 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40110 |  |
|  | https://linux.oracle.com/cve/CVE-2025-38349.html |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40082 |  |
|  | https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2775 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40134 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40169 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40179 |  |
|  | https://git.kernel.org/stable/c/6dee745bd0aec9d399df674256e7b1ecdb615444 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40120 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40192 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-38729 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40171 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40178 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40125 |  |
|  | https://git.kernel.org/stable/c/8c2e52ebbe885c7eeaabd3b7ddcdc1246fc400d2 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40129 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40187 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-21915 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40183 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40164 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-39703 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-37758 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-38234 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40035 |  |
|  | https://project-zero.issues.chromium.org/issues/430541637 |  |
|  | https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2774 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40140 |  |
|  | https://www.suse.com/security/cve/CVE-2025-38349.html |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-23147 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40211 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-38349 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-38214 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40048 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-22083 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40201 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-38100 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-37839 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-39785 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40109 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-21693 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-37891 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-39964 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-37785 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-39931 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-23159 |  |
|  | https://www.cve.org/CVERecord?id=CVE-2025-38349 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-39940 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40176 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-38173 |  |
|  | https://ubuntu.com/security/CVE-2025-38349 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40123 |  |
|  | https://bugzilla.redhat.com/show_bug.cgi?id=2381870 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-38084 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-22107 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40088 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-39751 |  |
|  | https://security-tracker.debian.org/tracker/CVE-2025-38349 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40084 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-38581 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40167 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40194 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40173 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-37812 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40190 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2024-36357 |  |
|  | https://bugzilla.suse.com/1246777 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40198 |  |
|  | https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2767 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-39938 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40153 |  |
|  | https://linux.oracle.com/errata/ELSA-2025-20551.html |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40053 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-23150 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-22080 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40202 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-37863 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40206 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-38717 |  |
|  | https://lore.kernel.org/linux-cve-announce/2025071819-CVE-2025-38349-ee39@gregkh/T |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-39692 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40012 |  |
|  | https://git.kernel.org/stable/c/521e9ff0b67c66a17d6f9593dfccafaa984aae4c |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-40043 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2025-39992 |  |

</details>

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

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| gregkh/linux |  | https://github.com/gregkh/linux/commit/8c2e52ebbe885c7eeaabd3b7ddcdc1246fc400d2.patch |  | ljqc |
|  |  | https://git.kernel.org/stable/c/605c18698ecfa99165f36b7f59d3ed503e169814 |  | nvd |
|  |  | https://git.kernel.org/stable/c/6dee745bd0aec9d399df674256e7b1ecdb615444 |  | nvd |
|  |  | https://git.kernel.org/stable/c/8c2e52ebbe885c7eeaabd3b7ddcdc1246fc400d2 |  | nvd |
|  |  | https://git.kernel.org/stable/c/521e9ff0b67c66a17d6f9593dfccafaa984aae4c |  | nvd |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:eventpoll: don t decrement ep refcount while still holding the ep mutexJann Horn points out that epoll is decrementing the ep refcount and thendoing amutex_unlock(&#38;ep-&gt;mtx);afterwards. That s very wrong, because it can lead to a use-after-free.That pattern is actually fine for the very last reference, because thecode in question will delay the actual call to  ep_free(ep)  until afterit has unlocked the mutex.But it s wrong for the much subtler  next to last  case when somebodyelse may also be dropping their reference and free the ep while we restill using the mutex.Note that this is true even if that other user is also using the same epmutex: mutexes, unlike spinlocks, can not be used for object ownership,even if they guarantee mutual exclusion.A mutex  unlock  operation is not atomic, and as one user is stillaccessing the mutex as part of unlocking it, another user can come inand get the now released mutex and free the data structure while thefirst user is still cleaning up.See our mutex documentation in Documentation/locking/mutex-design.rst,in particular the section [1] about semantics:&#34;mutex_unlock() may access the mutex structure even after it has internally released the lock already - so it&#39;s not safe for another context to acquire the mutex and assume that the mutex_unlock() context is not using the structure anymore&#34;So if we drop our ep ref before the mutex unlock, but we weren t thelast one, we may then unlock the mutex, another user comes in, dropstheir reference and releases the  ep  as it now has no users - allwhile the mutex_unlock() is still accessing it.Fix this by simply moving the ep refcount dropping to outside the mutex:the refcount itself is atomic, and doesn t need mutex protection (that sthe whole point of refcounts: unlike mutexes, they are inherentlyabout object lifetimes).The Linux kernel CVE team has assigned CVE-2025-38349 to this issue.
 openEuler评分：
  7.8
 Vector：CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
 受影响版本排查(受影响/不受影响)：
  1.openEuler-24.03-LTS(6.6.0):受影响
2.openEuler-24.03-LTS-SP1(6.6.0):受影响
3.openEuler-24.03-LTS-SP2(6.6.0):受影响
4.openEuler-24.03-LTS-SP3(6.6.0):不受影响
5.master(6.12.33):不受影响
6.openEuler-20.03-LTS-SP4(4.19.90):不受影响
7.openEuler-22.03-LTS-SP3(5.10.0):不受影响
8.openEuler-22.03-LTS-SP4(5.10.0):不受影响
9.openEuler-24.03-LTS-Next(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):否
9.openEuler-24.03-LTS-SP3(6.6.0):否

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

三、漏洞修复
安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2025-2775

src-openEuler / kernel
Closed

Content Risk Flag

Comments (29)

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

Content Risk Flag

CVE-2025-38349

Comments (29)

Search

src-openEuler / kernel
Closed