CVE-2025-22015

一、漏洞信息
漏洞编号：CVE-2025-22015
漏洞归属组件：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:mm/migrate: fix shmem xarray update during migrationA shmem folio can be either in page cache or in swap cache, but not at thesame time. Namely, once it is in swap cache, folio->mapping should beNULL, and the folio is no longer in a shmem mapping.In __folio_migrate_mapping(), to determine the number of xarray entries toupdate, folio_test_swapbacked() is used, but that conflates shmem in pagecache case and shmem in swap cache case. It leads to xarray multi-indexentry corruption, since it turns a sibling entry to a normal entry duringxas_store() (see [1] for a userspace reproduction). Fix it by only usingfolio_test_swapcache() to determine whether xarray is storing swap cacheentries or not to choose the right number of xarray entries to update.[1] https://lore.kernel.org/linux-mm/Z8idPCkaJW1IChjT@casper.infradead.org/Note:In __split_huge_page(), folio_test_anon() && folio_test_swapcache() isused to get swap_cache address space, but that ignores the shmem folio inswap cache case. It could lead to NULL pointer dereferencing when ain-swap-cache shmem folio is split at __xa_store(), since!folio_test_anon() is true and folio->mapping is NULL. But fortunately,its caller split_huge_page_to_list_to_order() bails out early with EBUSYwhen folio->mapping is NULL. So no need to take care of it here.
漏洞公开时间：2025-04-08 17:15:26
漏洞创建时间：2025-04-08 17:31:50
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2025-22015

更多参考(点击展开)

参考来源	参考链接	来源链接
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/29124ae980e2860f0eec7355949d3d3292ee81da
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/49100c0b070e900f87c8fac3be9b9ef8a30fa673
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/60cf233b585cdf1f3c5e52d1225606b86acd08b0
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/75cfb92eb63298d717b6b0118f91ba12c4fcfeb5
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/c057ee03f751d6cecf7ee64f52f6545d94082aaa
suse_bugzilla	http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-22015	https://bugzilla.suse.com/show_bug.cgi?id=1240944
suse_bugzilla	https://www.cve.org/CVERecord?id=CVE-2025-22015	https://bugzilla.suse.com/show_bug.cgi?id=1240944
suse_bugzilla	https://git.kernel.org/stable/c/29124ae980e2860f0eec7355949d3d3292ee81da	https://bugzilla.suse.com/show_bug.cgi?id=1240944
suse_bugzilla	https://git.kernel.org/stable/c/49100c0b070e900f87c8fac3be9b9ef8a30fa673	https://bugzilla.suse.com/show_bug.cgi?id=1240944
suse_bugzilla	https://git.kernel.org/stable/c/60cf233b585cdf1f3c5e52d1225606b86acd08b0	https://bugzilla.suse.com/show_bug.cgi?id=1240944
suse_bugzilla	https://git.kernel.org/stable/c/75cfb92eb63298d717b6b0118f91ba12c4fcfeb5	https://bugzilla.suse.com/show_bug.cgi?id=1240944
suse_bugzilla	https://git.kernel.org/stable/c/c057ee03f751d6cecf7ee64f52f6545d94082aaa	https://bugzilla.suse.com/show_bug.cgi?id=1240944
suse_bugzilla	https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2025/CVE-2025-22015.mbox	https://bugzilla.suse.com/show_bug.cgi?id=1240944
suse_bugzilla	https://bugzilla.redhat.com/show_bug.cgi?id=2358228	https://bugzilla.suse.com/show_bug.cgi?id=1240944
redhat_bugzilla	https://lore.kernel.org/linux-mm/Z8idPCkaJW1IChjT@casper.infradead.org/	https://bugzilla.redhat.com/show_bug.cgi?id=2358228
redhat_bugzilla	https://lore.kernel.org/linux-cve-announce/2025040843-CVE-2025-22015-3408@gregkh/T	https://bugzilla.redhat.com/show_bug.cgi?id=2358228
osv	https://git.kernel.org/stable/c/29124ae980e2860f0eec7355949d3d3292ee81da	https://osv.dev/vulnerability/CVE-2025-22015
osv	https://git.kernel.org/stable/c/49100c0b070e900f87c8fac3be9b9ef8a30fa673	https://osv.dev/vulnerability/CVE-2025-22015
osv	https://git.kernel.org/stable/c/60cf233b585cdf1f3c5e52d1225606b86acd08b0	https://osv.dev/vulnerability/CVE-2025-22015
osv	https://git.kernel.org/stable/c/75cfb92eb63298d717b6b0118f91ba12c4fcfeb5	https://osv.dev/vulnerability/CVE-2025-22015
osv	https://git.kernel.org/stable/c/c057ee03f751d6cecf7ee64f52f6545d94082aaa	https://osv.dev/vulnerability/CVE-2025-22015
osv	https://security-tracker.debian.org/tracker/CVE-2025-22015	https://osv.dev/vulnerability/CVE-2025-22015

