CVE-2024-54191

一、漏洞信息
漏洞编号：CVE-2024-54191
漏洞归属组件：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:Bluetooth: iso: Fix circular lock in iso_conn_big_syncThis fixes the circular locking dependency warning below, by reworkingiso_sock_recvmsg, to ensure that the socket lock is always releasedbefore calling a function that locks hdev.[ 561.670344] ======================================================[ 561.670346] WARNING: possible circular locking dependency detected[ 561.670349] 6.12.0-rc6+ #26 Not tainted[ 561.670351] ------------------------------------------------------[ 561.670353] iso-tester/3289 is trying to acquire lock:[ 561.670355] ffff88811f600078 (&hdev->lock){+.+.}-{3:3}, at: iso_conn_big_sync+0x73/0x260 [bluetooth][ 561.670405] but task is already holding lock:[ 561.670407] ffff88815af58258 (sk_lock-AF_BLUETOOTH){+.+.}-{0:0}, at: iso_sock_recvmsg+0xbf/0x500 [bluetooth][ 561.670450] which lock already depends on the new lock.[ 561.670452] the existing dependency chain (in reverse order) is:[ 561.670453] -> #2 (sk_lock-AF_BLUETOOTH){+.+.}-{0:0}:[ 561.670458] lock_acquire+0x7c/0xc0[ 561.670463] lock_sock_nested+0x3b/0xf0[ 561.670467] bt_accept_dequeue+0x1a5/0x4d0 [bluetooth][ 561.670510] iso_sock_accept+0x271/0x830 [bluetooth][ 561.670547] do_accept+0x3dd/0x610[ 561.670550] __sys_accept4+0xd8/0x170[ 561.670553] __x64_sys_accept+0x74/0xc0[ 561.670556] x64_sys_call+0x17d6/0x25f0[ 561.670559] do_syscall_64+0x87/0x150[ 561.670563] entry_SYSCALL_64_after_hwframe+0x76/0x7e[ 561.670567] -> #1 (sk_lock-AF_BLUETOOTH-BTPROTO_ISO){+.+.}-{0:0}:[ 561.670571] lock_acquire+0x7c/0xc0[ 561.670574] lock_sock_nested+0x3b/0xf0[ 561.670577] iso_sock_listen+0x2de/0xf30 [bluetooth][ 561.670617] __sys_listen_socket+0xef/0x130[ 561.670620] __x64_sys_listen+0xe1/0x190[ 561.670623] x64_sys_call+0x2517/0x25f0[ 561.670626] do_syscall_64+0x87/0x150[ 561.670629] entry_SYSCALL_64_after_hwframe+0x76/0x7e[ 561.670632] -> #0 (&hdev->lock){+.+.}-{3:3}:[ 561.670636] __lock_acquire+0x32ad/0x6ab0[ 561.670639] lock_acquire.part.0+0x118/0x360[ 561.670642] lock_acquire+0x7c/0xc0[ 561.670644] __mutex_lock+0x18d/0x12f0[ 561.670647] mutex_lock_nested+0x1b/0x30[ 561.670651] iso_conn_big_sync+0x73/0x260 [bluetooth][ 561.670687] iso_sock_recvmsg+0x3e9/0x500 [bluetooth][ 561.670722] sock_recvmsg+0x1d5/0x240[ 561.670725] sock_read_iter+0x27d/0x470[ 561.670727] vfs_read+0x9a0/0xd30[ 561.670731] ksys_read+0x1a8/0x250[ 561.670733] __x64_sys_read+0x72/0xc0[ 561.670736] x64_sys_call+0x1b12/0x25f0[ 561.670738] do_syscall_64+0x87/0x150[ 561.670741] entry_SYSCALL_64_after_hwframe+0x76/0x7e[ 561.670744] other info that might help us debug this:[ 561.670745] Chain exists of:&hdev->lock --> sk_lock-AF_BLUETOOTH-BTPROTO_ISO --> sk_lock-AF_BLUETOOTH[ 561.670751] Possible unsafe locking scenario:[ 561.670753] CPU0 CPU1[ 561.670754] ---- ----[ 561.670756] lock(sk_lock-AF_BLUETOOTH);[ 561.670758] lock(sk_lock AF_BLUETOOTH-BTPROTO_ISO);[ 561.670761] lock(sk_lock-AF_BLUETOOTH);[ 561.670764] lock(&hdev->lock);[ 561.670767] *** DEADLOCK ***
漏洞公开时间：2025-01-11 21:15:26
漏洞创建时间：2025-01-22 17:02:16
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2024-54191

更多参考(点击展开)

参考来源	参考链接	来源链接
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/7a17308c17880d259105f6e591eb1bc77b9612f0
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/cbe640d6cae590b9a7d81ce86fe9a90e83eec1d5
suse_bugzilla	http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-54191	https://bugzilla.suse.com/show_bug.cgi?id=1235717
suse_bugzilla	https://www.cve.org/CVERecord?id=CVE-2024-54191	https://bugzilla.suse.com/show_bug.cgi?id=1235717
suse_bugzilla	https://git.kernel.org/stable/c/7a17308c17880d259105f6e591eb1bc77b9612f0	https://bugzilla.suse.com/show_bug.cgi?id=1235717
suse_bugzilla	https://git.kernel.org/stable/c/cbe640d6cae590b9a7d81ce86fe9a90e83eec1d5	https://bugzilla.suse.com/show_bug.cgi?id=1235717
suse_bugzilla	https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-54191.mbox	https://bugzilla.suse.com/show_bug.cgi?id=1235717
redhat_bugzilla	https://lore.kernel.org/linux-cve-announce/2025011158-CVE-2024-54191-eeef@gregkh/T	https://bugzilla.redhat.com/show_bug.cgi?id=2337356
debian		https://security-tracker.debian.org/tracker/CVE-2024-54191

