CVE-2024-41057

一、漏洞信息
 漏洞编号：[CVE-2024-41057](https://nvd.nist.gov/vuln/detail/CVE-2024-41057)
 漏洞归属组件：[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:cachefiles: fix slab-use-after-free in cachefiles_withdraw_cookie()We got the following issue in our fault injection stress test:==================================================================BUG: KASAN: slab-use-after-free in cachefiles_withdraw_cookie+0x4d9/0x600Read of size 8 at addr ffff888118efc000 by task kworker/u78:0/109CPU: 13 PID: 109 Comm: kworker/u78:0 Not tainted 6.8.0-dirty #566Call Trace: <TASK> kasan_report+0x93/0xc0 cachefiles_withdraw_cookie+0x4d9/0x600 fscache_cookie_state_machine+0x5c8/0x1230 fscache_cookie_worker+0x91/0x1c0 process_one_work+0x7fa/0x1800 [...]Allocated by task 117: kmalloc_trace+0x1b3/0x3c0 cachefiles_acquire_volume+0xf3/0x9c0 fscache_create_volume_work+0x97/0x150 process_one_work+0x7fa/0x1800 [...]Freed by task 120301: kfree+0xf1/0x2c0 cachefiles_withdraw_cache+0x3fa/0x920 cachefiles_put_unbind_pincount+0x1f6/0x250 cachefiles_daemon_release+0x13b/0x290 __fput+0x204/0xa00 task_work_run+0x139/0x230 do_exit+0x87a/0x29b0 [...]==================================================================Following is the process that triggers the issue:           p1                |             p2------------------------------------------------------------                              fscache_begin_lookup                               fscache_begin_volume_access                                fscache_cache_is_live(fscache_cache)cachefiles_daemon_release cachefiles_put_unbind_pincount  cachefiles_daemon_unbind   cachefiles_withdraw_cache    fscache_withdraw_cache     fscache_set_cache_state(cache, FSCACHE_CACHE_IS_WITHDRAWN);    cachefiles_withdraw_objects(cache)    fscache_wait_for_objects(fscache)      atomic_read(&fscache_cache->object_count) == 0                              fscache_perform_lookup                               cachefiles_lookup_cookie                                cachefiles_alloc_object                                 refcount_set(&object->ref, 1);                                 object->volume = volume                                 fscache_count_object(vcookie->cache);                                  atomic_inc(&fscache_cache->object_count)    cachefiles_withdraw_volumes     cachefiles_withdraw_volume      fscache_withdraw_volume      __cachefiles_free_volume       kfree(cachefiles_volume)                              fscache_cookie_state_machine                               cachefiles_withdraw_cookie                                cache = object->volume->cache;                                // cachefiles_volume UAF !!!After setting FSCACHE_CACHE_IS_WITHDRAWN, wait for all the cookie lookupsto complete first, and then wait for fscache_cache->object_count == 0 toavoid the cookie exiting after the volume has been freed and triggeringthe above issue. Therefore call fscache_withdraw_volume() before callingcachefiles_withdraw_objects().This way, after setting FSCACHE_CACHE_IS_WITHDRAWN, only the following twocases will occur:1) fscache_begin_lookup fails in fscache_begin_volume_access().2) fscache_withdraw_volume() will ensure that fscache_count_object() has   been executed before calling fscache_wait_for_objects().
 漏洞公开时间：2024-07-29 23:15:13
 漏洞创建时间：2024-08-01 10:09:31
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-41057
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/5d8f805789072ea7fd39504694b7bd17e5f751c4 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/8de253177112a47c9af157d23ae934779188b4e1 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/9e67589a4a7b7e5660b524d1d5fe61242bcbcc11 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ef81340401e8a371d6b17f69e76d861920972cfe |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-41057 | https://bugzilla.suse.com/show_bug.cgi?id=1228462 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-41057.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1228462 |
| suse_bugzilla | https://git.kernel.org/stable/c/8de253177112a47c9af157d23ae934779188b4e1 | https://bugzilla.suse.com/show_bug.cgi?id=1228462 |
| suse_bugzilla | https://git.kernel.org/stable/c/9e67589a4a7b7e5660b524d1d5fe61242bcbcc11 | https://bugzilla.suse.com/show_bug.cgi?id=1228462 |
| suse_bugzilla | https://git.kernel.org/stable/c/ef81340401e8a371d6b17f69e76d861920972cfe | https://bugzilla.suse.com/show_bug.cgi?id=1228462 |
| suse_bugzilla | https://git.kernel.org/stable/c/5d8f805789072ea7fd39504694b7bd17e5f751c4 | https://bugzilla.suse.com/show_bug.cgi?id=1228462 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-41057 | https://bugzilla.suse.com/show_bug.cgi?id=1228462 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024072902-CVE-2024-41057-1d06@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2300431 |
| redhat_bugzilla | https://access.redhat.com/errata/RHSA-2024:9315 | https://bugzilla.redhat.com/show_bug.cgi?id=2300431 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-41057 | https://ubuntu.com/security/CVE-2024-41057 |
| ubuntu | https://git.kernel.org/linus/5d8f805789072ea7fd39504694b7bd17e5f751c4 (6.10) | https://ubuntu.com/security/CVE-2024-41057 |
| ubuntu | https://git.kernel.org/stable/c/8de253177112a47c9af157d23ae934779188b4e1 | https://ubuntu.com/security/CVE-2024-41057 |
| ubuntu | https://git.kernel.org/stable/c/9e67589a4a7b7e5660b524d1d5fe61242bcbcc11 | https://ubuntu.com/security/CVE-2024-41057 |
| ubuntu | https://git.kernel.org/stable/c/ef81340401e8a371d6b17f69e76d861920972cfe | https://ubuntu.com/security/CVE-2024-41057 |
| ubuntu | https://git.kernel.org/stable/c/5d8f805789072ea7fd39504694b7bd17e5f751c4 | https://ubuntu.com/security/CVE-2024-41057 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-41057 | https://ubuntu.com/security/CVE-2024-41057 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2024-41057 | https://ubuntu.com/security/CVE-2024-41057 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-41057 | https://ubuntu.com/security/CVE-2024-41057 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-41057 |
| anolis |  | https://anas.openanolis.cn/cves/detail/CVE-2024-41057 |
| mageia |  | http://advisories.mageia.org/MGASA-2024-0278.html |

</details>

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

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
|  |  | https://git.kernel.org/stable/c/5d8f805789072ea7fd39504694b7bd17e5f751c4 |  | nvd |
|  |  | https://git.kernel.org/stable/c/8de253177112a47c9af157d23ae934779188b4e1 |  | nvd |
|  |  | https://git.kernel.org/stable/c/9e67589a4a7b7e5660b524d1d5fe61242bcbcc11 |  | nvd |
|  |  | https://git.kernel.org/stable/c/ef81340401e8a371d6b17f69e76d861920972cfe |  | nvd |
| linux |  | https://git.kernel.org/linus/5d8f805789072ea7fd39504694b7bd17e5f751c4 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:cachefiles: fix slab-use-after-free in cachefiles_withdraw_cookie()We got the following issue in our fault injection stress test:==================================================================BUG: KASAN: slab-use-after-free in cachefiles_withdraw_cookie+0x4d9/0x600Read of size 8 at addr ffff888118efc000 by task kworker/u78:0/109CPU: 13 PID: 109 Comm: kworker/u78:0 Not tainted 6.8.0-dirty #566Call Trace: <TASK> kasan_report+0x93/0xc0 cachefiles_withdraw_cookie+0x4d9/0x600 fscache_cookie_state_machine+0x5c8/0x1230 fscache_cookie_worker+0x91/0x1c0 process_one_work+0x7fa/0x1800 [...]Allocated by task 117: kmalloc_trace+0x1b3/0x3c0 cachefiles_acquire_volume+0xf3/0x9c0 fscache_create_volume_work+0x97/0x150 process_one_work+0x7fa/0x1800 [...]Freed by task 120301: kfree+0xf1/0x2c0 cachefiles_withdraw_cache+0x3fa/0x920 cachefiles_put_unbind_pincount+0x1f6/0x250 cachefiles_daemon_release+0x13b/0x290 __fput+0x204/0xa00 task_work_run+0x139/0x230 do_exit+0x87a/0x29b0 [...]==================================================================Following is the process that triggers the issue:           p1                |             p2------------------------------------------------------------                              fscache_begin_lookup                               fscache_begin_volume_access                                fscache_cache_is_live(fscache_cache)cachefiles_daemon_release cachefiles_put_unbind_pincount  cachefiles_daemon_unbind   cachefiles_withdraw_cache    fscache_withdraw_cache     fscache_set_cache_state(cache, FSCACHE_CACHE_IS_WITHDRAWN);    cachefiles_withdraw_objects(cache)    fscache_wait_for_objects(fscache)      atomic_read(&fscache_cache->object_count) == 0                              fscache_perform_lookup                               cachefiles_lookup_cookie                                cachefiles_alloc_object                                 refcount_set(&object->ref, 1);                                 object->volume = volume                                 fscache_count_object(vcookie->cache);                                  atomic_inc(&fscache_cache->object_count)    cachefiles_withdraw_volumes     cachefiles_withdraw_volume      fscache_withdraw_volume      __cachefiles_free_volume       kfree(cachefiles_volume)                              fscache_cookie_state_machine                               cachefiles_withdraw_cookie                                cache = object->volume->cache;                                // cachefiles_volume UAF !!!After setting FSCACHE_CACHE_IS_WITHDRAWN, wait for all the cookie lookupsto complete first, and then wait for fscache_cache->object_count == 0 toavoid the cookie exiting after the volume has been freed and triggeringthe above issue. Therefore call fscache_withdraw_volume() before callingcachefiles_withdraw_objects().This way, after setting FSCACHE_CACHE_IS_WITHDRAWN, only the following twocases will occur:1) fscache_begin_lookup fails in fscache_begin_volume_access().2) fscache_withdraw_volume() will ensure that fscache_count_object() has   been executed before calling fscache_wait_for_objects().
 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-24.03-LTS(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.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-24.03-LTS(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.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-2590

src-openEuler/kernel

Content Risk Flag

Comments (27)

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

Content Risk Flag

CVE-2024-41057

Comments (27)

Search

src-openEuler/kernel