{"id":82296,"date":"2026-07-20T20:48:22","date_gmt":"2026-07-20T17:18:22","guid":{"rendered":"https:\/\/afaghhosting.net\/blog\/cve-2026-64206-bluetooth-l2cap-cancel-pending_rx_work-before-taking-conn-lock\/"},"modified":"2026-07-20T20:48:22","modified_gmt":"2026-07-20T17:18:22","slug":"cve-2026-64206-bluetooth-l2cap-cancel-pending_rx_work-before-taking-conn-lock","status":"publish","type":"post","link":"https:\/\/afaghhosting.net\/blog\/cve-2026-64206-bluetooth-l2cap-cancel-pending_rx_work-before-taking-conn-lock\/","title":{"rendered":"CVE-2026-64206 &#8211; Bluetooth: L2CAP: cancel pending_rx_work before taking conn-&gt;lock"},"content":{"rendered":"<p>CVE ID :CVE-2026-64206<\/p>\n<p>  Published : July 20, 2026, 5:18 p.m. | 25\u00a0minutes ago<\/p>\n<p>  Description :In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>Bluetooth: L2CAP: cancel pending_rx_work before taking conn-&gt;lock<\/p>\n<p>l2cap_conn_del() takes conn-&gt;lock and then calls cancel_work_sync() for<br \/>\npending_rx_work.  process_pending_rx() takes the same mutex, so teardown<br \/>\ncan deadlock against the worker it is flushing.<\/p>\n<p>This issue was found by our static analysis tool and then manually<br \/>\nreviewed against the current tree.<\/p>\n<p>The grounded PoC kept the l2cap_conn_ready() -&gt; queue_work(&#8230;,<br \/>\n&amp;conn-&gt;pending_rx_work) submit path, the l2cap_conn_del() -&gt;<br \/>\ncancel_work_sync(&amp;conn-&gt;pending_rx_work) teardown path, and the<br \/>\nprocess_pending_rx() -&gt; mutex_lock(&amp;conn-&gt;lock) worker edge.  Lockdep<\/p>\n<p>  WARNING: possible circular locking dependency detected<br \/>\n  process_pending_rx+0x21\/0x2a [vuln_msv]\n  l2cap_conn_del.constprop.0+0x3f\/0x4e [vuln_msv]\n  *** DEADLOCK ***<\/p>\n<p>Cancel pending_rx_work before taking conn-&gt;lock, matching the existing<br \/>\nlock-before-drain ordering used for the two delayed works in the same<br \/>\nteardown path.  The pending_rx queue is still purged after the work has<br \/>\nbeen cancelled and conn-&gt;lock has been acquired.<\/p>\n<p>  Severity: 0.0 | NA<\/p>\n<p>  Visit the link for more details, such as CVSS details, affected products, timeline, and more&#8230;\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"<p>CVE ID :CVE-2026-64206 Published : July 20, 2026, 5:18 p.m. | 25\u00a0minutes ago Description :In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: cancel pending_rx_work before taking conn-&gt;lock l2cap_conn_del() takes conn-&gt;lock and then calls cancel_work_sync() for pending_rx_work. process_pending_rx() takes the same mutex, so teardown can deadlock against the worker it is flushing. &hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-82296","post","type-post","status-publish","format-standard","hentry","category-vulnerability"],"_links":{"self":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/82296","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/comments?post=82296"}],"version-history":[{"count":0,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/82296\/revisions"}],"wp:attachment":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/media?parent=82296"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/categories?post=82296"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/tags?post=82296"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}