漏洞分析指导链接：
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
openBrain开源漏洞感知系统
漏洞补丁信息：

详情(点击展开)

影响的包	修复版本	修复补丁	问题引入补丁	来源
		https://git.kernel.org/stable/c/7a17308c17880d259105f6e591eb1bc77b9612f0		nvd
		https://git.kernel.org/stable/c/cbe640d6cae590b9a7d81ce86fe9a90e83eec1d5		nvd
linux_kernel	6.12.6	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=cbe640d6cae590b9a7d81ce86fe9a90e83eec1d5Issue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1360e5b6ce63d63d23223a659ca2bbafa30a53aa	linuxkernelcves
linux_kernel	6.13-rc3	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7a17308c17880d259105f6e591eb1bc77b9612f0Issue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1360e5b6ce63d63d23223a659ca2bbafa30a53aa	linuxkernelcves

二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:Bluetooth: iso: Fix circular lock in iso_conn_big_syncThis fixes the circular locking dependency warning below, by reworkingiso_sock_recvmsg, to ensure that the socket lock is always releasedbefore calling a function that locks hdev.[ 561.670344] ======================================================[ 561.670346] WARNING: possible circular locking dependency detected[ 561.670349] 6.12.0-rc6+ #26 Not tainted[ 561.670351] ------------------------------------------------------[ 561.670353] iso-tester/3289 is trying to acquire lock:[ 561.670355] ffff88811f600078 (&hdev->lock){+.+.}-{3:3}, at: iso_conn_big_sync+0x73/0x260 [bluetooth][ 561.670405] but task is already holding lock:[ 561.670407] ffff88815af58258 (sk_lock-AF_BLUETOOTH){+.+.}-{0:0}, at: iso_sock_recvmsg+0xbf/0x500 [bluetooth][ 561.670450] which lock already depends on the new lock.[ 561.670452] the existing dependency chain (in reverse order) is:[ 561.670453] -> #2 (sk_lock-AF_BLUETOOTH){+.+.}-{0:0}:[ 561.670458] lock_acquire+0x7c/0xc0[ 561.670463] lock_sock_nested+0x3b/0xf0[ 561.670467] bt_accept_dequeue+0x1a5/0x4d0 [bluetooth][ 561.670510] iso_sock_accept+0x271/0x830 [bluetooth][ 561.670547] do_accept+0x3dd/0x610[ 561.670550] __sys_accept4+0xd8/0x170[ 561.670553] __x64_sys_accept+0x74/0xc0[ 561.670556] x64_sys_call+0x17d6/0x25f0[ 561.670559] do_syscall_64+0x87/0x150[ 561.670563] entry_SYSCALL_64_after_hwframe+0x76/0x7e[ 561.670567] -> #1 (sk_lock-AF_BLUETOOTH-BTPROTO_ISO){+.+.}-{0:0}:[ 561.670571] lock_acquire+0x7c/0xc0[ 561.670574] lock_sock_nested+0x3b/0xf0[ 561.670577] iso_sock_listen+0x2de/0xf30 [bluetooth][ 561.670617] __sys_listen_socket+0xef/0x130[ 561.670620] __x64_sys_listen+0xe1/0x190[ 561.670623] x64_sys_call+0x2517/0x25f0[ 561.670626] do_syscall_64+0x87/0x150[ 561.670629] entry_SYSCALL_64_after_hwframe+0x76/0x7e[ 561.670632] -> #0 (&hdev->lock){+.+.}-{3:3}:[ 561.670636] __lock_acquire+0x32ad/0x6ab0[ 561.670639] lock_acquire.part.0+0x118/0x360[ 561.670642] lock_acquire+0x7c/0xc0[ 561.670644] __mutex_lock+0x18d/0x12f0[ 561.670647] mutex_lock_nested+0x1b/0x30[ 561.670651] iso_conn_big_sync+0x73/0x260 [bluetooth][ 561.670687] iso_sock_recvmsg+0x3e9/0x500 [bluetooth][ 561.670722] sock_recvmsg+0x1d5/0x240[ 561.670725] sock_read_iter+0x27d/0x470[ 561.670727] vfs_read+0x9a0/0xd30[ 561.670731] ksys_read+0x1a8/0x250[ 561.670733] __x64_sys_read+0x72/0xc0[ 561.670736] x64_sys_call+0x1b12/0x25f0[ 561.670738] do_syscall_64+0x87/0x150[ 561.670741] entry_SYSCALL_64_after_hwframe+0x76/0x7e[ 561.670744] other info that might help us debug this:[ 561.670745] Chain exists of:&hdev->lock --> sk_lock-AF_BLUETOOTH-BTPROTO_ISO --> sk_lock-AF_BLUETOOTH[ 561.670751] Possible unsafe locking scenario:[ 561.670753] CPU0 CPU1[ 561.670754] ---- ----[ 561.670756] lock(sk_lock-AF_BLUETOOTH);[ 561.670758] lock(sk_lock AF_BLUETOOTH-BTPROTO_ISO);[ 561.670761] lock(sk_lock-AF_BLUETOOTH);[ 561.670764] lock(&hdev->lock);[ 561.670767] *** DEADLOCK ***
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(5.10.0):不受影响
3.openEuler-22.03-LTS-SP4:不受影响
4.master(6.6.0):不受影响
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(5.10.0):否
3.master(6.6.0):否
4.openEuler-24.03-LTS:否
5.openEuler-24.03-LTS-Next:否
6.openEuler-22.03-LTS-SP4:否
7.openEuler-24.03-LTS-SP1:否

