CVE-2025-22120

一、漏洞信息
 漏洞编号：[CVE-2025-22120](https://nvd.nist.gov/vuln/detail/CVE-2025-22120)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,6.1.8,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:ext4: goto right label  out_mmap_sem  in ext4_setattr()Otherwise, if ext4_inode_attach_jinode() fails, a hung task willhappen because filemap_invalidate_unlock() isn t called to unlockmapping->invalidate_lock. Like this:EXT4-fs error (device sda) in ext4_setattr:5557: Out of memoryINFO: task fsstress:374 blocked for more than 122 seconds.      Not tainted 6.14.0-rc1-next-20250206-xfstests-dirty #726 echo 0 > /proc/sys/kernel/hung_task_timeout_secs  disables this message.task:fsstress state:D stack:0     pid:374   tgid:374   ppid:373                                  task_flags:0x440140 flags:0x00000000Call Trace: <TASK> __schedule+0x2c9/0x7f0 schedule+0x27/0xa0 schedule_preempt_disabled+0x15/0x30 rwsem_down_read_slowpath+0x278/0x4c0 down_read+0x59/0xb0 page_cache_ra_unbounded+0x65/0x1b0 filemap_get_pages+0x124/0x3e0 filemap_read+0x114/0x3d0 vfs_read+0x297/0x360 ksys_read+0x6c/0xe0 do_syscall_64+0x4b/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e
 漏洞公开时间：2025-04-16 23:16:06
 漏洞创建时间：2025-04-18 02:09:07
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2025-22120
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/32d872e3905746ff1048078256cb00f946b97d8a |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/7e91ae31e2d264155dfd102101afc2de7bd74a64 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-22120 | https://bugzilla.suse.com/show_bug.cgi?id=1241592 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2025-22120 | https://bugzilla.suse.com/show_bug.cgi?id=1241592 |
| suse_bugzilla | https://git.kernel.org/stable/c/32d872e3905746ff1048078256cb00f946b97d8a | https://bugzilla.suse.com/show_bug.cgi?id=1241592 |
| suse_bugzilla | https://git.kernel.org/stable/c/7e91ae31e2d264155dfd102101afc2de7bd74a64 | https://bugzilla.suse.com/show_bug.cgi?id=1241592 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2025/CVE-2025-22120.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1241592 |
| suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2360213 | https://bugzilla.suse.com/show_bug.cgi?id=1241592 |

</details>

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

无
</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:ext4: goto right label &#39;out_mmap_sem&#39; in ext4_setattr()Otherwise, if ext4_inode_attach_jinode() fails, a hung task willhappen because filemap_invalidate_unlock() isn&#39;t called to unlockmapping-&gt;invalidate_lock. Like this:EXT4-fs error (device sda) in ext4_setattr:5557: Out of memoryINFO: task fsstress:374 blocked for more than 122 seconds.      Not tainted 6.14.0-rc1-next-20250206-xfstests-dirty #726&#34;echo 0 &gt; /proc/sys/kernel/hung_task_timeout_secs&#34; disables this message.task:fsstress state:D stack:0     pid:374   tgid:374   ppid:373                                  task_flags:0x440140 flags:0x00000000Call Trace: &lt;TASK&gt; __schedule+0x2c9/0x7f0 schedule+0x27/0xa0 schedule_preempt_disabled+0x15/0x30 rwsem_down_read_slowpath+0x278/0x4c0 down_read+0x59/0xb0 page_cache_ra_unbounded+0x65/0x1b0 filemap_get_pages+0x124/0x3e0 filemap_read+0x114/0x3d0 vfs_read+0x297/0x360 ksys_read+0x6c/0xe0 do_syscall_64+0x4b/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7eThe Linux kernel CVE team has assigned CVE-2025-22120 to this issue.
 openEuler评分：
  3.9
 Vector：CVSS：3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
 受影响版本排查(受影响/不受影响)：
  1.openEuler-24.03-LTS(6.6.0):受影响
2.openEuler-24.03-LTS-SP1(6.6.0):受影响
3.master(6.6.0):不受影响
4.openEuler-20.03-LTS-SP4(4.19.90):不受影响
5.openEuler-22.03-LTS-SP3(5.10.0):不受影响
6.openEuler-22.03-LTS-SP4(5.10.0):不受影响
7.openEuler-24.03-LTS-Next(6.6.0):不受影响

修复是否涉及abi变化(是/否)：
  1.master(6.6.0):否
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):否

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

src-openEuler/kernel
Closed

Content Risk Flag

Comments (7)

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

Content Risk Flag

CVE-2025-22120

Comments (7)

Search

src-openEuler/kernel
Closed