CVE-2022-49513

一、漏洞信息
 漏洞编号：[CVE-2022-49513](https://nvd.nist.gov/vuln/detail/CVE-2022-49513)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,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:cpufreq: governor: Use kobject release() method to free dbs_dataThe struct dbs_data embeds a struct gov_attr_set andthe struct gov_attr_set embeds a kobject. Since every kobject must havea release() method and we can t use kfree() to free it directly,so introduce cpufreq_dbs_data_release() to release the dbs_data viathe kobject::release() method. This fixes the calltrace like below:  ODEBUG: free active (active state 0) object type: timer_list hint: delayed_work_timer_fn+0x0/0x34  WARNING: CPU: 12 PID: 810 at lib/debugobjects.c:505 debug_print_object+0xb8/0x100  Modules linked in:  CPU: 12 PID: 810 Comm: sh Not tainted 5.16.0-next-20220120-yocto-standard+ #536  Hardware name: Marvell OcteonTX CN96XX board (DT)  pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)  pc : debug_print_object+0xb8/0x100  lr : debug_print_object+0xb8/0x100  sp : ffff80001dfcf9a0  x29: ffff80001dfcf9a0 x28: 0000000000000001 x27: ffff0001464f0000  x26: 0000000000000000 x25: ffff8000090e3f00 x24: ffff80000af60210  x23: ffff8000094dfb78 x22: ffff8000090e3f00 x21: ffff0001080b7118  x20: ffff80000aeb2430 x19: ffff800009e8f5e0 x18: 0000000000000000  x17: 0000000000000002 x16: 00004d62e58be040 x15: 013590470523aff8  x14: ffff8000090e1828 x13: 0000000001359047 x12: 00000000f5257d14  x11: 0000000000040591 x10: 0000000066c1ffea x9 : ffff8000080d15e0  x8 : ffff80000a1765a8 x7 : 0000000000000000 x6 : 0000000000000001  x5 : ffff800009e8c000 x4 : ffff800009e8c760 x3 : 0000000000000000  x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0001474ed040  Call trace:   debug_print_object+0xb8/0x100   __debug_check_no_obj_freed+0x1d0/0x25c   debug_check_no_obj_freed+0x24/0xa0   kfree+0x11c/0x440   cpufreq_dbs_governor_exit+0xa8/0xac   cpufreq_exit_governor+0x44/0x90   cpufreq_set_policy+0x29c/0x570   store_scaling_governor+0x110/0x154   store+0xb0/0xe0   sysfs_kf_write+0x58/0x84   kernfs_fop_write_iter+0x12c/0x1c0   new_sync_write+0xf0/0x18c   vfs_write+0x1cc/0x220   ksys_write+0x74/0x100   __arm64_sys_write+0x28/0x3c   invoke_syscall.constprop.0+0x58/0xf0   do_el0_svc+0x70/0x170   el0_svc+0x54/0x190   el0t_64_sync_handler+0xa4/0x130   el0t_64_sync+0x1a0/0x1a4  irq event stamp: 189006  hardirqs last  enabled at (189005): [<ffff8000080849d0>] finish_task_switch.isra.0+0xe0/0x2c0  hardirqs last disabled at (189006): [<ffff8000090667a4>] el1_dbg+0x24/0xa0  softirqs last  enabled at (188966): [<ffff8000080106d0>] __do_softirq+0x4b0/0x6a0  softirqs last disabled at (188957): [<ffff80000804a618>] __irq_exit_rcu+0x108/0x1a4[ rjw: Because can be freed by the gov_attr_set_put() in  cpufreq_dbs_governor_exit() now, it is also necessary to put the  invocation of the governor ->exit() callback into the new  cpufreq_dbs_data_release() function. ]
 漏洞公开时间：2025-02-26 15:01
 漏洞创建时间：2025-02-26 17:57:53
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2022-49513
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/1e32083f327184b6226ce320ef30085ce785ea4e |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/a1964688582d26af1328e19b658933659fb54337 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/a85ee6401a47ae3fc64ba506cacb3e7873823c65 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-49513 | https://bugzilla.suse.com/show_bug.cgi?id=1237800 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2022/CVE-2022-49513.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1237800 |
| suse_bugzilla | https://git.kernel.org/stable/c/a1964688582d26af1328e19b658933659fb54337 | https://bugzilla.suse.com/show_bug.cgi?id=1237800 |
| suse_bugzilla | https://git.kernel.org/stable/c/1e32083f327184b6226ce320ef30085ce785ea4e | https://bugzilla.suse.com/show_bug.cgi?id=1237800 |
| suse_bugzilla | https://git.kernel.org/stable/c/a85ee6401a47ae3fc64ba506cacb3e7873823c65 | https://bugzilla.suse.com/show_bug.cgi?id=1237800 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2025022609-CVE-2022-49513-f147@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2348128 |

</details>

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

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| linux_kernel | 5.15.91 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a1964688582d26af1328e19b658933659fb54337Issue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c4435630361d9bebf7154a0c842dc1fb7ae39c99 | linuxkernelcves |
| linux_kernel | 5.18.3 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1e32083f327184b6226ce320ef30085ce785ea4eIssue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c4435630361d9bebf7154a0c842dc1fb7ae39c99 | linuxkernelcves |
| linux_kernel | 5.19 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a85ee6401a47ae3fc64ba506cacb3e7873823c65Please | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c4435630361d9bebf7154a0c842dc1fb7ae39c99 | linuxkernelcves |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:cpufreq: governor: Use kobject release() method to free dbs_dataThe struct dbs_data embeds a struct gov_attr_set andthe struct gov_attr_set embeds a kobject. Since every kobject must havea release() method and we can t use kfree() to free it directly,so introduce cpufreq_dbs_data_release() to release the dbs_data viathe kobject::release() method. This fixes the calltrace like below:  ODEBUG: free active (active state 0) object type: timer_list hint: delayed_work_timer_fn+0x0/0x34  WARNING: CPU: 12 PID: 810 at lib/debugobjects.c:505 debug_print_object+0xb8/0x100  Modules linked in:  CPU: 12 PID: 810 Comm: sh Not tainted 5.16.0-next-20220120-yocto-standard+ #536  Hardware name: Marvell OcteonTX CN96XX board (DT)  pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)  pc : debug_print_object+0xb8/0x100  lr : debug_print_object+0xb8/0x100  sp : ffff80001dfcf9a0  x29: ffff80001dfcf9a0 x28: 0000000000000001 x27: ffff0001464f0000  x26: 0000000000000000 x25: ffff8000090e3f00 x24: ffff80000af60210  x23: ffff8000094dfb78 x22: ffff8000090e3f00 x21: ffff0001080b7118  x20: ffff80000aeb2430 x19: ffff800009e8f5e0 x18: 0000000000000000  x17: 0000000000000002 x16: 00004d62e58be040 x15: 013590470523aff8  x14: ffff8000090e1828 x13: 0000000001359047 x12: 00000000f5257d14  x11: 0000000000040591 x10: 0000000066c1ffea x9 : ffff8000080d15e0  x8 : ffff80000a1765a8 x7 : 0000000000000000 x6 : 0000000000000001  x5 : ffff800009e8c000 x4 : ffff800009e8c760 x3 : 0000000000000000  x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0001474ed040  Call trace:   debug_print_object+0xb8/0x100   __debug_check_no_obj_freed+0x1d0/0x25c   debug_check_no_obj_freed+0x24/0xa0   kfree+0x11c/0x440   cpufreq_dbs_governor_exit+0xa8/0xac   cpufreq_exit_governor+0x44/0x90   cpufreq_set_policy+0x29c/0x570   store_scaling_governor+0x110/0x154   store+0xb0/0xe0   sysfs_kf_write+0x58/0x84   kernfs_fop_write_iter+0x12c/0x1c0   new_sync_write+0xf0/0x18c   vfs_write+0x1cc/0x220   ksys_write+0x74/0x100   __arm64_sys_write+0x28/0x3c   invoke_syscall.constprop.0+0x58/0xf0   do_el0_svc+0x70/0x170   el0_svc+0x54/0x190   el0t_64_sync_handler+0xa4/0x130   el0t_64_sync+0x1a0/0x1a4  irq event stamp: 189006  hardirqs last  enabled at (189005): [<ffff8000080849d0>] finish_task_switch.isra.0+0xe0/0x2c0  hardirqs last disabled at (189006): [<ffff8000090667a4>] el1_dbg+0x24/0xa0  softirqs last  enabled at (188966): [<ffff8000080106d0>] __do_softirq+0x4b0/0x6a0  softirqs last disabled at (188957): [<ffff80000804a618>] __irq_exit_rcu+0x108/0x1a4[ rjw: Because can be freed by the gov_attr_set_put() in  cpufreq_dbs_governor_exit() now, it is also necessary to put the  invocation of the governor ->exit() callback into the new  cpufreq_dbs_data_release() function. ]
 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-20.03-LTS-SP4(4.19.90):受影响
2.openEuler-22.03-LTS-SP3:受影响
3.openEuler-22.03-LTS-SP4:受影响
4.master:不受影响
5.openEuler-24.03-LTS:不受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:不受影响

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

原因说明：
  1.openEuler-20.03-LTS-SP4(4.19.90):正常修复
2.openEuler-22.03-LTS-SP3:不修复-超出修复范围
3.openEuler-22.03-LTS-SP4:不修复-超出修复范围
4.master:不受影响-漏洞代码不能被攻击者触发
5.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
6.openEuler-24.03-LTS:不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-SP1:不受影响-漏洞代码不存在

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

src-openEuler/kernel

内容风险标识

评论 (10)

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

内容风险标识

CVE-2022-49513

评论 (10)

搜索帮助

src-openEuler/kernel