原因说明：
1.master(6.6.0):不受影响-漏洞代码不能被攻击者触发
2.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
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.openEuler-24.03-LTS:不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-SP1:不受影响-漏洞代码不存在

Hi openeuler-ci-bot, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: Kernel, and any of the maintainers.

@yangyingliang ,@jiaoff ,@guohaocs2c ,@hanjun-guo ,@woqidaideshi ,@newbeats ,@zhangyi089 ,@colyli ,@thundertown ,@htforge ,@chiqijun ,@lengchao ,@zhujianwei001 ,@kylin-mayukun ,@wangxiongfeng ,@wkfxxx ,@SuperSix173 ,@jentlestea ,@oskernel0719 ,@gasonchen
issue处理注意事项:
1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.

影响性分析说明:

openEuler评分: (评分和向量)

受影响版本排查(受影响/不受影响):
1.master(6.6.0):
2.openEuler-20.03-LTS-SP4(4.19.90):
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.openEuler-24.03-LTS-Next(6.6.0):
7.openEuler-24.03-LTS-SP1(6.6.0):

修复是否涉及abi变化(是/否)：
1.master(6.6.0):
2.openEuler-20.03-LTS-SP4(4.19.90):
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.openEuler-24.03-LTS-Next(6.6.0):
7.openEuler-24.03-LTS-SP1(6.6.0):

原因说明：
1.master(6.6.0):
2.openEuler-20.03-LTS-SP4(4.19.90):
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.openEuler-24.03-LTS-Next(6.6.0):
7.openEuler-24.03-LTS-SP1(6.6.0):

原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如master版本分支受影响，那原因说明只能是受影响对应的原因之一!)：

分支状态	原因说明
受影响	正常修复
受影响	暂不修复-漏洞仍在分析中
受影响	暂不修复-暂无解决方案或补丁
受影响	暂不修复-待升级版本修复
受影响	不修复-超出修复范围
受影响	不修复-特殊原因导致不再修复
不受影响	不受影响-组件不存在
不受影响	不受影响-已有内置的内联控制或缓解措施
不受影响	不受影响-漏洞代码不能被攻击者触发
不受影响	不受影响-漏洞代码不在执行路径
不受影响	不受影响-漏洞代码不存在

issue处理具体操作请参考:
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://gitee.com/help/articles/4142

参考网址	关联pr	状态	补丁链接
https://nvd.nist.gov/vuln/detail/CVE-2024-54191	None	None	https://git.kernel.org/stable/c/cbe640d6cae590b9a7d81ce86fe9a90e83eec1d5 https://git.kernel.org/stable/c/7a17308c17880d259105f6e591eb1bc77b9612f0
https://www.opencve.io/cve/CVE-2024-54191
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2024-54191
https://security-tracker.debian.org/tracker/CVE-2024-54191	None	None	https://git.kernel.org/linus/7a17308c17880d259105f6e591eb1bc77b9612f0

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用CVE补丁工具。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1

CVE-2024-54191

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: iso: Fix circular lock in iso_conn_big_sync

This fixes the circular locking dependency warning below, by reworking
iso_sock_recvmsg, to ensure that the socket lock is always released
before calling a function that locks hdev.

[ 561.670344] ======================================================
[ 561.670346] WARNING: possible circular locking dependency detected
[ 561.670349] 6.12.0-rc6+ #26 Not tainted
[ 561.670351] ------------------------------------------------------
[ 561.670353] iso-tester/3289 is trying to acquire lock:
[ 561.670355] ffff88811f600078 (&hdev->lock){+.+.}-{3:3},
at: iso_conn_big_sync+0x73/0x260 [bluetooth]
[ 561.670405]
but task is already holding lock:
[ 561.670407] ffff88815af58258 (sk_lock-AF_BLUETOOTH){+.+.}-{0:0},
at: iso_sock_recvmsg+0xbf/0x500 [bluetooth]
[ 561.670450]
which lock already depends on the new lock.

[ 561.670452]
the existing dependency chain (in reverse order) is:
[ 561.670453]
-> #2 (sk_lock-AF_BLUETOOTH){+.+.}-{0:0}:
[ 561.670458] lock_acquire+0x7c/0xc0
[ 561.670463] lock_sock_nested+0x3b/0xf0
[ 561.670467] bt_accept_dequeue+0x1a5/0x4d0 [bluetooth]
[ 561.670510] iso_sock_accept+0x271/0x830 [bluetooth]
[ 561.670547] do_accept+0x3dd/0x610
[ 561.670550] __sys_accept4+0xd8/0x170
[ 561.670553] __x64_sys_accept+0x74/0xc0
[ 561.670556] x64_sys_call+0x17d6/0x25f0
[ 561.670559] do_syscall_64+0x87/0x150
[ 561.670563] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 561.670567]
-> #1 (sk_lock-AF_BLUETOOTH-BTPROTO_ISO){+.+.}-{0:0}:
[ 561.670571] lock_acquire+0x7c/0xc0
[ 561.670574] lock_sock_nested+0x3b/0xf0
[ 561.670577] iso_sock_listen+0x2de/0xf30 [bluetooth]
[ 561.670617] __sys_listen_socket+0xef/0x130
[ 561.670620] __x64_sys_listen+0xe1/0x190
[ 561.670623] x64_sys_call+0x2517/0x25f0
[ 561.670626] do_syscall_64+0x87/0x150
[ 561.670629] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 561.670632]
-> #0 (&hdev->lock){+.+.}-{3:3}:
[ 561.670636] __lock_acquire+0x32ad/0x6ab0
[ 561.670639] lock_acquire.part.0+0x118/0x360
[ 561.670642] lock_acquire+0x7c/0xc0
[ 561.670644] __mutex_lock+0x18d/0x12f0
[ 561.670647] mutex_lock_nested+0x1b/0x30
[ 561.670651] iso_conn_big_sync+0x73/0x260 [bluetooth]
[ 561.670687] iso_sock_recvmsg+0x3e9/0x500 [bluetooth]
[ 561.670722] sock_recvmsg+0x1d5/0x240
[ 561.670725] sock_read_iter+0x27d/0x470
[ 561.670727] vfs_read+0x9a0/0xd30
[ 561.670731] ksys_read+0x1a8/0x250
[ 561.670733] __x64_sys_read+0x72/0xc0
[ 561.670736] x64_sys_call+0x1b12/0x25f0
[ 561.670738] do_syscall_64+0x87/0x150
[ 561.670741] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 561.670744]
other info that might help us debug this:

