CVE-2024-43900

一、漏洞信息
 漏洞编号：[CVE-2024-43900](https://nvd.nist.gov/vuln/detail/CVE-2024-43900)
 漏洞归属组件：[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.8 High
  Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:media: xc2028: avoid use-after-free in load_firmware_cb()syzkaller reported use-after-free in load_firmware_cb() [1].The reason is because the module allocated a struct tuner in tuner_probe(),and then the module initialization failed, the struct tuner was released.A worker which created during module initialization accesses this structtuner later, it caused use-after-free.The process is as follows:task-6504           worker_threadtuner_probe                             <= alloc dvb_frontend [2]...request_firmware_nowait                 <= create a worker...tuner_remove                            <= free dvb_frontend...                    request_firmware_work_func  <= the firmware is ready                    load_firmware_cb    <= but now the dvb_frontend has been freedTo fix the issue, check the dvd_frontend in load_firmware_cb(), if it isnull, report a warning and just return.[1]:    ==================================================================     BUG: KASAN: use-after-free in load_firmware_cb+0x1310/0x17a0     Read of size 8 at addr ffff8000d7ca2308 by task kworker/2:3/6504     Call trace:      load_firmware_cb+0x1310/0x17a0      request_firmware_work_func+0x128/0x220      process_one_work+0x770/0x1824      worker_thread+0x488/0xea0      kthread+0x300/0x430      ret_from_fork+0x10/0x20     Allocated by task 6504:      kzalloc      tuner_probe+0xb0/0x1430      i2c_device_probe+0x92c/0xaf0      really_probe+0x678/0xcd0      driver_probe_device+0x280/0x370      __device_attach_driver+0x220/0x330      bus_for_each_drv+0x134/0x1c0      __device_attach+0x1f4/0x410      device_initial_probe+0x20/0x30      bus_probe_device+0x184/0x200      device_add+0x924/0x12c0      device_register+0x24/0x30      i2c_new_device+0x4e0/0xc44      v4l2_i2c_new_subdev_board+0xbc/0x290      v4l2_i2c_new_subdev+0xc8/0x104      em28xx_v4l2_init+0x1dd0/0x3770     Freed by task 6504:      kfree+0x238/0x4e4      tuner_remove+0x144/0x1c0      i2c_device_remove+0xc8/0x290      __device_release_driver+0x314/0x5fc      device_release_driver+0x30/0x44      bus_remove_device+0x244/0x490      device_del+0x350/0x900      device_unregister+0x28/0xd0      i2c_unregister_device+0x174/0x1d0      v4l2_device_unregister+0x224/0x380      em28xx_v4l2_init+0x1d90/0x3770     The buggy address belongs to the object at ffff8000d7ca2000      which belongs to the cache kmalloc-2k of size 2048     The buggy address is located 776 bytes inside of      2048-byte region [ffff8000d7ca2000, ffff8000d7ca2800)     The buggy address belongs to the page:     page:ffff7fe00035f280 count:1 mapcount:0 mapping:ffff8000c001f000 index:0x0     flags: 0x7ff800000000100(slab)     raw: 07ff800000000100 ffff7fe00049d880 0000000300000003 ffff8000c001f000     raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000     page dumped because: kasan: bad access detected     Memory state around the buggy address:      ffff8000d7ca2200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb      ffff8000d7ca2280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb     >ffff8000d7ca2300: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb                           ^      ffff8000d7ca2380: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb      ffff8000d7ca2400: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb     ==================================================================[2]    Actually, it is allocated for struct tuner, and dvb_frontend is inside.
 漏洞公开时间：2024-08-26 19:15:04
 漏洞创建时间：2024-08-27 05:21:14
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-43900
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/208deb6d8c3cb8c3acb1f41eb31cf68ea08726d5 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/68594cec291ff9523b9feb3f43fd853dcddd1f60 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/850304152d367f104d21c77cfbcc05806504218b |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ef517bdfc01818419f7bd426969a0c86b14f3e0e |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-43900 | https://bugzilla.suse.com/show_bug.cgi?id=1229756 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-43900 | https://bugzilla.suse.com/show_bug.cgi?id=1229756 |
| suse_bugzilla | https://git.kernel.org/stable/c/208deb6d8c3cb8c3acb1f41eb31cf68ea08726d5 | https://bugzilla.suse.com/show_bug.cgi?id=1229756 |
| suse_bugzilla | https://git.kernel.org/stable/c/68594cec291ff9523b9feb3f43fd853dcddd1f60 | https://bugzilla.suse.com/show_bug.cgi?id=1229756 |
| suse_bugzilla | https://git.kernel.org/stable/c/850304152d367f104d21c77cfbcc05806504218b | https://bugzilla.suse.com/show_bug.cgi?id=1229756 |
| suse_bugzilla | https://git.kernel.org/stable/c/ef517bdfc01818419f7bd426969a0c86b14f3e0e | https://bugzilla.suse.com/show_bug.cgi?id=1229756 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024082616-CVE-2024-43900-029c@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2307873 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-43900 | https://ubuntu.com/security/CVE-2024-43900 |
| ubuntu | https://git.kernel.org/linus/68594cec291ff9523b9feb3f43fd853dcddd1f60 (6.11-rc1) | https://ubuntu.com/security/CVE-2024-43900 |
| ubuntu | https://git.kernel.org/stable/c/ef517bdfc01818419f7bd426969a0c86b14f3e0e | https://ubuntu.com/security/CVE-2024-43900 |
| ubuntu | https://git.kernel.org/stable/c/850304152d367f104d21c77cfbcc05806504218b | https://ubuntu.com/security/CVE-2024-43900 |
| ubuntu | https://git.kernel.org/stable/c/208deb6d8c3cb8c3acb1f41eb31cf68ea08726d5 | https://ubuntu.com/security/CVE-2024-43900 |
| ubuntu | https://git.kernel.org/stable/c/68594cec291ff9523b9feb3f43fd853dcddd1f60 | https://ubuntu.com/security/CVE-2024-43900 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-43900 | https://ubuntu.com/security/CVE-2024-43900 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2024-43900 | https://ubuntu.com/security/CVE-2024-43900 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-43900 | https://ubuntu.com/security/CVE-2024-43900 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-43900 |
| mageia |  | http://advisories.mageia.org/MGASA-2024-0309.html |

</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/208deb6d8c3cb8c3acb1f41eb31cf68ea08726d5 |  | nvd |
|  |  | https://git.kernel.org/stable/c/68594cec291ff9523b9feb3f43fd853dcddd1f60 |  | nvd |
|  |  | https://git.kernel.org/stable/c/850304152d367f104d21c77cfbcc05806504218b |  | nvd |
|  |  | https://git.kernel.org/stable/c/ef517bdfc01818419f7bd426969a0c86b14f3e0e |  | nvd |
| linux |  | https://git.kernel.org/linus/68594cec291ff9523b9feb3f43fd853dcddd1f60 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
      In the Linux kernel, the following vulnerability has been resolved:media: xc2028: avoid use-after-free in load_firmware_cb()syzkaller reported use-after-free in load_firmware_cb() [1].The reason is because the module allocated a struct tuner in tuner_probe(),and then the module initialization failed, the struct tuner was released.A worker which created during module initialization accesses this structtuner later, it caused use-after-free.The process is as follows:task-6504           worker_threadtuner_probe                             &lt;= alloc dvb_frontend [2]...request_firmware_nowait                 &lt;= create a worker...tuner_remove                            &lt;= free dvb_frontend...                    request_firmware_work_func  &lt;= the firmware is ready                    load_firmware_cb    &lt;= but now the dvb_frontend has been freedTo fix the issue, check the dvd_frontend in load_firmware_cb(), if it isnull, report a warning and just return.[1]:    ==================================================================     BUG: KASAN: use-after-free in load_firmware_cb+0x1310/0x17a0     Read of size 8 at addr ffff8000d7ca2308 by task kworker/2:3/6504     Call trace:      load_firmware_cb+0x1310/0x17a0      request_firmware_work_func+0x128/0x220      process_one_work+0x770/0x1824      worker_thread+0x488/0xea0      kthread+0x300/0x430      ret_from_fork+0x10/0x20     Allocated by task 6504:      kzalloc      tuner_probe+0xb0/0x1430      i2c_device_probe+0x92c/0xaf0      really_probe+0x678/0xcd0      driver_probe_device+0x280/0x370      __device_attach_driver+0x220/0x330      bus_for_each_drv+0x134/0x1c0      __device_attach+0x1f4/0x410      device_initial_probe+0x20/0x30      bus_probe_device+0x184/0x200      device_add+0x924/0x12c0      device_register+0x24/0x30      i2c_new_device+0x4e0/0xc44      v4l2_i2c_new_subdev_board+0xbc/0x290      v4l2_i2c_new_subdev+0xc8/0x104      em28xx_v4l2_init+0x1dd0/0x3770     Freed by task 6504:      kfree+0x238/0x4e4      tuner_remove+0x144/0x1c0      i2c_device_remove+0xc8/0x290      __device_release_driver+0x314/0x5fc      device_release_driver+0x30/0x44      bus_remove_device+0x244/0x490      device_del+0x350/0x900      device_unregister+0x28/0xd0      i2c_unregister_device+0x174/0x1d0      v4l2_device_unregister+0x224/0x380      em28xx_v4l2_init+0x1d90/0x3770     The buggy address belongs to the object at ffff8000d7ca2000      which belongs to the cache kmalloc-2k of size 2048     The buggy address is located 776 bytes inside of      2048-byte region [ffff8000d7ca2000, ffff8000d7ca2800)     The buggy address belongs to the page:     page:ffff7fe00035f280 count:1 mapcount:0 mapping:ffff8000c001f000 index:0x0     flags: 0x7ff800000000100(slab)     raw: 07ff800000000100 ffff7fe00049d880 0000000300000003 ffff8000c001f000     raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000     page dumped because: kasan: bad access detected     Memory state around the buggy address:      ffff8000d7ca2200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb      ffff8000d7ca2280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb     &gt;ffff8000d7ca2300: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb                           ^      ffff8000d7ca2380: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb      ffff8000d7ca2400: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb     ==================================================================[2]    Actually, it is allocated for struct tuner, and dvb_frontend is inside.The Linux kernel CVE team has assigned CVE-2024-43900 to this issue.  
 openEuler评分：
  7.8
 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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):不受影响

修复是否涉及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):否

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

src-openEuler/kernel
Closed

Content Risk Flag

Comments (50)

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

Content Risk Flag

CVE-2024-43900

Comments (50)

Search

src-openEuler/kernel
Closed