CVE-2025-37774

一、漏洞信息
 漏洞编号：[CVE-2025-37774](https://nvd.nist.gov/vuln/detail/CVE-2025-37774)
 漏洞归属组件：[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:slab: ensure slab->obj_exts is clear in a newly allocated slab pagektest recently reported crashes while running several buffered io testswith __alloc_tagging_slab_alloc_hook() at the top of the crash call stack.The signature indicates an invalid address dereference with low bits ofslab->obj_exts being set. The bits were outside of the range used bypage_memcg_data_flags and objext_flags and hence were not masked outby slab_obj_exts() when obtaining the pointer stored in slab->obj_exts.The typical crash log looks like this:00510 Unable to handle kernel NULL pointer dereference at virtual address 000000000000001000510 Mem abort info:00510   ESR = 0x000000009600004500510   EC = 0x25: DABT (current EL), IL = 32 bits00510   SET = 0, FnV = 000510   EA = 0, S1PTW = 000510   FSC = 0x05: level 1 translation fault00510 Data abort info:00510   ISV = 0, ISS = 0x00000045, ISS2 = 0x0000000000510   CM = 0, WnR = 1, TnD = 0, TagAccess = 000510   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 000510 user pgtable: 4k pages, 39-bit VAs, pgdp=000000010417500000510 [0000000000000010] pgd=0000000000000000, p4d=0000000000000000, pud=000000000000000000510 Internal error: Oops: 0000000096000045 [#1]  SMP00510 Modules linked in:00510 CPU: 10 UID: 0 PID: 7692 Comm: cat Not tainted 6.15.0-rc1-ktest-g189e17946605 #19327 NONE00510 Hardware name: linux,dummy-virt (DT)00510 pstate: 20001005 (nzCv daif -PAN -UAO -TCO -DIT +SSBS BTYPE=--)00510 pc : __alloc_tagging_slab_alloc_hook+0xe0/0x19000510 lr : __kmalloc_noprof+0x150/0x31000510 sp : ffffff80c87df6c000510 x29: ffffff80c87df6c0 x28: 000000000013d1ff x27: 000000000013d20000510 x26: ffffff80c87df9e0 x25: 0000000000000000 x24: 000000000000000100510 x23: ffffffc08041953c x22: 000000000000004c x21: ffffff80c000218000510 x20: fffffffec3120840 x19: ffffff80c4821000 x18: 000000000000000000510 x17: fffffffec3d02f00 x16: fffffffec3d02e00 x15: fffffffec3d0070000510 x14: fffffffec3d00600 x13: 0000000000000200 x12: 000000000000000600510 x11: ffffffc080bb86c0 x10: 0000000000000000 x9 : ffffffc080201e5800510 x8 : ffffff80c4821060 x7 : 0000000000000000 x6 : 000000005555555600510 x5 : 0000000000000001 x4 : 0000000000000010 x3 : 000000000000006000510 x2 : 0000000000000000 x1 : ffffffc080f50cf8 x0 : ffffff80d801d00000510 Call trace:00510  __alloc_tagging_slab_alloc_hook+0xe0/0x190 (P)00510  __kmalloc_noprof+0x150/0x31000510  __bch2_folio_create+0x5c/0xf800510  bch2_folio_create+0x2c/0x4000510  bch2_readahead+0xc0/0x46000510  read_pages+0x7c/0x23000510  page_cache_ra_order+0x244/0x3a800510  page_cache_async_ra+0x124/0x17000510  filemap_readahead.isra.0+0x58/0xa000510  filemap_get_pages+0x454/0x7b000510  filemap_read+0xdc/0x41800510  bch2_read_iter+0x100/0x1b000510  vfs_read+0x214/0x30000510  ksys_read+0x6c/0x10800510  __arm64_sys_read+0x20/0x3000510  invoke_syscall.constprop.0+0x54/0xe800510  do_el0_svc+0x44/0xc800510  el0_svc+0x18/0x5800510  el0t_64_sync_handler+0x104/0x13000510  el0t_64_sync+0x154/0x15800510 Code: d5384100 f9401c01 b9401aa3 b40002e1 (f8227881)00510 ---[ end trace 0000000000000000 ]---00510 Kernel panic - not syncing: Oops: Fatal exception00510 SMP: stopping secondary CPUs00510 Kernel Offset: disabled00510 CPU features: 0x0000,000000e0,00000410,8240500b00510 Memory Limit: noneInvestigation indicates that these bits are already set when we allocateslab page and are not zeroed out after allocation. We are not yet surewhy these crashes start happening only recently but regardless of thereason, not initializing a field that gets used later is wrong. Fix itby initializing slab->obj_exts during slab page allocation.
 漏洞公开时间：2025-05-01 22:15:40
 漏洞创建时间：2025-05-01 22:47:57
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2025-37774
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/28bef6622a1a874fe63aceeb0c684fab75afb3ae |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/8baa747193591410a853bac9c3710142dfa4937b |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/d2f5819b6ed357c0c350c0616b6b9f38be59adf6 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-37774 | https://bugzilla.suse.com/show_bug.cgi?id=1242783 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2025/CVE-2025-37774.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1242783 |
| suse_bugzilla | https://git.kernel.org/stable/c/8baa747193591410a853bac9c3710142dfa4937b | https://bugzilla.suse.com/show_bug.cgi?id=1242783 |
| suse_bugzilla | https://git.kernel.org/stable/c/28bef6622a1a874fe63aceeb0c684fab75afb3ae | https://bugzilla.suse.com/show_bug.cgi?id=1242783 |
| suse_bugzilla | https://git.kernel.org/stable/c/d2f5819b6ed357c0c350c0616b6b9f38be59adf6 | https://bugzilla.suse.com/show_bug.cgi?id=1242783 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2025-37774 | https://bugzilla.suse.com/show_bug.cgi?id=1242783 |
| suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2363309 | https://bugzilla.suse.com/show_bug.cgi?id=1242783 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2025050114-CVE-2025-37774-8b9d@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2363309 |
| anolis |  | https://anas.openanolis.cn/cves/detail/CVE-2025-37774 |

</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:slab: ensure slab-&gt;obj_exts is clear in a newly allocated slab pagektest recently reported crashes while running several buffered io testswith __alloc_tagging_slab_alloc_hook() at the top of the crash call stack.The signature indicates an invalid address dereference with low bits ofslab-&gt;obj_exts being set. The bits were outside of the range used bypage_memcg_data_flags and objext_flags and hence were not masked outby slab_obj_exts() when obtaining the pointer stored in slab-&gt;obj_exts.The typical crash log looks like this:00510 Unable to handle kernel NULL pointer dereference at virtual address 000000000000001000510 Mem abort info:00510   ESR = 0x000000009600004500510   EC = 0x25: DABT (current EL), IL = 32 bits00510   SET = 0, FnV = 000510   EA = 0, S1PTW = 000510   FSC = 0x05: level 1 translation fault00510 Data abort info:00510   ISV = 0, ISS = 0x00000045, ISS2 = 0x0000000000510   CM = 0, WnR = 1, TnD = 0, TagAccess = 000510   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 000510 user pgtable: 4k pages, 39-bit VAs, pgdp=000000010417500000510 [0000000000000010] pgd=0000000000000000, p4d=0000000000000000, pud=000000000000000000510 Internal error: Oops: 0000000096000045 [#1]  SMP00510 Modules linked in:00510 CPU: 10 UID: 0 PID: 7692 Comm: cat Not tainted 6.15.0-rc1-ktest-g189e17946605 #19327 NONE00510 Hardware name: linux,dummy-virt (DT)00510 pstate: 20001005 (nzCv daif -PAN -UAO -TCO -DIT +SSBS BTYPE=--)00510 pc : __alloc_tagging_slab_alloc_hook+0xe0/0x19000510 lr : __kmalloc_noprof+0x150/0x31000510 sp : ffffff80c87df6c000510 x29: ffffff80c87df6c0 x28: 000000000013d1ff x27: 000000000013d20000510 x26: ffffff80c87df9e0 x25: 0000000000000000 x24: 000000000000000100510 x23: ffffffc08041953c x22: 000000000000004c x21: ffffff80c000218000510 x20: fffffffec3120840 x19: ffffff80c4821000 x18: 000000000000000000510 x17: fffffffec3d02f00 x16: fffffffec3d02e00 x15: fffffffec3d0070000510 x14: fffffffec3d00600 x13: 0000000000000200 x12: 000000000000000600510 x11: ffffffc080bb86c0 x10: 0000000000000000 x9 : ffffffc080201e5800510 x8 : ffffff80c4821060 x7 : 0000000000000000 x6 : 000000005555555600510 x5 : 0000000000000001 x4 : 0000000000000010 x3 : 000000000000006000510 x2 : 0000000000000000 x1 : ffffffc080f50cf8 x0 : ffffff80d801d00000510 Call trace:00510  __alloc_tagging_slab_alloc_hook+0xe0/0x190 (P)00510  __kmalloc_noprof+0x150/0x31000510  __bch2_folio_create+0x5c/0xf800510  bch2_folio_create+0x2c/0x4000510  bch2_readahead+0xc0/0x46000510  read_pages+0x7c/0x23000510  page_cache_ra_order+0x244/0x3a800510  page_cache_async_ra+0x124/0x17000510  filemap_readahead.isra.0+0x58/0xa000510  filemap_get_pages+0x454/0x7b000510  filemap_read+0xdc/0x41800510  bch2_read_iter+0x100/0x1b000510  vfs_read+0x214/0x30000510  ksys_read+0x6c/0x10800510  __arm64_sys_read+0x20/0x3000510  invoke_syscall.constprop.0+0x54/0xe800510  do_el0_svc+0x44/0xc800510  el0_svc+0x18/0x5800510  el0t_64_sync_handler+0x104/0x13000510  el0t_64_sync+0x154/0x15800510 Code: d5384100 f9401c01 b9401aa3 b40002e1 (f8227881)00510 ---[ end trace 0000000000000000 ]---00510 Kernel panic - not syncing: Oops: Fatal exception00510 SMP: stopping secondary CPUs00510 Kernel Offset: disabled00510 CPU features: 0x0000,000000e0,00000410,8240500b00510 Memory Limit: noneInvestigation indicates that these bits are already set when we allocateslab page and are not zeroed out after allocation. We are not yet surewhy these crashes start happening only recently but regardless of thereason, not initializing a field that gets used later is wrong. Fix itby initializing slab-&gt;obj_exts during slab page allocation.The Linux kernel CVE team has assigned CVE-2025-37774 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.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):不受影响
8.openEuler-24.03-LTS-SP2(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):否
8.openEuler-24.03-LTS-SP2(6.6.0):否

原因说明：
  1.master(6.6.0):不受影响-漏洞代码不能被攻击者触发
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

内容风险标识

评论 (5)

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

内容风险标识

CVE-2025-37774

评论 (5)

搜索帮助

src-openEuler/kernel