[ 561.670745] Chain exists of:
&hdev->lock --> sk_lock-AF_BLUETOOTH-BTPROTO_ISO --> sk_lock-AF_BLUETOOTH

[ 561.670751] Possible unsafe locking scenario:

[ 561.670753] CPU0 CPU1
[ 561.670754] ---- ----
[ 561.670756] lock(sk_lock-AF_BLUETOOTH);
[ 561.670758] lock(sk_lock
AF_BLUETOOTH-BTPROTO_ISO);
[ 561.670761] lock(sk_lock-AF_BLUETOOTH);
[ 561.670764] lock(&hdev->lock);
[ 561.670767]
*** DEADLOCK ***

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

受影响版本排查(受影响/不受影响):
1.master(6.1.0):不受影响
2.openEuler-20.03-LTS-SP4:不受影响
3.openEuler-22.03-LTS-SP3:不受影响
4.openEuler-22.03-LTS-SP4:不受影响
5.openEuler-24.03-LTS:不受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:不受影响

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

原因说明：
1.master(23.08.5):不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:不受影响-漏洞代码不存在
4.openEuler-22.03-LTS-SP3:不受影响-漏洞代码不存在
5.openEuler-22.03-LTS-SP4:不受影响-漏洞代码不存在
6.openEuler-24.03-LTS:不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
8.openEuler-24.03-LTS-SP1:不受影响-漏洞代码不存在

@sanglipeng 经过 cve-manager 解析, 已分析的内容如下表所示:

状态	分析项目	内容
已分析	1.影响性分析说明	In the Linux kernel, the following vulnerability has been resolved:Bluetooth: iso: Fix circular lock in iso_conn_big_syncThis fixes the circular locking dependency warning below, by reworkingiso_sock_recvmsg, to ensure that the socket lock is always releasedbefore calling a function that locks hdev.[ 561.670344] ======================================================[ 561.670346] WARNING: possible circular locking dependency detected[ 561.670349] 6.12.0-rc6+ #26 Not tainted[ 561.670351] ------------------------------------------------------[ 561.670353] iso-tester/3289 is trying to acquire lock:[ 561.670355] ffff88811f600078 (&hdev->lock){+.+.}-{3:3}, at: iso_conn_big_sync+0x73/0x260 [bluetooth][ 561.670405] but task is already holding lock:[ 561.670407] ffff88815af58258 (sk_lock-AF_BLUETOOTH){+.+.}-{0:0}, at: iso_sock_recvmsg+0xbf/0x500 [bluetooth][ 561.670450] which lock already depends on the new lock.[ 561.670452] the existing dependency chain (in reverse order) is:[ 561.670453] -> #2 (sk_lock-AF_BLUETOOTH){+.+.}-{0:0}:[ 561.670458] lock_acquire+0x7c/0xc0[ 561.670463] lock_sock_nested+0x3b/0xf0[ 561.670467] bt_accept_dequeue+0x1a5/0x4d0 [bluetooth][ 561.670510] iso_sock_accept+0x271/0x830 [bluetooth][ 561.670547] do_accept+0x3dd/0x610[ 561.670550] __sys_accept4+0xd8/0x170[ 561.670553] __x64_sys_accept+0x74/0xc0[ 561.670556] x64_sys_call+0x17d6/0x25f0[ 561.670559] do_syscall_64+0x87/0x150[ 561.670563] entry_SYSCALL_64_after_hwframe+0x76/0x7e[ 561.670567] -> #1 (sk_lock-AF_BLUETOOTH-BTPROTO_ISO){+.+.}-{0:0}:[ 561.670571] lock_acquire+0x7c/0xc0[ 561.670574] lock_sock_nested+0x3b/0xf0[ 561.670577] iso_sock_listen+0x2de/0xf30 [bluetooth][ 561.670617] __sys_listen_socket+0xef/0x130[ 561.670620] __x64_sys_listen+0xe1/0x190[ 561.670623] x64_sys_call+0x2517/0x25f0[ 561.670626] do_syscall_64+0x87/0x150[ 561.670629] entry_SYSCALL_64_after_hwframe+0x76/0x7e[ 561.670632] -> #0 (&hdev->lock){+.+.}-{3:3}:[ 561.670636] __lock_acquire+0x32ad/0x6ab0[ 561.670639] lock_acquire.part.0+0x118/0x360[ 561.670642] lock_acquire+0x7c/0xc0[ 561.670644] __mutex_lock+0x18d/0x12f0[ 561.670647] mutex_lock_nested+0x1b/0x30[ 561.670651] iso_conn_big_sync+0x73/0x260 [bluetooth][ 561.670687] iso_sock_recvmsg+0x3e9/0x500 [bluetooth][ 561.670722] sock_recvmsg+0x1d5/0x240[ 561.670725] sock_read_iter+0x27d/0x470[ 561.670727] vfs_read+0x9a0/0xd30[ 561.670731] ksys_read+0x1a8/0x250[ 561.670733] __x64_sys_read+0x72/0xc0[ 561.670736] x64_sys_call+0x1b12/0x25f0[ 561.670738] do_syscall_64+0x87/0x150[ 561.670741] entry_SYSCALL_64_after_hwframe+0x76/0x7e[ 561.670744] other info that might help us debug this:[ 561.670745] Chain exists of:&hdev->lock --> sk_lock-AF_BLUETOOTH-BTPROTO_ISO --> sk_lock-AF_BLUETOOTH[ 561.670751] Possible unsafe locking scenario:[ 561.670753] CPU0 CPU1[ 561.670754] ---- ----[ 561.670756] lock(sk_lock-AF_BLUETOOTH);[ 561.670758] lock(sk_lock AF_BLUETOOTH-BTPROTO_ISO);[ 561.670761] lock(sk_lock-AF_BLUETOOTH);[ 561.670764] lock(&hdev->lock);[ 561.670767] * DEADLOCK *
已分析	2.openEulerScore	5.5
已分析	3.openEulerVector	AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
已分析	4.受影响版本排查	master:不受影响,openEuler-20.03-LTS-SP4:不受影响,openEuler-22.03-LTS-SP3:不受影响,openEuler-22.03-LTS-SP4:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响,openEuler-24.03-LTS-SP1:不受影响
已分析	5.是否涉及abi变化	master:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP3:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-24.03-LTS-SP1:否
已分析	6.原因说明	master:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发,openEuler-20.03-LTS-SP4:不受影响-漏洞代码不存在,openEuler-22.03-LTS-SP3:不受影响-漏洞代码不存在,openEuler-22.03-LTS-SP4:不受影响-漏洞代码不存在,openEuler-24.03-LTS:不受影响-漏洞代码不存在,openEuler-24.03-LTS-SP1:不受影响-漏洞代码不存在