漏洞分析指导链接：
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
openBrain开源漏洞感知系统
漏洞补丁信息：

详情(点击展开)

影响的包	修复版本	修复补丁	问题引入补丁	来源
linux_kernel	6.1.132	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=49100c0b070e900f87c8fac3be9b9ef8a30fa673Issue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=be72d197b2281e2ee3f28017fc9be1ab17e26d16	linuxkernelcves
linux_kernel	6.6.85	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=29124ae980e2860f0eec7355949d3d3292ee81daIssue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=be72d197b2281e2ee3f28017fc9be1ab17e26d16	linuxkernelcves
linux_kernel	6.12.21	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c057ee03f751d6cecf7ee64f52f6545d94082aaaIssue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=be72d197b2281e2ee3f28017fc9be1ab17e26d16	linuxkernelcves
linux_kernel	6.13.9	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=75cfb92eb63298d717b6b0118f91ba12c4fcfeb5Issue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=be72d197b2281e2ee3f28017fc9be1ab17e26d16	linuxkernelcves
linux_kernel	6.14	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=60cf233b585cdf1f3c5e52d1225606b86acd08b0Please	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=be72d197b2281e2ee3f28017fc9be1ab17e26d16	linuxkernelcves

二、漏洞分析结构反馈
影响性分析说明：
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.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.6.0):不受影响
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.6.0):否
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.master(6.6.0):不受影响-漏洞代码不能被攻击者触发
5.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发
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):不受影响-漏洞代码不存在

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

Hi openeuler-ci-bot, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: Kernel, and any of the maintainers.

@yangyingliang ,@jiaoff ,@guohaocs2c ,@hanjun-guo ,@woqidaideshi ,@newbeats ,@zhangyi089 ,@colyli ,@thundertown ,@htforge ,@chiqijun ,@lengchao ,@zhujianwei001 ,@kylin-mayukun ,@wangxiongfeng ,@wkfxxx ,@SuperSix173 ,@jentlestea ,@oskernel0719 ,@gasonchen 
**issue处理注意事项:** 
**1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;**
**2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;**
**3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.**
************************************************************************
影响性分析说明:

openEuler评分: (评分和向量)

受影响版本排查(受影响/不受影响): 
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):

修复是否涉及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.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):

issue处理具体操作请参考: 
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://gitee.com/help/articles/4142

参考网址	关联pr	状态	补丁链接
https://nvd.nist.gov/vuln/detail/CVE-2025-22015	None	None	https://git.kernel.org/stable/c/60cf233b585cdf1f3c5e52d1225606b86acd08b0 https://git.kernel.org/stable/c/49100c0b070e900f87c8fac3be9b9ef8a30fa673 https://git.kernel.org/stable/c/75cfb92eb63298d717b6b0118f91ba12c4fcfeb5 https://git.kernel.org/stable/c/c057ee03f751d6cecf7ee64f52f6545d94082aaa https://git.kernel.org/stable/c/29124ae980e2860f0eec7355949d3d3292ee81da
https://ubuntu.com/security/CVE-2025-22015	None	None	https://discourse.ubuntu.com/c/project
https://www.opencve.io/cve/CVE-2025-22015	None	None	https://git.kernel.org/stable/c/60cf233b585cdf1f3c5e52d1225606b86acd08b0 https://git.kernel.org/stable/c/49100c0b070e900f87c8fac3be9b9ef8a30fa673 https://git.kernel.org/stable/c/75cfb92eb63298d717b6b0118f91ba12c4fcfeb5 https://git.kernel.org/stable/c/c057ee03f751d6cecf7ee64f52f6545d94082aaa https://git.kernel.org/stable/c/29124ae980e2860f0eec7355949d3d3292ee81da
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2025-22015
https://security-tracker.debian.org/tracker/CVE-2025-22015
http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2025-22015

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用CVE补丁工具。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1

CVE-2025-22015

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

mm/migrate: fix shmem xarray update during migration

A shmem folio can be either in page cache or in swap cache, but not at the
same time. Namely, once it is in swap cache, folio->mapping should be
NULL, and the folio is no longer in a shmem mapping.

