CVE-2022-48921

一、漏洞信息
 漏洞编号：[CVE-2022-48921](https://nvd.nist.gov/vuln/detail/CVE-2022-48921)
 漏洞归属组件：[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：4.7 Medium
  Vector：CVSS：3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:sched/fair: Fix fault in reweight_entitySyzbot found a GPF in reweight_entity. This has been bisected tocommit 4ef0c5c6b5ba ( kernel/sched: Fix sched_fork() access an invalidsched_task_group )There is a race between sched_post_fork() and setpriority(PRIO_PGRP)within a thread group that causes a null-ptr-deref inreweight_entity() in CFS. The scenario is that the main process spawnsnumber of new threads, which then call setpriority(PRIO_PGRP, 0, -20),wait, and exit.  For each of the new threads the copy_process() getsinvoked, which adds the new task_struct and calls sched_post_fork()for it.In the above scenario there is a possibility thatsetpriority(PRIO_PGRP) and set_one_prio() will be called for a threadin the group that is just being created by copy_process(), and forwhich the sched_post_fork() has not been executed yet. This willtrigger a null pointer dereference in reweight_entity(), as it willtry to access the run queue pointer, which hasn t been set.Before the mentioned change the cfs_rq pointer for the task  has beenset in sched_fork(), which is called much earlier in copy_process(),before the new task is added to the thread_group.  Now it is done inthe sched_post_fork(), which is called after that.  To fix the issuethe remove the update_load param from the update_load param() functionand call reweight_task() only if the task flag doesn t have theTASK_NEW flag set.
 漏洞公开时间：2024-08-22 10:15:08
 漏洞创建时间：2024-08-22 12:28:07
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2022-48921
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/13765de8148f71fa795e0a6607de37c49ea5915a |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/589a954daab5e18399860b6c8ffaeaf79844eb20 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/8f317cd888059c59e2fa924bf4b0957cfa53f78e |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/e0bcd6b5779352aed88f2e538a82a39f1a7715bb |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48921 | https://bugzilla.suse.com/show_bug.cgi?id=1229635 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2022-48921 | https://bugzilla.suse.com/show_bug.cgi?id=1229635 |
| suse_bugzilla | https://git.kernel.org/stable/c/13765de8148f71fa795e0a6607de37c49ea5915a | https://bugzilla.suse.com/show_bug.cgi?id=1229635 |
| suse_bugzilla | https://git.kernel.org/stable/c/589a954daab5e18399860b6c8ffaeaf79844eb20 | https://bugzilla.suse.com/show_bug.cgi?id=1229635 |
| suse_bugzilla | https://git.kernel.org/stable/c/8f317cd888059c59e2fa924bf4b0957cfa53f78e | https://bugzilla.suse.com/show_bug.cgi?id=1229635 |
| suse_bugzilla | https://git.kernel.org/stable/c/e0bcd6b5779352aed88f2e538a82a39f1a7715bb | https://bugzilla.suse.com/show_bug.cgi?id=1229635 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2022/CVE-2022-48921.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1229635 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2022-48921 | https://ubuntu.com/security/CVE-2022-48921 |
| ubuntu | https://git.kernel.org/linus/13765de8148f71fa795e0a6607de37c49ea5915a (5.17-rc4) | https://ubuntu.com/security/CVE-2022-48921 |
| ubuntu | https://git.kernel.org/stable/c/8f317cd888059c59e2fa924bf4b0957cfa53f78e | https://ubuntu.com/security/CVE-2022-48921 |
| ubuntu | https://git.kernel.org/stable/c/e0bcd6b5779352aed88f2e538a82a39f1a7715bb | https://ubuntu.com/security/CVE-2022-48921 |
| ubuntu | https://git.kernel.org/stable/c/589a954daab5e18399860b6c8ffaeaf79844eb20 | https://ubuntu.com/security/CVE-2022-48921 |
| ubuntu | https://git.kernel.org/stable/c/13765de8148f71fa795e0a6607de37c49ea5915a | https://ubuntu.com/security/CVE-2022-48921 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2022-48921 | https://ubuntu.com/security/CVE-2022-48921 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2022-48921 | https://ubuntu.com/security/CVE-2022-48921 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2022-48921 | https://ubuntu.com/security/CVE-2022-48921 |

</details>

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

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
|  |  | https://git.kernel.org/stable/c/13765de8148f71fa795e0a6607de37c49ea5915a |  | nvd |
|  |  | https://git.kernel.org/stable/c/589a954daab5e18399860b6c8ffaeaf79844eb20 |  | nvd |
|  |  | https://git.kernel.org/stable/c/8f317cd888059c59e2fa924bf4b0957cfa53f78e |  | nvd |
|  |  | https://git.kernel.org/stable/c/e0bcd6b5779352aed88f2e538a82a39f1a7715bb |  | nvd |
| linux_kernel | 5.10.137 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8f317cd88805Issue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c85c6fadbef0 | linuxkernelcves |
| linux_kernel | 5.15.27 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e0bcd6b57793Issue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c85c6fadbef0 | linuxkernelcves |
| linux_kernel | 5.16.13 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=589a954daab5Issue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c85c6fadbef0 | linuxkernelcves |
| linux_kernel | 5.17 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=13765de8148fIssue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c85c6fadbef0 | linuxkernelcves |
| linux |  | https://git.kernel.org/linus/13765de8148f71fa795e0a6607de37c49ea5915a | https://git.kernel.org/linus/4ef0c5c6b5ba1f38f0ea1cedad0cad722f00c14a | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:sched/fair: Fix fault in reweight_entitySyzbot found a GPF in reweight_entity. This has been bisected tocommit 4ef0c5c6b5ba ( kernel/sched: Fix sched_fork() access an invalidsched_task_group )There is a race between sched_post_fork() and setpriority(PRIO_PGRP)within a thread group that causes a null-ptr-deref inreweight_entity() in CFS. The scenario is that the main process spawnsnumber of new threads, which then call setpriority(PRIO_PGRP, 0, -20),wait, and exit.  For each of the new threads the copy_process() getsinvoked, which adds the new task_struct and calls sched_post_fork()for it.In the above scenario there is a possibility thatsetpriority(PRIO_PGRP) and set_one_prio() will be called for a threadin the group that is just being created by copy_process(), and forwhich the sched_post_fork() has not been executed yet. This willtrigger a null pointer dereference in reweight_entity(), as it willtry to access the run queue pointer, which hasn t been set.Before the mentioned change the cfs_rq pointer for the task  has beenset in sched_fork(), which is called much earlier in copy_process(),before the new task is added to the thread_group.  Now it is done inthe sched_post_fork(), which is called after that.  To fix the issuethe remove the update_load param from the update_load param() functionand call reweight_task() only if the task flag doesn t have theTASK_NEW flag set.
 openEuler评分：
  4.7
 Vector：CVSS：3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/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.master(6.6.0):不受影响
6.openEuler-24.03-LTS(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.master(6.6.0):不受影响-漏洞代码不存在
6.openEuler-24.03-LTS(6.6.0):不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不存在
8.openEuler-24.03-LTS-SP1(6.6.0):不受影响-漏洞代码不存在

src-openEuler / kernel
Closed

Content Risk Flag

Comments (28)

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

Content Risk Flag

CVE-2022-48921

Comments (28)

Search

src-openEuler / kernel
Closed