请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.

CVE-2024-54191

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: iso: Fix circular lock in iso_conn_big_sync

This fixes the circular locking dependency warning below, by reworking
iso_sock_recvmsg, to ensure that the socket lock is always released
before calling a function that locks hdev.

[ 561.670344] ======================================================
[ 561.670346] WARNING: possible circular locking dependency detected
[ 561.670349] 6.12.0-rc6+ #26 Not tainted
[ 561.670351] ------------------------------------------------------
[ 561.670353] iso-tester/3289 is trying to acquire lock:
[ 561.670355] ffff88811f600078 (&hdev->lock){+.+.}-{3:3},
at: iso_conn_big_sync+0x73/0x260 [bluetooth]
[ 561.670405]
but task is already holding lock:
[ 561.670407] ffff88815af58258 (sk_lock-AF_BLUETOOTH){+.+.}-{0:0},
at: iso_sock_recvmsg+0xbf/0x500 [bluetooth]
[ 561.670450]
which lock already depends on the new lock.

[ 561.670452]
the existing dependency chain (in reverse order) is:
[ 561.670453]
-> #2 (sk_lock-AF_BLUETOOTH){+.+.}-{0:0}:
[ 561.670458] lock_acquire+0x7c/0xc0
[ 561.670463] lock_sock_nested+0x3b/0xf0
[ 561.670467] bt_accept_dequeue+0x1a5/0x4d0 [bluetooth]
[ 561.670510] iso_sock_accept+0x271/0x830 [bluetooth]
[ 561.670547] do_accept+0x3dd/0x610
[ 561.670550] __sys_accept4+0xd8/0x170
[ 561.670553] __x64_sys_accept+0x74/0xc0
[ 561.670556] x64_sys_call+0x17d6/0x25f0
[ 561.670559] do_syscall_64+0x87/0x150
[ 561.670563] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 561.670567]
-> #1 (sk_lock-AF_BLUETOOTH-BTPROTO_ISO){+.+.}-{0:0}:
[ 561.670571] lock_acquire+0x7c/0xc0
[ 561.670574] lock_sock_nested+0x3b/0xf0
[ 561.670577] iso_sock_listen+0x2de/0xf30 [bluetooth]
[ 561.670617] __sys_listen_socket+0xef/0x130
[ 561.670620] __x64_sys_listen+0xe1/0x190
[ 561.670623] x64_sys_call+0x2517/0x25f0
[ 561.670626] do_syscall_64+0x87/0x150
[ 561.670629] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 561.670632]
-> #0 (&hdev->lock){+.+.}-{3:3}:
[ 561.670636] __lock_acquire+0x32ad/0x6ab0
[ 561.670639] lock_acquire.part.0+0x118/0x360
[ 561.670642] lock_acquire+0x7c/0xc0
[ 561.670644] __mutex_lock+0x18d/0x12f0
[ 561.670647] mutex_lock_nested+0x1b/0x30
[ 561.670651] iso_conn_big_sync+0x73/0x260 [bluetooth]
[ 561.670687] iso_sock_recvmsg+0x3e9/0x500 [bluetooth]
[ 561.670722] sock_recvmsg+0x1d5/0x240
[ 561.670725] sock_read_iter+0x27d/0x470
[ 561.670727] vfs_read+0x9a0/0xd30
[ 561.670731] ksys_read+0x1a8/0x250
[ 561.670733] __x64_sys_read+0x72/0xc0
[ 561.670736] x64_sys_call+0x1b12/0x25f0
[ 561.670738] do_syscall_64+0x87/0x150
[ 561.670741] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 561.670744]
other info that might help us debug this:

