CVE-2025-21861

一、漏洞信息
 漏洞编号：[CVE-2025-21861](https://nvd.nist.gov/vuln/detail/CVE-2025-21861)
 漏洞归属组件：[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：5.5 Medium
  Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:mm/migrate_device: don t add folio to be freed to LRU in migrate_device_finalize()If migration succeeded, we calledfolio_migrate_flags()->mem_cgroup_migrate() to migrate the memcg from theold to the new folio.  This will set memcg_data of the old folio to 0.Similarly, if migration failed, memcg_data of the dst folio is left unset.If we call folio_putback_lru() on such folios (memcg_data == 0), we willadd the folio to be freed to the LRU, making memcg code unhappy.  Runningthe hmm selftests:  # ./hmm-tests  ...  #  RUN           hmm.hmm_device_private.migrate ...  [  102.078007][T14893] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x7ff27d200 pfn:0x13cc00  [  102.079974][T14893] anon flags: 0x17ff00000020018(uptodate|dirty|swapbacked|node=0|zone=2|lastcpupid=0x7ff)  [  102.082037][T14893] raw: 017ff00000020018 dead000000000100 dead000000000122 ffff8881353896c9  [  102.083687][T14893] raw: 00000007ff27d200 0000000000000000 00000001ffffffff 0000000000000000  [  102.085331][T14893] page dumped because: VM_WARN_ON_ONCE_FOLIO(!memcg && !mem_cgroup_disabled())  [  102.087230][T14893] ------------[ cut here ]------------  [  102.088279][T14893] WARNING: CPU: 0 PID: 14893 at ./include/linux/memcontrol.h:726 folio_lruvec_lock_irqsave+0x10e/0x170  [  102.090478][T14893] Modules linked in:  [  102.091244][T14893] CPU: 0 UID: 0 PID: 14893 Comm: hmm-tests Not tainted 6.13.0-09623-g6c216bc522fd #151  [  102.093089][T14893] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014  [  102.094848][T14893] RIP: 0010:folio_lruvec_lock_irqsave+0x10e/0x170  [  102.096104][T14893] Code: ...  [  102.099908][T14893] RSP: 0018:ffffc900236c37b0 EFLAGS: 00010293  [  102.101152][T14893] RAX: 0000000000000000 RBX: ffffea0004f30000 RCX: ffffffff8183f426  [  102.102684][T14893] RDX: ffff8881063cb880 RSI: ffffffff81b8117f RDI: ffff8881063cb880  [  102.104227][T14893] RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000  [  102.105757][T14893] R10: 0000000000000001 R11: 0000000000000002 R12: ffffc900236c37d8  [  102.107296][T14893] R13: ffff888277a2bcb0 R14: 000000000000001f R15: 0000000000000000  [  102.108830][T14893] FS:  00007ff27dbdd740(0000) GS:ffff888277a00000(0000) knlGS:0000000000000000  [  102.110643][T14893] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  [  102.111924][T14893] CR2: 00007ff27d400000 CR3: 000000010866e000 CR4: 0000000000750ef0  [  102.113478][T14893] PKRU: 55555554  [  102.114172][T14893] Call Trace:  [  102.114805][T14893]  <TASK>  [  102.115397][T14893]  ? folio_lruvec_lock_irqsave+0x10e/0x170  [  102.116547][T14893]  ? __warn.cold+0x110/0x210  [  102.117461][T14893]  ? folio_lruvec_lock_irqsave+0x10e/0x170  [  102.118667][T14893]  ? report_bug+0x1b9/0x320  [  102.119571][T14893]  ? handle_bug+0x54/0x90  [  102.120494][T14893]  ? exc_invalid_op+0x17/0x50  [  102.121433][T14893]  ? asm_exc_invalid_op+0x1a/0x20  [  102.122435][T14893]  ? __wake_up_klogd.part.0+0x76/0xd0  [  102.123506][T14893]  ? dump_page+0x4f/0x60  [  102.124352][T14893]  ? folio_lruvec_lock_irqsave+0x10e/0x170  [  102.125500][T14893]  folio_batch_move_lru+0xd4/0x200  [  102.126577][T14893]  ? __pfx_lru_add+0x10/0x10  [  102.127505][T14893]  __folio_batch_add_and_move+0x391/0x720  [  102.128633][T14893]  ? __pfx_lru_add+0x10/0x10  [  102.129550][T14893]  folio_putback_lru+0x16/0x80  [  102.130564][T14893]  migrate_device_finalize+0x9b/0x530  [  102.131640][T14893]  dmirror_migrate_to_device.constprop.0+0x7c5/0xad0  [  102.133047][T14893]  dmirror_fops_unlocked_ioctl+0x89b/0xc80Likely, nothing else goes wrong: putting the last folio reference willremove the folio from the LRU again.  So besides memcg complaining, addingthe folio to be freed to the LRU is just an unnecessary step.The new flow resembles what we have in migrate_folio_move(): add the dstto the lru, rem---truncated---
 漏洞公开时间：2025-03-12 18:15:19
 漏洞创建时间：2025-03-12 18:34:49
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2025-21861
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/069dd21ea8262204f94737878389c2815a054a9e |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/3f9240d59e9a95d19f06120bfd1d0e681c6c0ac7 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/41cddf83d8b00f29fd105e7a0777366edc69a5cf |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-21861 | https://bugzilla.suse.com/show_bug.cgi?id=1239483 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2025/CVE-2025-21861.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1239483 |
| suse_bugzilla | https://git.kernel.org/stable/c/3f9240d59e9a95d19f06120bfd1d0e681c6c0ac7 | https://bugzilla.suse.com/show_bug.cgi?id=1239483 |
| suse_bugzilla | https://git.kernel.org/stable/c/069dd21ea8262204f94737878389c2815a054a9e | https://bugzilla.suse.com/show_bug.cgi?id=1239483 |
| suse_bugzilla | https://git.kernel.org/stable/c/41cddf83d8b00f29fd105e7a0777366edc69a5cf | https://bugzilla.suse.com/show_bug.cgi?id=1239483 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2025-21861 | https://bugzilla.suse.com/show_bug.cgi?id=1239483 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2025031216-CVE-2025-21861-c775@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2351625 |
| amazon_linux_explore | https://access.redhat.com/security/cve/CVE-2025-21861 | https://explore.alas.aws.amazon.com/CVE-2025-21861.html |
| amazon_linux_explore | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21861 | https://explore.alas.aws.amazon.com/CVE-2025-21861.html |

</details>

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

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
|  |  | https://git.kernel.org/stable/c/069dd21ea8262204f94737878389c2815a054a9e |  | nvd |
|  |  | https://git.kernel.org/stable/c/3f9240d59e9a95d19f06120bfd1d0e681c6c0ac7 |  | nvd |
|  |  | https://git.kernel.org/stable/c/41cddf83d8b00f29fd105e7a0777366edc69a5cf |  | nvd |
| linux_kernel | 6.12.17 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3f9240d59e9a95d19f06120bfd1d0e681c6c0ac7Issue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 | linuxkernelcves |
| linux_kernel | 6.13.5 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=069dd21ea8262204f94737878389c2815a054a9eIssue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 | linuxkernelcves |
| linux_kernel | 6.14-rc4 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=41cddf83d8b00f29fd105e7a0777366edc69a5cfPlease | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 | linuxkernelcves |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:mm/migrate_device: don t add folio to be freed to LRU in migrate_device_finalize()If migration succeeded, we calledfolio_migrate_flags()->mem_cgroup_migrate() to migrate the memcg from theold to the new folio.  This will set memcg_data of the old folio to 0.Similarly, if migration failed, memcg_data of the dst folio is left unset.If we call folio_putback_lru() on such folios (memcg_data == 0), we willadd the folio to be freed to the LRU, making memcg code unhappy.  Runningthe hmm selftests:  # ./hmm-tests  ...  #  RUN           hmm.hmm_device_private.migrate ...  [  102.078007][T14893] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x7ff27d200 pfn:0x13cc00  [  102.079974][T14893] anon flags: 0x17ff00000020018(uptodate|dirty|swapbacked|node=0|zone=2|lastcpupid=0x7ff)  [  102.082037][T14893] raw: 017ff00000020018 dead000000000100 dead000000000122 ffff8881353896c9  [  102.083687][T14893] raw: 00000007ff27d200 0000000000000000 00000001ffffffff 0000000000000000  [  102.085331][T14893] page dumped because: VM_WARN_ON_ONCE_FOLIO(!memcg && !mem_cgroup_disabled())  [  102.087230][T14893] ------------[ cut here ]------------  [  102.088279][T14893] WARNING: CPU: 0 PID: 14893 at ./include/linux/memcontrol.h:726 folio_lruvec_lock_irqsave+0x10e/0x170  [  102.090478][T14893] Modules linked in:  [  102.091244][T14893] CPU: 0 UID: 0 PID: 14893 Comm: hmm-tests Not tainted 6.13.0-09623-g6c216bc522fd #151  [  102.093089][T14893] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014  [  102.094848][T14893] RIP: 0010:folio_lruvec_lock_irqsave+0x10e/0x170  [  102.096104][T14893] Code: ...  [  102.099908][T14893] RSP: 0018:ffffc900236c37b0 EFLAGS: 00010293  [  102.101152][T14893] RAX: 0000000000000000 RBX: ffffea0004f30000 RCX: ffffffff8183f426  [  102.102684][T14893] RDX: ffff8881063cb880 RSI: ffffffff81b8117f RDI: ffff8881063cb880  [  102.104227][T14893] RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000  [  102.105757][T14893] R10: 0000000000000001 R11: 0000000000000002 R12: ffffc900236c37d8  [  102.107296][T14893] R13: ffff888277a2bcb0 R14: 000000000000001f R15: 0000000000000000  [  102.108830][T14893] FS:  00007ff27dbdd740(0000) GS:ffff888277a00000(0000) knlGS:0000000000000000  [  102.110643][T14893] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  [  102.111924][T14893] CR2: 00007ff27d400000 CR3: 000000010866e000 CR4: 0000000000750ef0  [  102.113478][T14893] PKRU: 55555554  [  102.114172][T14893] Call Trace:  [  102.114805][T14893]  <TASK>  [  102.115397][T14893]  ? folio_lruvec_lock_irqsave+0x10e/0x170  [  102.116547][T14893]  ? __warn.cold+0x110/0x210  [  102.117461][T14893]  ? folio_lruvec_lock_irqsave+0x10e/0x170  [  102.118667][T14893]  ? report_bug+0x1b9/0x320  [  102.119571][T14893]  ? handle_bug+0x54/0x90  [  102.120494][T14893]  ? exc_invalid_op+0x17/0x50  [  102.121433][T14893]  ? asm_exc_invalid_op+0x1a/0x20  [  102.122435][T14893]  ? __wake_up_klogd.part.0+0x76/0xd0  [  102.123506][T14893]  ? dump_page+0x4f/0x60  [  102.124352][T14893]  ? folio_lruvec_lock_irqsave+0x10e/0x170  [  102.125500][T14893]  folio_batch_move_lru+0xd4/0x200  [  102.126577][T14893]  ? __pfx_lru_add+0x10/0x10  [  102.127505][T14893]  __folio_batch_add_and_move+0x391/0x720  [  102.128633][T14893]  ? __pfx_lru_add+0x10/0x10  [  102.129550][T14893]  folio_putback_lru+0x16/0x80  [  102.130564][T14893]  migrate_device_finalize+0x9b/0x530  [  102.131640][T14893]  dmirror_migrate_to_device.constprop.0+0x7c5/0xad0  [  102.133047][T14893]  dmirror_fops_unlocked_ioctl+0x89b/0xc80Likely, nothing else goes wrong: putting the last folio reference willremove the folio from the LRU again.  So besides memcg complaining, addingthe folio to be freed to the LRU is just an unnecessary step.The new flow resembles what we have in migrate_folio_move(): add the dstto the lru, rem---truncated---
 openEuler评分：
  5.5
 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 受影响版本排查(受影响/不受影响)：
  1.openEuler-20.03-LTS-SP4(4.19.90):受影响
2.openEuler-22.03-LTS-SP3(5.10.0):受影响
3.openEuler-22.03-LTS-SP4(5.10.0):受影响
4.openEuler-24.03-LTS(6.6.0):受影响
5.openEuler-24.03-LTS-SP1(6.6.0):受影响
6.openEuler-24.03-LTS-SP2(6.6.0):受影响
7.master(6.12.33):不受影响
8.openEuler-24.03-LTS-Next(6.6.0):不受影响

修复是否涉及abi变化(是/否)：
  1.openEuler-20.03-LTS-SP4(4.19.90):否
2.openEuler-22.03-LTS-SP3(5.10.0):否
3.master(6.12.33):否
4.openEuler-24.03-LTS(6.6.0):否
5.openEuler-24.03-LTS-Next(6.6.0):否
6.openEuler-22.03-LTS-SP4(5.10.0):否
7.openEuler-24.03-LTS-SP1(6.6.0):否
8.openEuler-24.03-LTS-SP2(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-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.master(6.12.33):不受影响-漏洞代码不能被攻击者触发
8.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发

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

src-openEuler/kernel
关闭

内容风险标识

评论 (7)

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

内容风险标识

CVE-2025-21861

评论 (7)

搜索帮助

src-openEuler/kernel
关闭