CVE-2024-46789

一、漏洞信息
 漏洞编号：[CVE-2024-46789](https://nvd.nist.gov/vuln/detail/CVE-2024-46789)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0,6.6.0
 CVSS V3.0分值：
  BaseScore：0.0 None
  Vector：CVSS：3.0/
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:mm/slub: add check for s->flags in the alloc_tagging_slab_free_hookWhen enable CONFIG_MEMCG & CONFIG_KFENCE & CONFIG_KMEMLEAK, the followingwarning always occurs,This is because the following call stack occurred:mem_pool_alloc    kmem_cache_alloc_noprof        slab_alloc_node            kfence_allocOnce the kfence allocation is successful,slab->obj_exts will not be empty,because it has already been assigned a value in kfence_init_pool.Since in the prepare_slab_obj_exts_hook function,we perform a check fors->flags & (SLAB_NO_OBJ_EXT | SLAB_NOLEAKTRACE),the alloc_tag_add functionwill not be called as a result.Therefore,ref->ct remains NULL.However,when we call mem_pool_free,since obj_ext is not empty, iteventually leads to the alloc_tag_sub scenario being invoked.  This iswhere the warning occurs.So we should add corresponding checks in the alloc_tagging_slab_free_hook.For __GFP_NO_OBJ_EXT case,I didn t see the specific case where it s usingkfence,so I won t add the corresponding check inalloc_tagging_slab_free_hook for now.[    3.734349] ------------[ cut here ]------------[    3.734807] alloc_tag was not set[    3.735129] WARNING: CPU: 4 PID: 40 at ./include/linux/alloc_tag.h:130 kmem_cache_free+0x444/0x574[    3.735866] Modules linked in: autofs4[    3.736211] CPU: 4 UID: 0 PID: 40 Comm: ksoftirqd/4 Tainted: G        W          6.11.0-rc3-dirty #1[    3.736969] Tainted: [W]=WARN[    3.737258] Hardware name: QEMU KVM Virtual Machine, BIOS unknown 2/2/2022[    3.737875] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)[    3.738501] pc : kmem_cache_free+0x444/0x574[    3.738951] lr : kmem_cache_free+0x444/0x574[    3.739361] sp : ffff80008357bb60[    3.739693] x29: ffff80008357bb70 x28: 0000000000000000 x27: 0000000000000000[    3.740338] x26: ffff80008207f000 x25: ffff000b2eb2fd60 x24: ffff0000c0005700[    3.740982] x23: ffff8000804229e4 x22: ffff800082080000 x21: ffff800081756000[    3.741630] x20: fffffd7ff8253360 x19: 00000000000000a8 x18: ffffffffffffffff[    3.742274] x17: ffff800ab327f000 x16: ffff800083398000 x15: ffff800081756df0[    3.742919] x14: 0000000000000000 x13: 205d344320202020 x12: 5b5d373038343337[    3.743560] x11: ffff80008357b650 x10: 000000000000005d x9 : 00000000ffffffd0[    3.744231] x8 : 7f7f7f7f7f7f7f7f x7 : ffff80008237bad0 x6 : c0000000ffff7fff[    3.744907] x5 : ffff80008237ba78 x4 : ffff8000820bbad0 x3 : 0000000000000001[    3.745580] x2 : 68d66547c09f7800 x1 : 68d66547c09f7800 x0 : 0000000000000000[    3.746255] Call trace:[    3.746530]  kmem_cache_free+0x444/0x574[    3.746931]  mem_pool_free+0x44/0xf4[    3.747306]  free_object_rcu+0xc8/0xdc[    3.747693]  rcu_do_batch+0x234/0x8a4[    3.748075]  rcu_core+0x230/0x3e4[    3.748424]  rcu_core_si+0x14/0x1c[    3.748780]  handle_softirqs+0x134/0x378[    3.749189]  run_ksoftirqd+0x70/0x9c[    3.749560]  smpboot_thread_fn+0x148/0x22c[    3.749978]  kthread+0x10c/0x118[    3.750323]  ret_from_fork+0x10/0x20[    3.750696] ---[ end trace 0000000000000000 ]---
 漏洞公开时间：2024-09-18 16:15:05
 漏洞创建时间：2024-09-18 17:18:48
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-46789
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/2d476c86ba4745fcbc912ce4627df4fa80caa9ad |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ab7ca09520e9c41c219a4427fe0dae24024bfe7f |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-46789 | https://bugzilla.suse.com/show_bug.cgi?id=1230816 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-46789.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1230816 |
| suse_bugzilla | https://git.kernel.org/stable/c/2d476c86ba4745fcbc912ce4627df4fa80caa9ad | https://bugzilla.suse.com/show_bug.cgi?id=1230816 |
| suse_bugzilla | https://git.kernel.org/stable/c/ab7ca09520e9c41c219a4427fe0dae24024bfe7f | https://bugzilla.suse.com/show_bug.cgi?id=1230816 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-46789 | https://bugzilla.suse.com/show_bug.cgi?id=1230816 |
| suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2313137 | https://bugzilla.suse.com/show_bug.cgi?id=1230816 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-46789 |
| anolis |  | https://anas.openanolis.cn/cves/detail/CVE-2024-46789 |
| amazon_linux_explore | https://access.redhat.com/security/cve/CVE-2024-46789 | https://explore.alas.aws.amazon.com/CVE-2024-46789.html |
| amazon_linux_explore | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-46789 | https://explore.alas.aws.amazon.com/CVE-2024-46789.html |

</details>

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

无
</details>

二、漏洞分析结构反馈
 影响性分析说明：
  Reserved.
 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-20.03-LTS-SP4(4.19.90):不受影响
2.openEuler-22.03-LTS-SP1(5.10.0):不受影响
3.openEuler-22.03-LTS-SP3(5.10.0):不受影响
4.openEuler-22.03-LTS-SP4(5.10.0):不受影响
5.master(6.6.0):不受影响
6.openEuler-24.03-LTS(6.6.0):不受影响
7.openEuler-24.03-LTS-Next(6.6.0):不受影响

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

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-SP1(5.10.0):
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-Next(6.6.0):

修复是否涉及abi变化(是/否)：
1.master(6.6.0):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP1(5.10.0):
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-Next(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-2024-46789	None	None	https://git.kernel.org/stable/c/ab7ca09520e9c41c219a4427fe0dae24024bfe7f https://git.kernel.org/stable/c/2d476c86ba4745fcbc912ce4627df4fa80caa9ad
https://ubuntu.com/security/CVE-2024-46789	None	None	https://discourse.ubuntu.com/c/ubuntu-pro
https://www.opencve.io/cve/CVE-2024-46789	None	None	https://git.kernel.org/stable/c/ab7ca09520e9c41c219a4427fe0dae24024bfe7f https://git.kernel.org/stable/c/2d476c86ba4745fcbc912ce4627df4fa80caa9ad
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2024-46789
https://security-tracker.debian.org/tracker/CVE-2024-46789	None	None	https://git.kernel.org/linus/ab7ca09520e9c41c219a4427fe0dae24024bfe7f

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用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-2024-46789

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

mm/slub: add check for s-&gt;flags in the alloc_tagging_slab_free_hook

When enable CONFIG_MEMCG &#38; CONFIG_KFENCE &#38; CONFIG_KMEMLEAK, the following
warning always occurs,This is because the following call stack occurred:
mem_pool_alloc
    kmem_cache_alloc_noprof
        slab_alloc_node
            kfence_alloc

Once the kfence allocation is successful,slab-&gt;obj_exts will not be empty,
because it has already been assigned a value in kfence_init_pool.

Since in the prepare_slab_obj_exts_hook function,we perform a check for
s-&gt;flags &#38; (SLAB_NO_OBJ_EXT | SLAB_NOLEAKTRACE),the alloc_tag_add function
will not be called as a result.Therefore,ref-&gt;ct remains NULL.

However,when we call mem_pool_free,since obj_ext is not empty, it
eventually leads to the alloc_tag_sub scenario being invoked.  This is
where the warning occurs.

So we should add corresponding checks in the alloc_tagging_slab_free_hook.
For __GFP_NO_OBJ_EXT case,I didn&#39;t see the specific case where it&#39;s using
kfence,so I won&#39;t add the corresponding check in
alloc_tagging_slab_free_hook for now.

[    3.734349] ------------[ cut here ]------------
[    3.734807] alloc_tag was not set
[    3.735129] WARNING: CPU: 4 PID: 40 at ./include/linux/alloc_tag.h:130 kmem_cache_free+0x444/0x574
[    3.735866] Modules linked in: autofs4
[    3.736211] CPU: 4 UID: 0 PID: 40 Comm: ksoftirqd/4 Tainted: G        W          6.11.0-rc3-dirty #1
[    3.736969] Tainted: [W]=WARN
[    3.737258] Hardware name: QEMU KVM Virtual Machine, BIOS unknown 2/2/2022
[    3.737875] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    3.738501] pc : kmem_cache_free+0x444/0x574
[    3.738951] lr : kmem_cache_free+0x444/0x574
[    3.739361] sp : ffff80008357bb60
[    3.739693] x29: ffff80008357bb70 x28: 0000000000000000 x27: 0000000000000000
[    3.740338] x26: ffff80008207f000 x25: ffff000b2eb2fd60 x24: ffff0000c0005700
[    3.740982] x23: ffff8000804229e4 x22: ffff800082080000 x21: ffff800081756000
[    3.741630] x20: fffffd7ff8253360 x19: 00000000000000a8 x18: ffffffffffffffff
[    3.742274] x17: ffff800ab327f000 x16: ffff800083398000 x15: ffff800081756df0
[    3.742919] x14: 0000000000000000 x13: 205d344320202020 x12: 5b5d373038343337
[    3.743560] x11: ffff80008357b650 x10: 000000000000005d x9 : 00000000ffffffd0
[    3.744231] x8 : 7f7f7f7f7f7f7f7f x7 : ffff80008237bad0 x6 : c0000000ffff7fff
[    3.744907] x5 : ffff80008237ba78 x4 : ffff8000820bbad0 x3 : 0000000000000001
[    3.745580] x2 : 68d66547c09f7800 x1 : 68d66547c09f7800 x0 : 0000000000000000
[    3.746255] Call trace:
[    3.746530]  kmem_cache_free+0x444/0x574
[    3.746931]  mem_pool_free+0x44/0xf4
[    3.747306]  free_object_rcu+0xc8/0xdc
[    3.747693]  rcu_do_batch+0x234/0x8a4
[    3.748075]  rcu_core+0x230/0x3e4
[    3.748424]  rcu_core_si+0x14/0x1c
[    3.748780]  handle_softirqs+0x134/0x378
[    3.749189]  run_ksoftirqd+0x70/0x9c
[    3.749560]  smpboot_thread_fn+0x148/0x22c
[    3.749978]  kthread+0x10c/0x118
[    3.750323]  ret_from_fork+0x10/0x20
[    3.750696] ---[ end trace 0000000000000000 ]---

The Linux kernel CVE team has assigned CVE-2024-46789 to this issue.

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

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

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

@ 经过 cve-manager 解析, 已分析的内容如下表所示:

状态	需分析	内容
已分析	1.影响性分析说明	In the Linux kernel, the following vulnerability has been resolved:mm/slub: add check for s->flags in the alloc_tagging_slab_free_hookWhen enable CONFIG_MEMCG & CONFIG_KFENCE & CONFIG_KMEMLEAK, the followingwarning always occurs,This is because the following call stack occurred:mem_pool_alloc kmem_cache_alloc_noprof slab_alloc_node kfence_allocOnce the kfence allocation is successful,slab->obj_exts will not be empty,because it has already been assigned a value in kfence_init_pool.Since in the prepare_slab_obj_exts_hook function,we perform a check fors->flags & (SLAB_NO_OBJ_EXT
已分析	2.openEulerScore	3.9
已分析	3.openEulerVector	AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
已分析	4.受影响版本排查	openEuler-20.03-LTS-SP4:不受影响,openEuler-22.03-LTS-SP1:不受影响,openEuler-22.03-LTS-SP3:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响
已分析	5.修复是否涉及abi变化	openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否

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