[ 561.670745] Chain exists of:
&hdev->lock --> sk_lock-AF_BLUETOOTH-BTPROTO_ISO --> sk_lock-AF_BLUETOOTH

[ 561.670751] Possible unsafe locking scenario:

[ 561.670753] CPU0 CPU1
[ 561.670754] ---- ----
[ 561.670756] lock(sk_lock-AF_BLUETOOTH);
[ 561.670758] lock(sk_lock
AF_BLUETOOTH-BTPROTO_ISO);
[ 561.670761] lock(sk_lock-AF_BLUETOOTH);
[ 561.670764] lock(&hdev->lock);
[ 561.670767]
*** DEADLOCK ***

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP4:不受影响
2.openEuler-22.03-LTS-SP3:不受影响
3.openEuler-22.03-LTS-SP4:不受影响
4.master(6.6.0):不受影响
5.openEuler-24.03-LTS:不受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:不受影响

原因说明:
1.openEuler-20.03-LTS-SP4:不受影响-漏洞代码不存在
2.openEuler-22.03-LTS-SP3:不受影响-漏洞代码不存在
3.openEuler-22.03-LTS-SP4:不受影响-漏洞代码不存在
4.master(6.6.0):不受影响-漏洞代码不能被攻击者触发
5.openEuler-24.03-LTS:不受影响-漏洞代码不存在
6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1:不受影响-漏洞代码不存在

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

===========================================================

@sanglipeng 经过 cve-manager 解析, 已分析的内容如下表所示:

状态	分析项目	内容
已分析	1.影响性分析说明	In the Linux kernel, the following vulnerability has been resolved:Bluetooth: iso: Fix circular lock in iso_conn_big_syncThis fixes the circular locking dependency warning below, by reworkingiso_sock_recvmsg, to ensure that the socket lock is always releasedbefore calling a function that locks hdev.[ 561.670344] ======================================================[ 561.670346] WARNING: possible circular locking dependency detected[ 561.670349] 6.12.0-rc6+ #26 Not tainted[ 561.670351] ------------------------------------------------------[ 561.670353] iso-tester/3289 is trying to acquire lock:[ 561.670355] ffff88811f600078 (&hdev->lock){+.+.}-{3:3}, at: iso_conn_big_sync+0x73/0x260 [bluetooth][ 561.670405] but task is already holding lock:[ 561.670407] ffff88815af58258 (sk_lock-AF_BLUETOOTH){+.+.}-{0:0}, at: iso_sock_recvmsg+0xbf/0x500 [bluetooth][ 561.670450] which lock already depends on the new lock.[ 561.670452] the existing dependency chain (in reverse order) is:[ 561.670453] -> #2 (sk_lock-AF_BLUETOOTH){+.+.}-{0:0}:[ 561.670458] lock_acquire+0x7c/0xc0[ 561.670463] lock_sock_nested+0x3b/0xf0[ 561.670467] bt_accept_dequeue+0x1a5/0x4d0 [bluetooth][ 561.670510] iso_sock_accept+0x271/0x830 [bluetooth][ 561.670547] do_accept+0x3dd/0x610[ 561.670550] __sys_accept4+0xd8/0x170[ 561.670553] __x64_sys_accept+0x74/0xc0[ 561.670556] x64_sys_call+0x17d6/0x25f0[ 561.670559] do_syscall_64+0x87/0x150[ 561.670563] entry_SYSCALL_64_after_hwframe+0x76/0x7e[ 561.670567] -> #1 (sk_lock-AF_BLUETOOTH-BTPROTO_ISO){+.+.}-{0:0}:[ 561.670571] lock_acquire+0x7c/0xc0[ 561.670574] lock_sock_nested+0x3b/0xf0[ 561.670577] iso_sock_listen+0x2de/0xf30 [bluetooth][ 561.670617] __sys_listen_socket+0xef/0x130[ 561.670620] __x64_sys_listen+0xe1/0x190[ 561.670623] x64_sys_call+0x2517/0x25f0[ 561.670626] do_syscall_64+0x87/0x150[ 561.670629] entry_SYSCALL_64_after_hwframe+0x76/0x7e[ 561.670632] -> #0 (&hdev->lock){+.+.}-{3:3}:[ 561.670636] __lock_acquire+0x32ad/0x6ab0[ 561.670639] lock_acquire.part.0+0x118/0x360[ 561.670642] lock_acquire+0x7c/0xc0[ 561.670644] __mutex_lock+0x18d/0x12f0[ 561.670647] mutex_lock_nested+0x1b/0x30[ 561.670651] iso_conn_big_sync+0x73/0x260 [bluetooth][ 561.670687] iso_sock_recvmsg+0x3e9/0x500 [bluetooth][ 561.670722] sock_recvmsg+0x1d5/0x240[ 561.670725] sock_read_iter+0x27d/0x470[ 561.670727] vfs_read+0x9a0/0xd30[ 561.670731] ksys_read+0x1a8/0x250[ 561.670733] __x64_sys_read+0x72/0xc0[ 561.670736] x64_sys_call+0x1b12/0x25f0[ 561.670738] do_syscall_64+0x87/0x150[ 561.670741] entry_SYSCALL_64_after_hwframe+0x76/0x7e[ 561.670744] other info that might help us debug this:[ 561.670745] Chain exists of:&hdev->lock --> sk_lock-AF_BLUETOOTH-BTPROTO_ISO --> sk_lock-AF_BLUETOOTH[ 561.670751] Possible unsafe locking scenario:[ 561.670753] CPU0 CPU1[ 561.670754] ---- ----[ 561.670756] lock(sk_lock-AF_BLUETOOTH);[ 561.670758] lock(sk_lock AF_BLUETOOTH-BTPROTO_ISO);[ 561.670761] lock(sk_lock-AF_BLUETOOTH);[ 561.670764] lock(&hdev->lock);[ 561.670767] * DEADLOCK *
已分析	2.openEulerScore	5.5
已分析	3.openEulerVector	AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
已分析	4.受影响版本排查	openEuler-20.03-LTS-SP4:不受影响,openEuler-22.03-LTS-SP3:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响,openEuler-24.03-LTS-SP1:不受影响
已分析	5.是否涉及abi变化	openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS-SP1:否
已分析	6.原因说明	master:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发,openEuler-20.03-LTS-SP4:不受影响-漏洞代码不存在,openEuler-22.03-LTS-SP3:不受影响-漏洞代码不存在,openEuler-22.03-LTS-SP4:不受影响-漏洞代码不存在,openEuler-24.03-LTS:不受影响-漏洞代码不存在,openEuler-24.03-LTS-SP1:不受影响-漏洞代码不存在

