CVE-2024-50084

一、漏洞信息
漏洞编号：CVE-2024-50084
漏洞归属组件：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：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:net: microchip: vcap api: Fix memory leaks in vcap_api_encode_rule_test()Commit a3c1e45156ad ( net: microchip: vcap: Fix use-after-free error inkunit test ) fixed the use-after-free error, but introduced belowmemory leaks by removing necessary vcap_free_rule(), add it to fix it. unreferenced object 0xffffff80ca58b700 (size 192): comm kunit_try_catch , pid 1215, jiffies 4294898264 hex dump (first 32 bytes): 00 12 7a 00 05 00 00 00 0a 00 00 00 64 00 00 00 ..z.........d... 00 00 00 00 00 00 00 00 00 04 0b cc 80 ff ff ff ................ backtrace (crc 9c09c3fe): [<0000000052a0be73>] kmemleak_alloc+0x34/0x40 [<0000000043605459>] __kmalloc_cache_noprof+0x26c/0x2f4 [<0000000040a01b8d>] vcap_alloc_rule+0x3cc/0x9c4 [<000000003fe86110>] vcap_api_encode_rule_test+0x1ac/0x16b0 [<00000000b3595fc4>] kunit_try_run_case+0x13c/0x3ac [<0000000010f5d2bf>] kunit_generic_run_threadfn_adapter+0x80/0xec [<00000000c5d82c9a>] kthread+0x2e8/0x374 [<00000000f4287308>] ret_from_fork+0x10/0x20 unreferenced object 0xffffff80cc0b0400 (size 64): comm kunit_try_catch , pid 1215, jiffies 4294898265 hex dump (first 32 bytes): 80 04 0b cc 80 ff ff ff 18 b7 58 ca 80 ff ff ff ..........X..... 39 00 00 00 02 00 00 00 06 05 04 03 02 01 ff ff 9............... backtrace (crc daf014e9): [<0000000052a0be73>] kmemleak_alloc+0x34/0x40 [<0000000043605459>] __kmalloc_cache_noprof+0x26c/0x2f4 [<000000000ff63fd4>] vcap_rule_add_key+0x2cc/0x528 [<00000000dfdb1e81>] vcap_api_encode_rule_test+0x224/0x16b0 [<00000000b3595fc4>] kunit_try_run_case+0x13c/0x3ac [<0000000010f5d2bf>] kunit_generic_run_threadfn_adapter+0x80/0xec [<00000000c5d82c9a>] kthread+0x2e8/0x374 [<00000000f4287308>] ret_from_fork+0x10/0x20 unreferenced object 0xffffff80cc0b0700 (size 64): comm kunit_try_catch , pid 1215, jiffies 4294898265 hex dump (first 32 bytes): 80 07 0b cc 80 ff ff ff 28 b7 58 ca 80 ff ff ff ........(.X..... 3c 00 00 00 00 00 00 00 01 2f 03 b3 ec ff ff ff <......../...... backtrace (crc 8d877792): [<0000000052a0be73>] kmemleak_alloc+0x34/0x40 [<0000000043605459>] __kmalloc_cache_noprof+0x26c/0x2f4 [<000000006eadfab7>] vcap_rule_add_action+0x2d0/0x52c [<00000000323475d1>] vcap_api_encode_rule_test+0x4d4/0x16b0 [<00000000b3595fc4>] kunit_try_run_case+0x13c/0x3ac [<0000000010f5d2bf>] kunit_generic_run_threadfn_adapter+0x80/0xec [<00000000c5d82c9a>] kthread+0x2e8/0x374 [<00000000f4287308>] ret_from_fork+0x10/0x20 unreferenced object 0xffffff80cc0b0900 (size 64): comm kunit_try_catch , pid 1215, jiffies 4294898266 hex dump (first 32 bytes): 80 09 0b cc 80 ff ff ff 80 06 0b cc 80 ff ff ff ................ 7d 00 00 00 01 00 00 00 00 00 00 00 ff 00 00 00 }............... backtrace (crc 34181e56): [<0000000052a0be73>] kmemleak_alloc+0x34/0x40 [<0000000043605459>] __kmalloc_cache_noprof+0x26c/0x2f4 [<000000000ff63fd4>] vcap_rule_add_key+0x2cc/0x528 [<00000000991e3564>] vcap_val_rule+0xcf0/0x13e8 [<00000000fc9868e5>] vcap_api_encode_rule_test+0x678/0x16b0 [<00000000b3595fc4>] kunit_try_run_case+0x13c/0x3ac [<0000000010f5d2bf>] kunit_generic_run_threadfn_adapter+0x80/0xec [<00000000c5d82c9a>] kthread+0x2e8/0x374 [<00000000f4287308>] ret_from_fork+0x10/0x20 unreferenced object 0xffffff80cc0b0980 (size 64): comm kunit_try_catch , pid 1215, jiffies 4294898266 hex dump (first 32 bytes): 18 b7 58 ca 80 ff ff ff 00 09 0b cc 80 ff ff ff ..X............. 67 00 00 00 00 00 00 00 01 01 74 88 c0 ff ff ff g.........t..... backtrace (crc 275fd9be): [<0000000052a0be73>] kmemleak_alloc+0x34/0x40 [<0000000043605459>] __kmalloc_cache_noprof+0x26c/0x2f4 [<000000000ff63fd4>] vcap_rule_add_key+0x2cc/0x528 [<000000001396a1a2>] test_add_de---truncated---
漏洞公开时间：2024-10-29 09:15:05
漏洞创建时间：2024-10-29 09:28:53
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2024-50084