In __folio_migrate_mapping(), to determine the number of xarray entries to
update, folio_test_swapbacked() is used, but that conflates shmem in page
cache case and shmem in swap cache case. It leads to xarray multi-index
entry corruption, since it turns a sibling entry to a normal entry during
xas_store() (see [1] for a userspace reproduction). Fix it by only using
folio_test_swapcache() to determine whether xarray is storing swap cache
entries or not to choose the right number of xarray entries to update.

[1] https://lore.kernel.org/linux-mm/Z8idPCkaJW1IChjT@casper.infradead.org/

Note:
In __split_huge_page(), folio_test_anon() && folio_test_swapcache() is
used to get swap_cache address space, but that ignores the shmem folio in
swap cache case. It could lead to NULL pointer dereferencing when a
in-swap-cache shmem folio is split at __xa_store(), since
!folio_test_anon() is true and folio->mapping is NULL. But fortunately,
its caller split_huge_page_to_list_to_order() bails out early with EBUSY
when folio->mapping is NULL. So no need to take care of it here.

openEuler评分:(评分和向量)
3.9
AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L

受影响版本排查(受影响/不受影响):
1.master(6.1.0):不受影响
2.openEuler-20.03-LTS-SP4:不受影响
3.openEuler-22.03-LTS-SP3:不受影响
4.openEuler-22.03-LTS-SP4:不受影响
5.openEuler-24.03-LTS:受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:受影响
8.openEuler-24.03-LTS-SP2:受影响

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

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

@CTC-XiboWang 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态  | 分析项目 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|In the Linux kernel, the following vulnerability has been resolved:mm/migrate: fix shmem xarray update during migrationA shmem folio can be either in page cache or in swap cache, but not at thesame time.  Namely, once it is in swap cache, folio->mapping should beNULL, and the folio is no longer in a shmem mapping.In __folio_migrate_mapping(), to determine the number of xarray entries toupdate, folio_test_swapbacked() is used, but that conflates shmem in pagecache case and shmem in swap cache case.  It leads to xarray multi-indexentry corruption, since it turns a sibling entry to a normal entry duringxas_store() (see [1] for a userspace reproduction).  Fix it by only usingfolio_test_swapcache() to determine whether xarray is storing swap cacheentries or not to choose the right number of xarray entries to update.[1] https://lore.kernel.org/linux-mm/Z8idPCkaJW1IChjT@casper.infradead.org/Note:In __split_huge_page(), folio_test_anon() && folio_test_swapcache() isused to get swap_cache address space, but that ignores the shmem folio inswap cache case.  It could lead to NULL pointer dereferencing when ain-swap-cache shmem folio is split at __xa_store(), since!folio_test_anon() is true and folio->mapping is NULL.  But fortunately,its caller split_huge_page_to_list_to_order() bails out early with EBUSYwhen folio->mapping is NULL.  So no need to take care of it here.|
|已分析|2.openEulerScore|3.9|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L|
|已分析|4.受影响版本排查|openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-SP1:受影响,openEuler-24.03-LTS-SP2:受影响,master:不受影响,openEuler-20.03-LTS-SP4:不受影响,openEuler-22.03-LTS-SP3:不受影响,openEuler-22.03-LTS-SP4:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.是否涉及abi变化|master:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP3:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-24.03-LTS-SP1:否,openEuler-24.03-LTS-SP2:否|
|已分析|6.原因说明|openEuler-24.03-LTS:正常修复,openEuler-24.03-LTS-SP1:正常修复,openEuler-24.03-LTS-SP2:正常修复,master:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发,openEuler-20.03-LTS-SP4:不受影响-漏洞代码不存在,openEuler-22.03-LTS-SP3:不受影响-漏洞代码不存在,openEuler-22.03-LTS-SP4:不受影响-漏洞代码不存在|

**请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.**

CVE-2025-22015

影响性分析说明：
Reserved.

openEuler评分:(评分和向量)
5.5
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:不受影响
2.openEuler-22.03-LTS-SP3:不受影响
3.openEuler-22.03-LTS-SP4:不受影响
4.master(6.6.0):不受影响
5.openEuler-24.03-LTS:受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:受影响
8.openEuler-24.03-LTS-SP2:受影响

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

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

===========================================================

src-openEuler/kernel

内容风险标识

评论 (7)

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

内容风险标识

CVE-2025-22015

评论 (7)

搜索帮助

src-openEuler/kernel