请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.

CVE-2024-54191

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: iso: Fix circular lock in iso_conn_big_sync

This fixes the circular locking dependency warning below, by reworking
iso_sock_recvmsg, to ensure that the socket lock is always released
before calling a function that locks hdev.

[ 561.670344] ======================================================
[ 561.670346] WARNING: possible circular locking dependency detected
[ 561.670349] 6.12.0-rc6+ #26 Not tainted
[ 561.670351] ------------------------------------------------------
[ 561.670353] iso-tester/3289 is trying to acquire lock:
[ 561.670355] ffff88811f600078 (&hdev->lock){+.+.}-{3:3},
at: iso_conn_big_sync+0x73/0x260 [bluetooth]
[ 561.670405]
but task is already holding lock:
[ 561.670407] ffff88815af58258 (sk_lock-AF_BLUETOOTH){+.+.}-{0:0},
at: iso_sock_recvmsg+0xbf/0x500 [bluetooth]
[ 561.670450]
which lock already depends on the new lock.

[ 561.670452]
the existing dependency chain (in reverse order) is:
[ 561.670453]
-> #2 (sk_lock-AF_BLUETOOTH){+.+.}-{0:0}:
[ 561.670458] lock_acquire+0x7c/0xc0
[ 561.670463] lock_sock_nested+0x3b/0xf0
[ 561.670467] bt_accept_dequeue+0x1a5/0x4d0 [bluetooth]
[ 561.670510] iso_sock_accept+0x271/0x830 [bluetooth]
[ 561.670547] do_accept+0x3dd/0x610
[ 561.670550] __sys_accept4+0xd8/0x170
[ 561.670553] __x64_sys_accept+0x74/0xc0
[ 561.670556] x64_sys_call+0x17d6/0x25f0
[ 561.670559] do_syscall_64+0x87/0x150
[ 561.670563] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 561.670567]
-> #1 (sk_lock-AF_BLUETOOTH-BTPROTO_ISO){+.+.}-{0:0}:
[ 561.670571] lock_acquire+0x7c/0xc0
[ 561.670574] lock_sock_nested+0x3b/0xf0
[ 561.670577] iso_sock_listen+0x2de/0xf30 [bluetooth]
[ 561.670617] __sys_listen_socket+0xef/0x130
[ 561.670620] __x64_sys_listen+0xe1/0x190
[ 561.670623] x64_sys_call+0x2517/0x25f0
[ 561.670626] do_syscall_64+0x87/0x150
[ 561.670629] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 561.670632]
-> #0 (&hdev->lock){+.+.}-{3:3}:
[ 561.670636] __lock_acquire+0x32ad/0x6ab0
[ 561.670639] lock_acquire.part.0+0x118/0x360
[ 561.670642] lock_acquire+0x7c/0xc0
[ 561.670644] __mutex_lock+0x18d/0x12f0
[ 561.670647] mutex_lock_nested+0x1b/0x30
[ 561.670651] iso_conn_big_sync+0x73/0x260 [bluetooth]
[ 561.670687] iso_sock_recvmsg+0x3e9/0x500 [bluetooth]
[ 561.670722] sock_recvmsg+0x1d5/0x240
[ 561.670725] sock_read_iter+0x27d/0x470
[ 561.670727] vfs_read+0x9a0/0xd30
[ 561.670731] ksys_read+0x1a8/0x250
[ 561.670733] __x64_sys_read+0x72/0xc0
[ 561.670736] x64_sys_call+0x1b12/0x25f0
[ 561.670738] do_syscall_64+0x87/0x150
[ 561.670741] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 561.670744]
other info that might help us debug this:

[ 561.670745] Chain exists of:
&hdev->lock --> sk_lock-AF_BLUETOOTH-BTPROTO_ISO --> sk_lock-AF_BLUETOOTH

[ 561.670751] Possible unsafe locking scenario:

[ 561.670753] CPU0 CPU1
[ 561.670754] ---- ----
[ 561.670756] lock(sk_lock-AF_BLUETOOTH);
[ 561.670758] lock(sk_lock
AF_BLUETOOTH-BTPROTO_ISO);
[ 561.670761] lock(sk_lock-AF_BLUETOOTH);
[ 561.670764] lock(&hdev->lock);
[ 561.670767]
*** DEADLOCK ***

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP4:不受影响
2.openEuler-22.03-LTS-SP3:不受影响
3.openEuler-22.03-LTS-SP4:不受影响
4.master(6.6.0):不受影响
5.openEuler-24.03-LTS:不受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:不受影响

