{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80666 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80666 is a vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-80666 and fix it if it is affected.\n\nWhat it is: CVE-2026-80666 is a vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-80666 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-80666/ (Markdown: https://insights.sbomify.com/CVE-2026-80666/index.md)","id":"CVE-2026-80666","markdown":"https://insights.sbomify.com/CVE-2026-80666/index.md","name":"CVE-2026-80666","record":{"aliases":["BELL-CVE-2026-80666","DEBIAN-CVE-2026-80666","GHSA-53mq-p582-hhfx","UBUNTU-CVE-2026-80666"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel Bluetooth","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel Bluetooth SCO subsystem can cause a deadlock, leading to a local denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: sco: Fix a race condition in sco_sock_timeout()\n\nsco_sock_timeout() runs asynchronously and lock_sock(sk). If the socket\nis closing while the timer is running, it holds the same lock\n(lock_sock(sk)) twice, leading to a deadlock.\n\nCPU 0                      CPU 1\n====================       ======================\nsco_sock_close()\n                           sco_sock_timeout()\nlock_sock(sk) // \u003c-- LOCK\n  __sco_sock_close()\n    sco_chan_del()\n      sco_conn_put()\n\t      sco_conn_free()\n\t        disable_delayed_work_sync()\n\t                           lock(sk) // \u003c-- SAME LOCK\n\nFix this by moving disable_delayed_work_sync() outside of lock_sock(sk),\nensuring that no lock_sock(sk) is held before sco_sock_timeout().\n\nLockdep splat:\n\nWARNING: possible circular locking dependency detected\n6.13.0-rc4 #7 Not tainted\n\nsyz-executor292/9514 is trying to acquire lock:\nffff8881115d5070 ((work_completion)(\u0026(\u0026conn-\u003etimeout_work)-\u003ework)){+.+.}-{0:0}, at: rcu_lock_acquire sect/v6.13-rc4/./include/linux/rcupdate.h:337 [inline]\nffff8881115d5070 ((work_completion)(\u0026(\u0026conn-\u003etimeout_work)-\u003ework)){+.+.}-{0:0}, at: rcu_read_lock sect/v6.13-rc4/./include/linux/rcupdate.h:849 [inline]\nffff8881115d5070 ((work_completion)(\u0026(\u0026conn-\u003etimeout_work)-\u003ework)){+.+.}-{0:0}, at: start_flush_work sect/v6.13-rc4/kernel/workqueue.c:4137 [inline]\nffff8881115d5070 ((work_completion)(\u0026(\u0026conn-\u003etimeout_work)-\u003ework)){+.+.}-{0:0}, at: __flush_work+0xd1/0xc40 sect/v6.13-rc4/kernel/workqueue.c:4195\n\nbut task is already holding lock:\nffff88807db3a258 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: lock_sock sect/v6.13-rc4/./include/net/sock.h:1623 [inline]\nffff88807db3a258 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: sco_sock_close+0x25/0x100 sect/v6.13-rc4/net/bluetooth/sco.c:524\n\nwhich lock already depends on the new lock.\n\nthe existing dependency chain (in reverse order) is:\n\n-\u003e #1 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}:\n       lock_acquire+0x1c4/0x520 sect/v6.13-rc4/kernel/locking/lockdep.c:5849\n       lock_sock_nested+0x48/0x130 sect/v6.13-rc4/net/core/sock.c:3622\n       lock_sock sect/v6.13-rc4/./include/net/sock.h:1623 [inline]\n       sco_sock_timeout+0xbe/0x270 sect/v6.13-rc4/net/bluetooth/sco.c:158\n       process_one_work sect/v6.13-rc4/kernel/workqueue.c:3229 [inline]\n       process_scheduled_works+0xa99/0x18f0 sect/v6.13-rc4/kernel/workqueue.c:3310\n       worker_thread+0x8a9/0xd80 sect/v6.13-rc4/kernel/workqueue.c:3391\n       kthread+0x2c6/0x360 sect/v6.13-rc4/kernel/kthread.c:389\n       ret_from_fork+0x4e/0x80 sect/v6.13-rc4/arch/x86/kernel/process.c:147\n       ret_from_fork_asm+0x1a/0x30 sect/v6.13-rc4/arch/x86/entry/entry_64.S:244\n\n-\u003e #0 ((work_completion)(\u0026(\u0026conn-\u003etimeout_work)-\u003ework)){+.+.}-{0:0}:\n       check_prev_add sect/v6.13-rc4/kernel/locking/lockdep.c:3161 [inline]\n       check_prevs_add sect/v6.13-rc4/kernel/locking/lockdep.c:3280 [inline]\n       validate_chain+0x1888/0x5760 sect/v6.13-rc4/kernel/locking/lockdep.c:3904\n       __lock_acquire+0x13b4/0x2120 sect/v6.13-rc4/kernel/locking/lockdep.c:5226\n       lock_acquire+0x1c4/0x520 sect/v6.13-rc4/kernel/locking/lockdep.c:5849\n       touch_work_lockdep_map sect/v6.13-rc4/kernel/workqueue.c:3909 [inline]\n       start_flush_work sect/v6.13-rc4/kernel/workqueue.c:4163 [inline]\n       __flush_work+0x70f/0xc40 sect/v6.13-rc4/kernel/workqueue.c:4195\n       __cancel_work_sync sect/v6.13-rc4/kernel/workqueue.c:4351 [inline]\n       disable_delayed_work_sync+0xbb/0xf0 sect/v6.13-rc4/kernel/workqueue.c:4514\n       sco_conn_free sect/v6.13-rc4/net/bluetooth/sco.c:95 [inline]\n       kref_put sect/v6.13-rc4/./include/linux/kref.h:65 [inline]\n       sco_conn_put+0x18f/0x270 sect/v6.13-rc4/net/bluetooth/sco.c:107\n       sco_chan_del+0xe2/0x210 sect/v6.13-rc4/net/bluetooth/sco.c:236\n       sco_sock_close+0x8f/0x100 sect/v6.13-rc4/net/bluetooth/sco.c:526\n       sco_sock_release+0x62/0x2d0 sect/v6.13-rc4/net/blueto\n---truncated---","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Bluetooth: sco: Fix a race condition in sco_sock_timeout()","id":"CVE-2026-80666","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"net/mlx5: LAG, MPESW, Fix missing complete() on devcom error","id":"CVE-2026-80667"},"packages":[],"prev":{"headline":"KVM: arm64: nv: Inject SEA if kvm_translate_vncr() can't resolve PFN","id":"CVE-2026-80665"},"products":["Linux"],"published":"2026-08-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-28","vendors":["Linux"]},"summary":"A race condition in the Linux kernel Bluetooth SCO subsystem can cause a deadlock, leading to a local denial of service.","url":"https://insights.sbomify.com/CVE-2026-80666/"}