PT-2026-61647 · Linux · Linux
CVE-2026-64206
·
Published
2026-07-20
·
Updated
2026-07-20
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: cancel pending rx work before taking conn->lock
l2cap conn del() takes conn->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.
This issue was found by our static analysis tool and then manually
reviewed against the current tree.
The grounded PoC kept the l2cap conn ready() -> queue work(...,
&conn->pending rx work) submit path, the l2cap conn del() ->
cancel work sync(&conn->pending rx work) teardown path, and the
process pending rx() -> mutex lock(&conn->lock) worker edge. Lockdep
WARNING: possible circular locking dependency detected
process pending rx+0x21/0x2a [vuln msv]
l2cap conn del.constprop.0+0x3f/0x4e [vuln msv]
*** DEADLOCK ***
Cancel pending rx work before taking conn->lock, matching the existing
lock-before-drain ordering used for the two delayed works in the same
teardown path. The pending rx queue is still purged after the work has
been cancelled and conn->lock has been acquired.
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux