Loading vulnerability…
CVE-2023-53297 is an improper locking defect in the Linux kernel Bluetooth L2CAP subsystem. In l2cap_disconnect_rsp(), conn->chan_lock is not acquired before calling l2cap_get_chan_by_scid(). When the channel lookup returns NULL, the affected error path performs an unmatched unlock operation, triggering a bad unlock-balance condition.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel Bluetooth L2CAP locking error in l2cap_disconnect_rsp().
Linux kernel Bluetooth L2CAP flaw involving incorrect lock/unlock balance in l2cap_disconnect_rsp().
Linux kernel Bluetooth L2CAP locking-balance flaw in l2cap_disconnect_rsp.
Linux kernel Bluetooth L2CAP flaw involving an incorrect lock/unlock balance in l2cap_disconnect_rsp.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.