Bug 2507111 (CVE-2026-64408)

Summary: CVE-2026-64408 kernel: Bluetooth: bnep: pin L2CAP connection during netdev registration
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: rhel-process-autobot, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the Bluetooth Network Encapsulation Protocol (BNEP) module of the Linux kernel. The `bnep_add_connection()` function reads the Logical Link Control and Adaptation Protocol (L2CAP) connection without properly holding a channel lock. This can allow a local attacker to trigger a use-after-free vulnerability during network device registration, potentially leading to a system crash and denial of service.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-07-25 10:05:34 UTC 
In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: bnep: pin L2CAP connection during netdev registration

bnep_add_connection() reads the L2CAP connection without holding the
channel lock, then passes its HCI device to register_netdev(). Controller
teardown can clear and release that connection concurrently, leaving the
network device registration path to dereference a freed parent device.

Take a reference to the L2CAP connection while holding the channel lock.
Retain it until register_netdev() has taken the parent device reference.
Comment 1 TEJ RATHI 2026-07-30 05:09:03 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026072531-CVE-2026-64408-3013@gregkh/T