Answer in brief
CVE-2026-64408 records a Unknown severity vulnerability in Bluetooth: bnep: pin L2CAP connection during netdev registration. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-64408 records a Unknown severity vulnerability in Bluetooth: bnep: pin L2CAP connection during netdev registration. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=65f53e9802dbfae0e5758a91793c3f5f8bece49b <390b5db3ff8745187f094c4e915663b7b1f98944 || >=65f53e9802dbfae0e5758a91793c3f5f8bece49b <46a88784c4c9b96954dd86f747ce93f65efa1302 || >=65f53e9802dbfae0e5758a91793c3f5f8bece49b <551ae773ec64045b4e72099132654887e0270bcc || >=65f53e9802dbfae0e5758a91793c3f5f8bece49b <ae215c5b6422d8eda443b861b124bd1be6969c31 || >=65f53e9802dbfae0e5758a91793c3f5f8bece49b <df22adc7eafc22e651561813c11dc51a796b12ee || >=65f53e9802dbfae0e5758a91793c3f5f8bece49b <a6b22dbd80926556290ad2243be25218d6956a19 || >=65f53e9802dbfae0e5758a91793c3f5f8bece49b <563a8573047182f550b1e1e030615755cd8c41da || >=65f53e9802dbfae0e5758a91793c3f5f8bece49b <bb067a99a0356196c0b89a95721985485ebce5a5 | 390b5db3ff8745187f094c4e915663b7b1f98944, 46a88784c4c9b96954dd86f747ce93f65efa1302, 551ae773ec64045b4e72099132654887e0270bcc, ae215c5b6422d8eda443b861b124bd1be6969c31, df22adc7eafc22e651561813c11dc51a796b12ee, a6b22dbd80926556290ad2243be25218d6956a19, 563a8573047182f550b1e1e030615755cd8c41da, bb067a99a0356196c0b89a95721985485ebce5a5 |
| Linux/Linuxgeneric | 3.13 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=65f53e9802dbfae0e5758a91793c3f5f8bece49b <390b5db3ff8745187f094c4e915663b7b1f98944 || >=65f53e9802dbfae0e5758a91793c3f5f8bece49b <46a88784c4c9b96954dd86f747ce93f65efa1302 || >=65f53e9802dbfae0e5758a91793c3f5f8bece49b <551ae773ec64045b4e72099132654887e0270bcc || >=65f53e9802dbfae0e5758a91793c3f5f8bece49b <ae215c5b6422d8eda443b861b124bd1be6969c31 || >=65f53e9802dbfae0e5758a91793c3f5f8bece49b <df22adc7eafc22e651561813c11dc51a796b12ee || >=65f53e9802dbfae0e5758a91793c3f5f8bece49b <a6b22dbd80926556290ad2243be25218d6956a19 || >=65f53e9802dbfae0e5758a91793c3f5f8bece49b <563a8573047182f550b1e1e030615755cd8c41da || >=65f53e9802dbfae0e5758a91793c3f5f8bece49b <bb067a99a0356196c0b89a95721985485ebce5a5 | 390b5db3ff8745187f094c4e915663b7b1f98944, 46a88784c4c9b96954dd86f747ce93f65efa1302, 551ae773ec64045b4e72099132654887e0270bcc, ae215c5b6422d8eda443b861b124bd1be6969c31, df22adc7eafc22e651561813c11dc51a796b12ee, a6b22dbd80926556290ad2243be25218d6956a19, 563a8573047182f550b1e1e030615755cd8c41da, bb067a99a0356196c0b89a95721985485ebce5a5 |
| Linux/Linuxgeneric | 3.13 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.