更多参考(点击展开)

参考来源	参考链接	来源链接
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/170792097bb21e5da77443b6a03d35489813eabe
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/20b5342de51bda794791e013b90754774003a515
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/217a3d98d1e9891a8b1438a27dfbc64ddf01f691
suse_bugzilla	http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-50084	https://bugzilla.suse.com/show_bug.cgi?id=1232494
suse_bugzilla	https://www.cve.org/CVERecord?id=CVE-2024-50084	https://bugzilla.suse.com/show_bug.cgi?id=1232494
suse_bugzilla	https://git.kernel.org/stable/c/170792097bb21e5da77443b6a03d35489813eabe	https://bugzilla.suse.com/show_bug.cgi?id=1232494
suse_bugzilla	https://git.kernel.org/stable/c/20b5342de51bda794791e013b90754774003a515	https://bugzilla.suse.com/show_bug.cgi?id=1232494
suse_bugzilla	https://git.kernel.org/stable/c/217a3d98d1e9891a8b1438a27dfbc64ddf01f691	https://bugzilla.suse.com/show_bug.cgi?id=1232494
suse_bugzilla	https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-50084.mbox	https://bugzilla.suse.com/show_bug.cgi?id=1232494
redhat_bugzilla	https://lore.kernel.org/linux-cve-announce/2024102937-CVE-2024-50084-daf1@gregkh/T	https://bugzilla.redhat.com/show_bug.cgi?id=2322304
debian		https://security-tracker.debian.org/tracker/CVE-2024-50084
cve_search		https://git.kernel.org/stable/c/20b5342de51bda794791e013b90754774003a515
cve_search		https://git.kernel.org/stable/c/170792097bb21e5da77443b6a03d35489813eabe
cve_search		https://git.kernel.org/stable/c/217a3d98d1e9891a8b1438a27dfbc64ddf01f691

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

详情(点击展开)

影响的包	修复版本	修复补丁	问题引入补丁	来源
		https://git.kernel.org/stable/c/170792097bb21e5da77443b6a03d35489813eabe		nvd
		https://git.kernel.org/stable/c/20b5342de51bda794791e013b90754774003a515		nvd
		https://git.kernel.org/stable/c/217a3d98d1e9891a8b1438a27dfbc64ddf01f691		nvd

