Sign in
Sign up
Explore
Enterprise
Education
Search
Help
Terms of use
About Us
Explore
Enterprise
Education
Gitee Premium
Gitee AI
AI teammates
Sign in
Sign up
Fetch the repository succeeded.
description of repo status
Open Source
>
Other
>
Operation System
&&
Watch
Unwatch
Watching
Releases Only
Ignoring
128
Star
73
Fork
331
src-openEuler
/
kernel
Closed
Code
Issues
1197
Pull Requests
35
Wiki
Insights
Pipelines
Service
JavaDoc
PHPDoc
Quality Analysis
Jenkins for Gitee
Tencent CloudBase
Tencent Cloud Serverless
悬镜安全
Aliyun SAE
Codeblitz
SBOM
DevLens
Don’t show this again
Update failed. Please try again later!
Remove this flag
Content Risk Flag
This task is identified by
as the content contains sensitive information such as code security bugs, privacy leaks, etc., so it is only accessible to contributors of this repository.
CVE-2024-56653
Done
#IBEAOV
CVE和安全问题
openeuler-ci-bot
owner
Opened this issue
2024-12-28 00:02
一、漏洞信息 漏洞编号:[CVE-2024-56653](https://nvd.nist.gov/vuln/detail/CVE-2024-56653) 漏洞归属组件:[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: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:Bluetooth: btmtk: avoid UAF in btmtk_process_coredumphci_devcd_append may lead to the release of the skb, so it cannot beaccessed once it is called.==================================================================BUG: KASAN: slab-use-after-free in btmtk_process_coredump+0x2a7/0x2d0 [btmtk]Read of size 4 at addr ffff888033cfabb0 by task kworker/0:3/82CPU: 0 PID: 82 Comm: kworker/0:3 Tainted: G U 6.6.40-lockdep-03464-g1d8b4eb3060e #1 b0b3c1cc0c842735643fb411799d97921d1f688cHardware name: Google Yaviks_Ufs/Yaviks_Ufs, BIOS Google_Yaviks_Ufs.15217.552.0 05/07/2024Workqueue: events btusb_rx_work [btusb]Call Trace: <TASK> dump_stack_lvl+0xfd/0x150 print_report+0x131/0x780 kasan_report+0x177/0x1c0 btmtk_process_coredump+0x2a7/0x2d0 [btmtk 03edd567dd71a65958807c95a65db31d433e1d01] btusb_recv_acl_mtk+0x11c/0x1a0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec] btusb_rx_work+0x9e/0xe0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30 </TASK>Allocated by task 82: stack_trace_save+0xdc/0x190 kasan_set_track+0x4e/0x80 __kasan_slab_alloc+0x4e/0x60 kmem_cache_alloc+0x19f/0x360 skb_clone+0x132/0xf70 btusb_recv_acl_mtk+0x104/0x1a0 [btusb] btusb_rx_work+0x9e/0xe0 [btusb] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30Freed by task 1733: stack_trace_save+0xdc/0x190 kasan_set_track+0x4e/0x80 kasan_save_free_info+0x28/0xb0 ____kasan_slab_free+0xfd/0x170 kmem_cache_free+0x183/0x3f0 hci_devcd_rx+0x91a/0x2060 [bluetooth] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30The buggy address belongs to the object at ffff888033cfab40 which belongs to the cache skbuff_head_cache of size 232The buggy address is located 112 bytes inside of freed 232-byte region [ffff888033cfab40, ffff888033cfac28)The buggy address belongs to the physical page:page:00000000a174ba93 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x33cfahead:00000000a174ba93 order:1 entire_mapcount:0 nr_pages_mapped:0 pincount:0anon flags: 0x4000000000000840(slab|head|zone=1)page_type: 0xffffffff()raw: 4000000000000840 ffff888100848a00 0000000000000000 0000000000000001raw: 0000000000000000 0000000080190019 00000001ffffffff 0000000000000000page dumped because: kasan: bad access detectedMemory state around the buggy address: ffff888033cfaa80: fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc ffff888033cfab00: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb>ffff888033cfab80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff888033cfac00: fb fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc ffff888033cfac80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb==================================================================Check if we need to call hci_devcd_complete before callinghci_devcd_append. That requires that we check data->cd_info.cnt >=MTK_COREDUMP_NUM instead of data->cd_info.cnt > MTK_COREDUMP_NUM, as weincrement data->cd_info.cnt only once the call to hci_devcd_appendsucceeds. 漏洞公开时间:2024-12-27 23:15:25 漏洞创建时间:2025-02-05 10:34:33 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2024-56653 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/b548f5e9456c568155499d9ebac675c0d7a296e8 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/d20ff1d3cb40479789368f502eedb0a00e4161fc | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ecdcaea0e4057171ea4c3783e1cc1c900ad99125 | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-56653 | https://bugzilla.suse.com/show_bug.cgi?id=1235531 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-56653 | https://bugzilla.suse.com/show_bug.cgi?id=1235531 | | suse_bugzilla | https://git.kernel.org/stable/c/b548f5e9456c568155499d9ebac675c0d7a296e8 | https://bugzilla.suse.com/show_bug.cgi?id=1235531 | | suse_bugzilla | https://git.kernel.org/stable/c/d20ff1d3cb40479789368f502eedb0a00e4161fc | https://bugzilla.suse.com/show_bug.cgi?id=1235531 | | suse_bugzilla | https://git.kernel.org/stable/c/ecdcaea0e4057171ea4c3783e1cc1c900ad99125 | https://bugzilla.suse.com/show_bug.cgi?id=1235531 | | suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-56653.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1235531 | | suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2334538 | https://bugzilla.suse.com/show_bug.cgi?id=1235531 | | redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024122749-CVE-2024-56653-bb35@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2334538 | | debian | | https://security-tracker.debian.org/tracker/CVE-2024-56653 | </details> 漏洞分析指导链接: https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: openBrain开源漏洞感知系统 漏洞补丁信息: <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | linux_kernel | 6.6.67 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ecdcaea0e4057171ea4c3783e1cc1c900ad99125Issue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0b70151328781a89c89e4cf3fae21fc0e98d869e | linuxkernelcves | | linux_kernel | 6.12.6 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d20ff1d3cb40479789368f502eedb0a00e4161fcIssue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0b70151328781a89c89e4cf3fae21fc0e98d869e | linuxkernelcves | | linux_kernel | 6.13-rc3 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b548f5e9456c568155499d9ebac675c0d7a296e8Please | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0b70151328781a89c89e4cf3fae21fc0e98d869e | linuxkernelcves | </details> 二、漏洞分析结构反馈 影响性分析说明: In the Linux kernel, the following vulnerability has been resolved:Bluetooth: btmtk: avoid UAF in btmtk_process_coredumphci_devcd_append may lead to the release of the skb, so it cannot beaccessed once it is called.==================================================================BUG: KASAN: slab-use-after-free in btmtk_process_coredump+0x2a7/0x2d0 [btmtk]Read of size 4 at addr ffff888033cfabb0 by task kworker/0:3/82CPU: 0 PID: 82 Comm: kworker/0:3 Tainted: G U 6.6.40-lockdep-03464-g1d8b4eb3060e #1 b0b3c1cc0c842735643fb411799d97921d1f688cHardware name: Google Yaviks_Ufs/Yaviks_Ufs, BIOS Google_Yaviks_Ufs.15217.552.0 05/07/2024Workqueue: events btusb_rx_work [btusb]Call Trace: <TASK> dump_stack_lvl+0xfd/0x150 print_report+0x131/0x780 kasan_report+0x177/0x1c0 btmtk_process_coredump+0x2a7/0x2d0 [btmtk 03edd567dd71a65958807c95a65db31d433e1d01] btusb_recv_acl_mtk+0x11c/0x1a0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec] btusb_rx_work+0x9e/0xe0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30 </TASK>Allocated by task 82: stack_trace_save+0xdc/0x190 kasan_set_track+0x4e/0x80 __kasan_slab_alloc+0x4e/0x60 kmem_cache_alloc+0x19f/0x360 skb_clone+0x132/0xf70 btusb_recv_acl_mtk+0x104/0x1a0 [btusb] btusb_rx_work+0x9e/0xe0 [btusb] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30Freed by task 1733: stack_trace_save+0xdc/0x190 kasan_set_track+0x4e/0x80 kasan_save_free_info+0x28/0xb0 ____kasan_slab_free+0xfd/0x170 kmem_cache_free+0x183/0x3f0 hci_devcd_rx+0x91a/0x2060 [bluetooth] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30The buggy address belongs to the object at ffff888033cfab40 which belongs to the cache skbuff_head_cache of size 232The buggy address is located 112 bytes inside of freed 232-byte region [ffff888033cfab40, ffff888033cfac28)The buggy address belongs to the physical page:page:00000000a174ba93 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x33cfahead:00000000a174ba93 order:1 entire_mapcount:0 nr_pages_mapped:0 pincount:0anon flags: 0x4000000000000840(slab|head|zone=1)page_type: 0xffffffff()raw: 4000000000000840 ffff888100848a00 0000000000000000 0000000000000001raw: 0000000000000000 0000000080190019 00000001ffffffff 0000000000000000page dumped because: kasan: bad access detectedMemory state around the buggy address: ffff888033cfaa80: fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc ffff888033cfab00: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb>ffff888033cfab80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff888033cfac00: fb fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc ffff888033cfac80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb==================================================================Check if we need to call hci_devcd_complete before callinghci_devcd_append. That requires that we check data->cd_info.cnt >=MTK_COREDUMP_NUM instead of data->cd_info.cnt > MTK_COREDUMP_NUM, as weincrement data->cd_info.cnt only once the call to hci_devcd_appendsucceeds. 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-24.03-LTS-SP1(6.6.0):受影响 3.openEuler-20.03-LTS-SP4(4.19.90):不受影响 4.openEuler-22.03-LTS-SP3(5.10.0):不受影响 5.openEuler-22.03-LTS-SP4:不受影响 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-SP3(5.10.0):否 3.master(6.6.0):否 4.openEuler-24.03-LTS(6.6.0):否 5.openEuler-24.03-LTS-Next(6.6.0):否 6.openEuler-22.03-LTS-SP4:否 7.openEuler-24.03-LTS-SP1(6.6.0):否 原因说明: 1.openEuler-24.03-LTS(6.6.0):正常修复 2.openEuler-24.03-LTS-SP1(6.6.0):正常修复 3.master(6.6.0):不受影响-漏洞代码不能被攻击者触发 4.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发 5.openEuler-20.03-LTS-SP4(4.19.90):不受影响-漏洞代码不存在 6.openEuler-22.03-LTS-SP3(5.10.0):不受影响-漏洞代码不存在 7.openEuler-22.03-LTS-SP4:不受影响-漏洞代码不存在
一、漏洞信息 漏洞编号:[CVE-2024-56653](https://nvd.nist.gov/vuln/detail/CVE-2024-56653) 漏洞归属组件:[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: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:Bluetooth: btmtk: avoid UAF in btmtk_process_coredumphci_devcd_append may lead to the release of the skb, so it cannot beaccessed once it is called.==================================================================BUG: KASAN: slab-use-after-free in btmtk_process_coredump+0x2a7/0x2d0 [btmtk]Read of size 4 at addr ffff888033cfabb0 by task kworker/0:3/82CPU: 0 PID: 82 Comm: kworker/0:3 Tainted: G U 6.6.40-lockdep-03464-g1d8b4eb3060e #1 b0b3c1cc0c842735643fb411799d97921d1f688cHardware name: Google Yaviks_Ufs/Yaviks_Ufs, BIOS Google_Yaviks_Ufs.15217.552.0 05/07/2024Workqueue: events btusb_rx_work [btusb]Call Trace: <TASK> dump_stack_lvl+0xfd/0x150 print_report+0x131/0x780 kasan_report+0x177/0x1c0 btmtk_process_coredump+0x2a7/0x2d0 [btmtk 03edd567dd71a65958807c95a65db31d433e1d01] btusb_recv_acl_mtk+0x11c/0x1a0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec] btusb_rx_work+0x9e/0xe0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30 </TASK>Allocated by task 82: stack_trace_save+0xdc/0x190 kasan_set_track+0x4e/0x80 __kasan_slab_alloc+0x4e/0x60 kmem_cache_alloc+0x19f/0x360 skb_clone+0x132/0xf70 btusb_recv_acl_mtk+0x104/0x1a0 [btusb] btusb_rx_work+0x9e/0xe0 [btusb] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30Freed by task 1733: stack_trace_save+0xdc/0x190 kasan_set_track+0x4e/0x80 kasan_save_free_info+0x28/0xb0 ____kasan_slab_free+0xfd/0x170 kmem_cache_free+0x183/0x3f0 hci_devcd_rx+0x91a/0x2060 [bluetooth] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30The buggy address belongs to the object at ffff888033cfab40 which belongs to the cache skbuff_head_cache of size 232The buggy address is located 112 bytes inside of freed 232-byte region [ffff888033cfab40, ffff888033cfac28)The buggy address belongs to the physical page:page:00000000a174ba93 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x33cfahead:00000000a174ba93 order:1 entire_mapcount:0 nr_pages_mapped:0 pincount:0anon flags: 0x4000000000000840(slab|head|zone=1)page_type: 0xffffffff()raw: 4000000000000840 ffff888100848a00 0000000000000000 0000000000000001raw: 0000000000000000 0000000080190019 00000001ffffffff 0000000000000000page dumped because: kasan: bad access detectedMemory state around the buggy address: ffff888033cfaa80: fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc ffff888033cfab00: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb>ffff888033cfab80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff888033cfac00: fb fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc ffff888033cfac80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb==================================================================Check if we need to call hci_devcd_complete before callinghci_devcd_append. That requires that we check data->cd_info.cnt >=MTK_COREDUMP_NUM instead of data->cd_info.cnt > MTK_COREDUMP_NUM, as weincrement data->cd_info.cnt only once the call to hci_devcd_appendsucceeds. 漏洞公开时间:2024-12-27 23:15:25 漏洞创建时间:2025-02-05 10:34:33 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2024-56653 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/b548f5e9456c568155499d9ebac675c0d7a296e8 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/d20ff1d3cb40479789368f502eedb0a00e4161fc | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ecdcaea0e4057171ea4c3783e1cc1c900ad99125 | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-56653 | https://bugzilla.suse.com/show_bug.cgi?id=1235531 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-56653 | https://bugzilla.suse.com/show_bug.cgi?id=1235531 | | suse_bugzilla | https://git.kernel.org/stable/c/b548f5e9456c568155499d9ebac675c0d7a296e8 | https://bugzilla.suse.com/show_bug.cgi?id=1235531 | | suse_bugzilla | https://git.kernel.org/stable/c/d20ff1d3cb40479789368f502eedb0a00e4161fc | https://bugzilla.suse.com/show_bug.cgi?id=1235531 | | suse_bugzilla | https://git.kernel.org/stable/c/ecdcaea0e4057171ea4c3783e1cc1c900ad99125 | https://bugzilla.suse.com/show_bug.cgi?id=1235531 | | suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-56653.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1235531 | | suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2334538 | https://bugzilla.suse.com/show_bug.cgi?id=1235531 | | redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024122749-CVE-2024-56653-bb35@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2334538 | | debian | | https://security-tracker.debian.org/tracker/CVE-2024-56653 | </details> 漏洞分析指导链接: https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: openBrain开源漏洞感知系统 漏洞补丁信息: <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | linux_kernel | 6.6.67 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ecdcaea0e4057171ea4c3783e1cc1c900ad99125Issue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0b70151328781a89c89e4cf3fae21fc0e98d869e | linuxkernelcves | | linux_kernel | 6.12.6 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d20ff1d3cb40479789368f502eedb0a00e4161fcIssue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0b70151328781a89c89e4cf3fae21fc0e98d869e | linuxkernelcves | | linux_kernel | 6.13-rc3 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b548f5e9456c568155499d9ebac675c0d7a296e8Please | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0b70151328781a89c89e4cf3fae21fc0e98d869e | linuxkernelcves | </details> 二、漏洞分析结构反馈 影响性分析说明: In the Linux kernel, the following vulnerability has been resolved:Bluetooth: btmtk: avoid UAF in btmtk_process_coredumphci_devcd_append may lead to the release of the skb, so it cannot beaccessed once it is called.==================================================================BUG: KASAN: slab-use-after-free in btmtk_process_coredump+0x2a7/0x2d0 [btmtk]Read of size 4 at addr ffff888033cfabb0 by task kworker/0:3/82CPU: 0 PID: 82 Comm: kworker/0:3 Tainted: G U 6.6.40-lockdep-03464-g1d8b4eb3060e #1 b0b3c1cc0c842735643fb411799d97921d1f688cHardware name: Google Yaviks_Ufs/Yaviks_Ufs, BIOS Google_Yaviks_Ufs.15217.552.0 05/07/2024Workqueue: events btusb_rx_work [btusb]Call Trace: <TASK> dump_stack_lvl+0xfd/0x150 print_report+0x131/0x780 kasan_report+0x177/0x1c0 btmtk_process_coredump+0x2a7/0x2d0 [btmtk 03edd567dd71a65958807c95a65db31d433e1d01] btusb_recv_acl_mtk+0x11c/0x1a0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec] btusb_rx_work+0x9e/0xe0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30 </TASK>Allocated by task 82: stack_trace_save+0xdc/0x190 kasan_set_track+0x4e/0x80 __kasan_slab_alloc+0x4e/0x60 kmem_cache_alloc+0x19f/0x360 skb_clone+0x132/0xf70 btusb_recv_acl_mtk+0x104/0x1a0 [btusb] btusb_rx_work+0x9e/0xe0 [btusb] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30Freed by task 1733: stack_trace_save+0xdc/0x190 kasan_set_track+0x4e/0x80 kasan_save_free_info+0x28/0xb0 ____kasan_slab_free+0xfd/0x170 kmem_cache_free+0x183/0x3f0 hci_devcd_rx+0x91a/0x2060 [bluetooth] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30The buggy address belongs to the object at ffff888033cfab40 which belongs to the cache skbuff_head_cache of size 232The buggy address is located 112 bytes inside of freed 232-byte region [ffff888033cfab40, ffff888033cfac28)The buggy address belongs to the physical page:page:00000000a174ba93 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x33cfahead:00000000a174ba93 order:1 entire_mapcount:0 nr_pages_mapped:0 pincount:0anon flags: 0x4000000000000840(slab|head|zone=1)page_type: 0xffffffff()raw: 4000000000000840 ffff888100848a00 0000000000000000 0000000000000001raw: 0000000000000000 0000000080190019 00000001ffffffff 0000000000000000page dumped because: kasan: bad access detectedMemory state around the buggy address: ffff888033cfaa80: fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc ffff888033cfab00: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb>ffff888033cfab80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff888033cfac00: fb fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc ffff888033cfac80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb==================================================================Check if we need to call hci_devcd_complete before callinghci_devcd_append. That requires that we check data->cd_info.cnt >=MTK_COREDUMP_NUM instead of data->cd_info.cnt > MTK_COREDUMP_NUM, as weincrement data->cd_info.cnt only once the call to hci_devcd_appendsucceeds. 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-24.03-LTS-SP1(6.6.0):受影响 3.openEuler-20.03-LTS-SP4(4.19.90):不受影响 4.openEuler-22.03-LTS-SP3(5.10.0):不受影响 5.openEuler-22.03-LTS-SP4:不受影响 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-SP3(5.10.0):否 3.master(6.6.0):否 4.openEuler-24.03-LTS(6.6.0):否 5.openEuler-24.03-LTS-Next(6.6.0):否 6.openEuler-22.03-LTS-SP4:否 7.openEuler-24.03-LTS-SP1(6.6.0):否 原因说明: 1.openEuler-24.03-LTS(6.6.0):正常修复 2.openEuler-24.03-LTS-SP1(6.6.0):正常修复 3.master(6.6.0):不受影响-漏洞代码不能被攻击者触发 4.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发 5.openEuler-20.03-LTS-SP4(4.19.90):不受影响-漏洞代码不存在 6.openEuler-22.03-LTS-SP3(5.10.0):不受影响-漏洞代码不存在 7.openEuler-22.03-LTS-SP4:不受影响-漏洞代码不存在
Comments (
13
)
Sign in
to comment
Status
Done
Backlog
已挂起
Doing
Done
Declined
Assignees
Not set
sanglipeng
sanglipeng
Assignee
Collaborator
+Assign
+Mention
Labels
CVE/FIXED
sig/Kernel
Not set
Projects
Unprojected
Unprojected
Milestones
No related milestones
No related milestones
Pull Requests
None yet
None yet
Successfully merging a pull request will close this issue.
Branches
No related branch
Branches (
-
)
Tags (
-
)
Planed to start   -   Planed to end
-
Top level
Not Top
Top Level: High
Top Level: Medium
Top Level: Low
Priority
Not specified
Serious
Main
Secondary
Unimportant
Duration
(hours)
参与者(4)
1
https://gitee.com/src-openeuler/kernel.git
git@gitee.com:src-openeuler/kernel.git
src-openeuler
kernel
kernel
Going to Help Center
Search
Git 命令在线学习
如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大,如何减小?
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release(发行版)
将 PHP 项目自动发布到 packagist.org
Repository Report
Back to the top
Login prompt
This operation requires login to the code cloud account. Please log in before operating.
Go to login
No account. Register