CVE-2024-50301

一、漏洞信息
 漏洞编号：[CVE-2024-50301](https://nvd.nist.gov/vuln/detail/CVE-2024-50301)
 漏洞归属组件：[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：7.1 High
  Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:security/keys: fix slab-out-of-bounds in key_task_permissionKASAN reports an out of bounds read:BUG: KASAN: slab-out-of-bounds in __kuid_val include/linux/uidgid.h:36BUG: KASAN: slab-out-of-bounds in uid_eq include/linux/uidgid.h:63 [inline]BUG: KASAN: slab-out-of-bounds in key_task_permission+0x394/0x410security/keys/permission.c:54Read of size 4 at addr ffff88813c3ab618 by task stress-ng/4362CPU: 2 PID: 4362 Comm: stress-ng Not tainted 5.10.0-14930-gafbffd6c3ede #15Call Trace: __dump_stack lib/dump_stack.c:82 [inline] dump_stack+0x107/0x167 lib/dump_stack.c:123 print_address_description.constprop.0+0x19/0x170 mm/kasan/report.c:400 __kasan_report.cold+0x6c/0x84 mm/kasan/report.c:560 kasan_report+0x3a/0x50 mm/kasan/report.c:585 __kuid_val include/linux/uidgid.h:36 [inline] uid_eq include/linux/uidgid.h:63 [inline] key_task_permission+0x394/0x410 security/keys/permission.c:54 search_nested_keyrings+0x90e/0xe90 security/keys/keyring.c:793This issue was also reported by syzbot.It can be reproduced by following these steps(more details [1]):1. Obtain more than 32 inputs that have similar hashes, which ends with the   pattern  0xxxxxxxe6 .2. Reboot and add the keys obtained in step 1.The reproducer demonstrates how this issue happened:1. In the search_nested_keyrings function, when it iterates through the   slots in a node(below tag ascend_to_node), if the slot pointer is meta   and node->back_pointer != NULL(it means a root), it will proceed to   descend_to_node. However, there is an exception. If node is the root,   and one of the slots points to a shortcut, it will be treated as a   keyring.2. Whether the ptr is keyring decided by keyring_ptr_is_keyring function.   However, KEYRING_PTR_SUBTYPE is 0x2UL, the same as   ASSOC_ARRAY_PTR_SUBTYPE_MASK.3. When 32 keys with the similar hashes are added to the tree, the ROOT   has keys with hashes that are not similar (e.g. slot 0) and it splits   NODE A without using a shortcut. When NODE A is filled with keys that   all hashes are xxe6, the keys are similar, NODE A will split with a   shortcut. Finally, it forms the tree as shown below, where slot 6 points   to a shortcut.                      NODE A              +------>+---+      ROOT    |       | 0 | xxe6      +---+   |       +---+ xxxx | 0 | shortcut  :   : xxe6      +---+   |       +---+ xxe6 :   :   |       |   | xxe6      +---+   |       +---+      | 6 |---+       :   : xxe6      +---+           +---+ xxe6 :   :           | f | xxe6      +---+           +---+ xxe6 | f |      +---+4. As mentioned above, If a slot(slot 6) of the root points to a shortcut,   it may be mistakenly transferred to a key*, leading to a read   out-of-bounds read.To fix this issue, one should jump to descend_to_node if the ptr is ashortcut, regardless of whether the node is root or not.[1] https://lore.kernel.org/linux-kernel/1cfa878e-8c7b-4570-8606-21daf5e13ce7@huaweicloud.com/[jarkko: tweaked the commit message a bit to have an appropriate closes tag.]
 漏洞公开时间：2024-11-19 10:16:32
 漏洞创建时间：2024-11-19 10:34:56
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-50301
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/199c20fb7499c79557a075dc24e9a7dae7d9f1ce |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/1e4332581cd4eed75aea77af6f66cdcdda8b49b9 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/3e79ad156bedf2da0ab909a118d2cec6c9c22b79 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/4a74da044ec9ec8679e6beccc4306b936b62873f |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/4efb69a0e294ef201bcdf7ce3d6202cd0a545a5d |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/bbad2d5b6c99db468d8f88b6ba6a56ed409b4881 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c3ce634ad953ce48c75c39bdfd8b711dd95f346f |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/e0a317ad68e4ea48a0158187238c5407e4fdec8b |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-50301 | https://bugzilla.suse.com/show_bug.cgi?id=1233490 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-50301.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1233490 |
| suse_bugzilla | https://git.kernel.org/stable/c/c3ce634ad953ce48c75c39bdfd8b711dd95f346f | https://bugzilla.suse.com/show_bug.cgi?id=1233490 |
| suse_bugzilla | https://git.kernel.org/stable/c/4efb69a0e294ef201bcdf7ce3d6202cd0a545a5d | https://bugzilla.suse.com/show_bug.cgi?id=1233490 |
| suse_bugzilla | https://git.kernel.org/stable/c/1e4332581cd4eed75aea77af6f66cdcdda8b49b9 | https://bugzilla.suse.com/show_bug.cgi?id=1233490 |
| suse_bugzilla | https://git.kernel.org/stable/c/199c20fb7499c79557a075dc24e9a7dae7d9f1ce | https://bugzilla.suse.com/show_bug.cgi?id=1233490 |
| suse_bugzilla | https://git.kernel.org/stable/c/bbad2d5b6c99db468d8f88b6ba6a56ed409b4881 | https://bugzilla.suse.com/show_bug.cgi?id=1233490 |
| suse_bugzilla | https://git.kernel.org/stable/c/3e79ad156bedf2da0ab909a118d2cec6c9c22b79 | https://bugzilla.suse.com/show_bug.cgi?id=1233490 |
| suse_bugzilla | https://git.kernel.org/stable/c/e0a317ad68e4ea48a0158187238c5407e4fdec8b | https://bugzilla.suse.com/show_bug.cgi?id=1233490 |
| suse_bugzilla | https://git.kernel.org/stable/c/4a74da044ec9ec8679e6beccc4306b936b62873f | https://bugzilla.suse.com/show_bug.cgi?id=1233490 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-50301 | https://bugzilla.suse.com/show_bug.cgi?id=1233490 |
| redhat_bugzilla | https://lore.kernel.org/linux-kernel/1cfa878e-8c7b-4570-8606-21daf5e13ce7@huaweicloud.com/ | https://bugzilla.redhat.com/show_bug.cgi?id=2327188 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024111907-CVE-2024-50301-ec76@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2327188 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-50301 |

</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:security/keys: fix slab-out-of-bounds in key_task_permissionKASAN reports an out of bounds read:BUG: KASAN: slab-out-of-bounds in __kuid_val include/linux/uidgid.h:36BUG: KASAN: slab-out-of-bounds in uid_eq include/linux/uidgid.h:63 [inline]BUG: KASAN: slab-out-of-bounds in key_task_permission+0x394/0x410security/keys/permission.c:54Read of size 4 at addr ffff88813c3ab618 by task stress-ng/4362CPU: 2 PID: 4362 Comm: stress-ng Not tainted 5.10.0-14930-gafbffd6c3ede #15Call Trace: __dump_stack lib/dump_stack.c:82 [inline] dump_stack+0x107/0x167 lib/dump_stack.c:123 print_address_description.constprop.0+0x19/0x170 mm/kasan/report.c:400 __kasan_report.cold+0x6c/0x84 mm/kasan/report.c:560 kasan_report+0x3a/0x50 mm/kasan/report.c:585 __kuid_val include/linux/uidgid.h:36 [inline] uid_eq include/linux/uidgid.h:63 [inline] key_task_permission+0x394/0x410 security/keys/permission.c:54 search_nested_keyrings+0x90e/0xe90 security/keys/keyring.c:793This issue was also reported by syzbot.It can be reproduced by following these steps(more details [1]):1. Obtain more than 32 inputs that have similar hashes, which ends with the   pattern  0xxxxxxxe6 .2. Reboot and add the keys obtained in step 1.The reproducer demonstrates how this issue happened:1. In the search_nested_keyrings function, when it iterates through the   slots in a node(below tag ascend_to_node), if the slot pointer is meta   and node->back_pointer != NULL(it means a root), it will proceed to   descend_to_node. However, there is an exception. If node is the root,   and one of the slots points to a shortcut, it will be treated as a   keyring.2. Whether the ptr is keyring decided by keyring_ptr_is_keyring function.   However, KEYRING_PTR_SUBTYPE is 0x2UL, the same as   ASSOC_ARRAY_PTR_SUBTYPE_MASK.3. When 32 keys with the similar hashes are added to the tree, the ROOT   has keys with hashes that are not similar (e.g. slot 0) and it splits   NODE A without using a shortcut. When NODE A is filled with keys that   all hashes are xxe6, the keys are similar, NODE A will split with a   shortcut. Finally, it forms the tree as shown below, where slot 6 points   to a shortcut.                      NODE A              +------>+---+      ROOT    |       | 0 | xxe6      +---+   |       +---+ xxxx | 0 | shortcut  :   : xxe6      +---+   |       +---+ xxe6 :   :   |       |   | xxe6      +---+   |       +---+      | 6 |---+       :   : xxe6      +---+           +---+ xxe6 :   :           | f | xxe6      +---+           +---+ xxe6 | f |      +---+4. As mentioned above, If a slot(slot 6) of the root points to a shortcut,   it may be mistakenly transferred to a key*, leading to a read   out-of-bounds read.To fix this issue, one should jump to descend_to_node if the ptr is ashortcut, regardless of whether the node is root or not.[1] https://lore.kernel.org/linux-kernel/1cfa878e-8c7b-4570-8606-21daf5e13ce7@huaweicloud.com/[jarkko: tweaked the commit message a bit to have an appropriate closes tag.]
 openEuler评分：
  7.1
 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
 受影响版本排查(受影响/不受影响)：
  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.openEuler-24.03-LTS(6.6.0):受影响
6.master(6.6.0):不受影响
7.openEuler-24.03-LTS-Next(6.6.0):不受影响
8.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-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.openEuler-24.03-LTS(6.6.0):正常修复
6.master(6.6.0):不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不存在
8.openEuler-24.03-LTS-SP1(6.6.0):不受影响-漏洞代码不存在

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

src-openEuler/kernel
Closed

Content Risk Flag

Comments (17)

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

Content Risk Flag

CVE-2024-50301

Comments (17)

Search

src-openEuler/kernel
Closed