二、漏洞分析结构反馈
影响性分析说明：
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-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.master(6.6.0):不受影响
6.openEuler-24.03-LTS-Next(6.6.0):不受影响
7.openEuler-24.03-LTS-SP1(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):否
8.openEuler-24.03-LTS-SP1(6.6.0):否

原因说明：
1.openEuler-24.03-LTS(6.6.0):正常修复
2.master(6.6.0):不受影响-漏洞代码不能被攻击者触发
3.openEuler-24.03-LTS-Next(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-SP1(6.6.0):不受影响-漏洞代码不存在

@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):

原因说明：
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

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.

CVE-2024-50084

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

net: microchip: vcap api: Fix memory leaks in vcap_api_encode_rule_test()

Commit a3c1e45156ad ("net: microchip: vcap: Fix use-after-free error in
kunit test") fixed the use-after-free error, but introduced below
memory leaks by removing necessary vcap_free_rule(), add it to fix it.

unreferenced object 0xffffff80ca58b700 (size 192):
  comm &#34;kunit_try_catch&#34;, pid 1215, jiffies 4294898264
  hex dump (first 32 bytes):
    00 12 7a 00 05 00 00 00 0a 00 00 00 64 00 00 00  ..z.........d...
    00 00 00 00 00 00 00 00 00 04 0b cc 80 ff ff ff  ................
  backtrace (crc 9c09c3fe):
    [&lt;0000000052a0be73&gt;] kmemleak_alloc+0x34/0x40
    [&lt;0000000043605459&gt;] __kmalloc_cache_noprof+0x26c/0x2f4
    [&lt;0000000040a01b8d&gt;] vcap_alloc_rule+0x3cc/0x9c4
    [&lt;000000003fe86110&gt;] vcap_api_encode_rule_test+0x1ac/0x16b0
    [&lt;00000000b3595fc4&gt;] kunit_try_run_case+0x13c/0x3ac
    [&lt;0000000010f5d2bf&gt;] kunit_generic_run_threadfn_adapter+0x80/0xec
    [&lt;00000000c5d82c9a&gt;] kthread+0x2e8/0x374
    [&lt;00000000f4287308&gt;] ret_from_fork+0x10/0x20
unreferenced object 0xffffff80cc0b0400 (size 64):
  comm &#34;kunit_try_catch&#34;, pid 1215, jiffies 4294898265
  hex dump (first 32 bytes):
    80 04 0b cc 80 ff ff ff 18 b7 58 ca 80 ff ff ff  ..........X.....
    39 00 00 00 02 00 00 00 06 05 04 03 02 01 ff ff  9...............
  backtrace (crc daf014e9):
    [&lt;0000000052a0be73&gt;] kmemleak_alloc+0x34/0x40
    [&lt;0000000043605459&gt;] __kmalloc_cache_noprof+0x26c/0x2f4
    [&lt;000000000ff63fd4&gt;] vcap_rule_add_key+0x2cc/0x528
    [&lt;00000000dfdb1e81&gt;] vcap_api_encode_rule_test+0x224/0x16b0
    [&lt;00000000b3595fc4&gt;] kunit_try_run_case+0x13c/0x3ac
    [&lt;0000000010f5d2bf&gt;] kunit_generic_run_threadfn_adapter+0x80/0xec
    [&lt;00000000c5d82c9a&gt;] kthread+0x2e8/0x374
    [&lt;00000000f4287308&gt;] ret_from_fork+0x10/0x20
unreferenced object 0xffffff80cc0b0700 (size 64):
  comm &#34;kunit_try_catch&#34;, pid 1215, jiffies 4294898265
  hex dump (first 32 bytes):
    80 07 0b cc 80 ff ff ff 28 b7 58 ca 80 ff ff ff  ........(.X.....
    3c 00 00 00 00 00 00 00 01 2f 03 b3 ec ff ff ff  &lt;......../......
  backtrace (crc 8d877792):
    [&lt;0000000052a0be73&gt;] kmemleak_alloc+0x34/0x40
    [&lt;0000000043605459&gt;] __kmalloc_cache_noprof+0x26c/0x2f4
    [&lt;000000006eadfab7&gt;] vcap_rule_add_action+0x2d0/0x52c
    [&lt;00000000323475d1&gt;] vcap_api_encode_rule_test+0x4d4/0x16b0
    [&lt;00000000b3595fc4&gt;] kunit_try_run_case+0x13c/0x3ac
    [&lt;0000000010f5d2bf&gt;] kunit_generic_run_threadfn_adapter+0x80/0xec
    [&lt;00000000c5d82c9a&gt;] kthread+0x2e8/0x374
    [&lt;00000000f4287308&gt;] ret_from_fork+0x10/0x20
unreferenced object 0xffffff80cc0b0900 (size 64):
  comm &#34;kunit_try_catch&#34;, pid 1215, jiffies 4294898266
  hex dump (first 32 bytes):
    80 09 0b cc 80 ff ff ff 80 06 0b cc 80 ff ff ff  ................
    7d 00 00 00 01 00 00 00 00 00 00 00 ff 00 00 00  }...............
  backtrace (crc 34181e56):
    [&lt;0000000052a0be73&gt;] kmemleak_alloc+0x34/0x40
    [&lt;0000000043605459&gt;] __kmalloc_cache_noprof+0x26c/0x2f4
    [&lt;000000000ff63fd4&gt;] vcap_rule_add_key+0x2cc/0x528
    [&lt;00000000991e3564&gt;] vcap_val_rule+0xcf0/0x13e8
    [&lt;00000000fc9868e5&gt;] vcap_api_encode_rule_test+0x678/0x16b0
    [&lt;00000000b3595fc4&gt;] kunit_try_run_case+0x13c/0x3ac
    [&lt;0000000010f5d2bf&gt;] kunit_generic_run_threadfn_adapter+0x80/0xec
    [&lt;00000000c5d82c9a&gt;] kthread+0x2e8/0x374
    [&lt;00000000f4287308&gt;] ret_from_fork+0x10/0x20
unreferenced object 0xffffff80cc0b0980 (size 64):
  comm &#34;kunit_try_catch&#34;, pid 1215, jiffies 4294898266
  hex dump (first 32 bytes):
    18 b7 58 ca 80 ff ff ff 00 09 0b cc 80 ff ff ff  ..X.............
    67 00 00 00 00 00 00 00 01 01 74 88 c0 ff ff ff  g.........t.....
  backtrace (crc 275fd9be):
    [&lt;0000000052a0be73&gt;] kmemleak_alloc+0x34/0x40
    [&lt;0000000043605459&gt;] __kmalloc_cache_noprof+0x26c/0x2f4
    [&lt;000000000ff63fd4&gt;] vcap_rule_add_key+0x2cc/0x528
    [&lt;000000001396a1a2&gt;] test_add_def_fields+0xb0/0x100
    [&lt;000000006e7621f0&gt;] vcap_val_rule+0xa98/0x13e8
    [&lt;00000000fc9868e5&gt;] vcap_api_encode_rule_test+0x678/0x16b0
    [&lt;00000000b3595fc4&gt;] kunit_try_run_case+0x13c/0x3ac
    [&lt;0000000010f5d2bf&gt;] kunit_generic_run_threadfn_adapter+0x80/0xec
    [&lt;00000000c5d82c9a&gt;] kthread+0x2e8/0x374
    [&lt;00000000f4287308&gt;] ret_from_fork+0x10/0x20
......

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

openEuler评分:(评分和向量)
5.5
CVSS:3.1/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-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-2024-50084

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

net: microchip: vcap api: Fix memory leaks in vcap_api_encode_rule_test()

Commit a3c1e45156ad ("net: microchip: vcap: Fix use-after-free error in
kunit test") fixed the use-after-free error, but introduced below
memory leaks by removing necessary vcap_free_rule(), add it to fix it.

unreferenced object 0xffffff80ca58b700 (size 192):
  comm &#34;kunit_try_catch&#34;, pid 1215, jiffies 4294898264
  hex dump (first 32 bytes):
    00 12 7a 00 05 00 00 00 0a 00 00 00 64 00 00 00  ..z.........d...
    00 00 00 00 00 00 00 00 00 04 0b cc 80 ff ff ff  ................
  backtrace (crc 9c09c3fe):
    [&lt;0000000052a0be73&gt;] kmemleak_alloc+0x34/0x40
    [&lt;0000000043605459&gt;] __kmalloc_cache_noprof+0x26c/0x2f4
    [&lt;0000000040a01b8d&gt;] vcap_alloc_rule+0x3cc/0x9c4
    [&lt;000000003fe86110&gt;] vcap_api_encode_rule_test+0x1ac/0x16b0
    [&lt;00000000b3595fc4&gt;] kunit_try_run_case+0x13c/0x3ac
    [&lt;0000000010f5d2bf&gt;] kunit_generic_run_threadfn_adapter+0x80/0xec
    [&lt;00000000c5d82c9a&gt;] kthread+0x2e8/0x374
    [&lt;00000000f4287308&gt;] ret_from_fork+0x10/0x20
unreferenced object 0xffffff80cc0b0400 (size 64):
  comm &#34;kunit_try_catch&#34;, pid 1215, jiffies 4294898265
  hex dump (first 32 bytes):
    80 04 0b cc 80 ff ff ff 18 b7 58 ca 80 ff ff ff  ..........X.....
    39 00 00 00 02 00 00 00 06 05 04 03 02 01 ff ff  9...............
  backtrace (crc daf014e9):
    [&lt;0000000052a0be73&gt;] kmemleak_alloc+0x34/0x40
    [&lt;0000000043605459&gt;] __kmalloc_cache_noprof+0x26c/0x2f4
    [&lt;000000000ff63fd4&gt;] vcap_rule_add_key+0x2cc/0x528
    [&lt;00000000dfdb1e81&gt;] vcap_api_encode_rule_test+0x224/0x16b0
    [&lt;00000000b3595fc4&gt;] kunit_try_run_case+0x13c/0x3ac
    [&lt;0000000010f5d2bf&gt;] kunit_generic_run_threadfn_adapter+0x80/0xec
    [&lt;00000000c5d82c9a&gt;] kthread+0x2e8/0x374
    [&lt;00000000f4287308&gt;] ret_from_fork+0x10/0x20
unreferenced object 0xffffff80cc0b0700 (size 64):
  comm &#34;kunit_try_catch&#34;, pid 1215, jiffies 4294898265
  hex dump (first 32 bytes):
    80 07 0b cc 80 ff ff ff 28 b7 58 ca 80 ff ff ff  ........(.X.....
    3c 00 00 00 00 00 00 00 01 2f 03 b3 ec ff ff ff  &lt;......../......
  backtrace (crc 8d877792):
    [&lt;0000000052a0be73&gt;] kmemleak_alloc+0x34/0x40
    [&lt;0000000043605459&gt;] __kmalloc_cache_noprof+0x26c/0x2f4
    [&lt;000000006eadfab7&gt;] vcap_rule_add_action+0x2d0/0x52c
    [&lt;00000000323475d1&gt;] vcap_api_encode_rule_test+0x4d4/0x16b0
    [&lt;00000000b3595fc4&gt;] kunit_try_run_case+0x13c/0x3ac
    [&lt;0000000010f5d2bf&gt;] kunit_generic_run_threadfn_adapter+0x80/0xec
    [&lt;00000000c5d82c9a&gt;] kthread+0x2e8/0x374
    [&lt;00000000f4287308&gt;] ret_from_fork+0x10/0x20
unreferenced object 0xffffff80cc0b0900 (size 64):
  comm &#34;kunit_try_catch&#34;, pid 1215, jiffies 4294898266
  hex dump (first 32 bytes):
    80 09 0b cc 80 ff ff ff 80 06 0b cc 80 ff ff ff  ................
    7d 00 00 00 01 00 00 00 00 00 00 00 ff 00 00 00  }...............
  backtrace (crc 34181e56):
    [&lt;0000000052a0be73&gt;] kmemleak_alloc+0x34/0x40
    [&lt;0000000043605459&gt;] __kmalloc_cache_noprof+0x26c/0x2f4
    [&lt;000000000ff63fd4&gt;] vcap_rule_add_key+0x2cc/0x528
    [&lt;00000000991e3564&gt;] vcap_val_rule+0xcf0/0x13e8
    [&lt;00000000fc9868e5&gt;] vcap_api_encode_rule_test+0x678/0x16b0
    [&lt;00000000b3595fc4&gt;] kunit_try_run_case+0x13c/0x3ac
    [&lt;0000000010f5d2bf&gt;] kunit_generic_run_threadfn_adapter+0x80/0xec
    [&lt;00000000c5d82c9a&gt;] kthread+0x2e8/0x374
    [&lt;00000000f4287308&gt;] ret_from_fork+0x10/0x20
unreferenced object 0xffffff80cc0b0980 (size 64):
  comm &#34;kunit_try_catch&#34;, pid 1215, jiffies 4294898266
  hex dump (first 32 bytes):
    18 b7 58 ca 80 ff ff ff 00 09 0b cc 80 ff ff ff  ..X.............
    67 00 00 00 00 00 00 00 01 01 74 88 c0 ff ff ff  g.........t.....
  backtrace (crc 275fd9be):
    [&lt;0000000052a0be73&gt;] kmemleak_alloc+0x34/0x40
    [&lt;0000000043605459&gt;] __kmalloc_cache_noprof+0x26c/0x2f4
    [&lt;000000000ff63fd4&gt;] vcap_rule_add_key+0x2cc/0x528
    [&lt;000000001396a1a2&gt;] test_add_def_fields+0xb0/0x100
    [&lt;000000006e7621f0&gt;] vcap_val_rule+0xa98/0x13e8
    [&lt;00000000fc9868e5&gt;] vcap_api_encode_rule_test+0x678/0x16b0
    [&lt;00000000b3595fc4&gt;] kunit_try_run_case+0x13c/0x3ac
    [&lt;0000000010f5d2bf&gt;] kunit_generic_run_threadfn_adapter+0x80/0xec
    [&lt;00000000c5d82c9a&gt;] kthread+0x2e8/0x374
    [&lt;00000000f4287308&gt;] ret_from_fork+0x10/0x20
......

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

openEuler评分:(评分和向量)
5.5
CVSS:3.1/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-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-2024-50084

影响性分析说明：
Reserved.

openEuler评分:(评分和向量)
3.9
CVSS: 3.1/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-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:不受影响

原因说明:
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:不受影响-漏洞代码不存在

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

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

CVE-2024-50084

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

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

状态	分析项目	内容
已分析	1.影响性分析说明	Reserved.
已分析	2.openEulerScore	5.5
已分析	3.openEulerVector	AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
已分析	4.受影响版本排查	openEuler-24.03-LTS:受影响,openEuler-20.03-LTS-SP4:不受影响,openEuler-22.03-LTS-SP3:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-24.03-LTS-Next:不受影响,openEuler-24.03-LTS-SP1:不受影响
已分析	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:否,openEuler-24.03-LTS-SP1:否
已分析	6.原因说明	openEuler-24.03-LTS:正常修复,master:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发,openEuler-20.03-LTS-SP4:不受影响-漏洞代码不存在,openEuler-22.03-LTS-SP3:不受影响-漏洞代码不存在,openEuler-22.03-LTS-SP4:不受影响-漏洞代码不存在,openEuler-24.03-LTS-SP1:不受影响-漏洞代码不存在

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

src-openEuler/kernel

内容风险标识

评论 (13)

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

内容风险标识

CVE-2024-50084

评论 (13)

搜索帮助

src-openEuler/kernel