原因说明:
1.openEuler-20.03-LTS-SP4:不受影响-漏洞代码不存在
2.openEuler-22.03-LTS-SP3:不受影响-漏洞代码不存在
3.openEuler-22.03-LTS-SP4:不受影响-漏洞代码不存在
4.master(6.6.0):不受影响-漏洞代码不能被攻击者触发
5.openEuler-24.03-LTS:不受影响-漏洞代码不存在
6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1:不受影响-漏洞代码不存在

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

===========================================================

CVE-2024-54191

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: iso: Fix circular lock in iso_conn_big_sync

This fixes the circular locking dependency warning below, by reworking
iso_sock_recvmsg, to ensure that the socket lock is always released
before calling a function that locks hdev.

[ 561.670344] ======================================================
[ 561.670346] WARNING: possible circular locking dependency detected
[ 561.670349] 6.12.0-rc6+ #26 Not tainted
[ 561.670351] ------------------------------------------------------
[ 561.670353] iso-tester/3289 is trying to acquire lock:
[ 561.670355] ffff88811f600078 (&hdev->lock){+.+.}-{3:3},
at: iso_conn_big_sync+0x73/0x260 [bluetooth]
[ 561.670405]
but task is already holding lock:
[ 561.670407] ffff88815af58258 (sk_lock-AF_BLUETOOTH){+.+.}-{0:0},
at: iso_sock_recvmsg+0xbf/0x500 [bluetooth]
[ 561.670450]
which lock already depends on the new lock.

[ 561.670452]
the existing dependency chain (in reverse order) is:
[ 561.670453]
-> #2 (sk_lock-AF_BLUETOOTH){+.+.}-{0:0}:
[ 561.670458] lock_acquire+0x7c/0xc0
[ 561.670463] lock_sock_nested+0x3b/0xf0
[ 561.670467] bt_accept_dequeue+0x1a5/0x4d0 [bluetooth]
[ 561.670510] iso_sock_accept+0x271/0x830 [bluetooth]
[ 561.670547] do_accept+0x3dd/0x610
[ 561.670550] __sys_accept4+0xd8/0x170
[ 561.670553] __x64_sys_accept+0x74/0xc0
[ 561.670556] x64_sys_call+0x17d6/0x25f0
[ 561.670559] do_syscall_64+0x87/0x150
[ 561.670563] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 561.670567]
-> #1 (sk_lock-AF_BLUETOOTH-BTPROTO_ISO){+.+.}-{0:0}:
[ 561.670571] lock_acquire+0x7c/0xc0
[ 561.670574] lock_sock_nested+0x3b/0xf0
[ 561.670577] iso_sock_listen+0x2de/0xf30 [bluetooth]
[ 561.670617] __sys_listen_socket+0xef/0x130
[ 561.670620] __x64_sys_listen+0xe1/0x190
[ 561.670623] x64_sys_call+0x2517/0x25f0
[ 561.670626] do_syscall_64+0x87/0x150
[ 561.670629] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 561.670632]
-> #0 (&hdev->lock){+.+.}-{3:3}:
[ 561.670636] __lock_acquire+0x32ad/0x6ab0
[ 561.670639] lock_acquire.part.0+0x118/0x360
[ 561.670642] lock_acquire+0x7c/0xc0
[ 561.670644] __mutex_lock+0x18d/0x12f0
[ 561.670647] mutex_lock_nested+0x1b/0x30
[ 561.670651] iso_conn_big_sync+0x73/0x260 [bluetooth]
[ 561.670687] iso_sock_recvmsg+0x3e9/0x500 [bluetooth]
[ 561.670722] sock_recvmsg+0x1d5/0x240
[ 561.670725] sock_read_iter+0x27d/0x470
[ 561.670727] vfs_read+0x9a0/0xd30
[ 561.670731] ksys_read+0x1a8/0x250
[ 561.670733] __x64_sys_read+0x72/0xc0
[ 561.670736] x64_sys_call+0x1b12/0x25f0
[ 561.670738] do_syscall_64+0x87/0x150
[ 561.670741] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 561.670744]
other info that might help us debug this:

[ 561.670745] Chain exists of:
&hdev->lock --> sk_lock-AF_BLUETOOTH-BTPROTO_ISO --> sk_lock-AF_BLUETOOTH

[ 561.670751] Possible unsafe locking scenario:

[ 561.670753] CPU0 CPU1
[ 561.670754] ---- ----
[ 561.670756] lock(sk_lock-AF_BLUETOOTH);
[ 561.670758] lock(sk_lock
AF_BLUETOOTH-BTPROTO_ISO);
[ 561.670761] lock(sk_lock-AF_BLUETOOTH);
[ 561.670764] lock(&hdev->lock);
[ 561.670767]
*** DEADLOCK ***

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP4:不受影响
2.openEuler-22.03-LTS-SP3:不受影响
3.openEuler-22.03-LTS-SP4:不受影响
4.master(6.6.0):不受影响
5.openEuler-24.03-LTS:不受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:不受影响

原因说明:
1.openEuler-20.03-LTS-SP4:不受影响-漏洞代码不存在
2.openEuler-22.03-LTS-SP3:不受影响-漏洞代码不存在
3.openEuler-22.03-LTS-SP4:不受影响-漏洞代码不存在
4.master(6.6.0):不受影响-漏洞代码不能被攻击者触发
5.openEuler-24.03-LTS:不受影响-漏洞代码不存在
6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1:不受影响-漏洞代码不存在

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

===========================================================

src-openEuler/kernel

内容风险标识

评论 (9)

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

内容风险标识

CVE-2024-54191

评论 (9)

搜索帮助

src-openEuler/kernel