Answer in brief
CVE-2025-39889 records a Unknown severity vulnerability in Bluetooth: l2cap: Check encryption key size on incoming connection. 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-2025-39889 records a Unknown severity vulnerability in Bluetooth: l2cap: Check encryption key size on incoming connection. 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 | >=4f911a538e089cce808a15dc3277250f4f8daef9 <ed503d340a501e414114ddc614a3aae4f6e9eae2 || >=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <24b2cdfc16e9bd6ab3d03b8e01c590755bd3141f || >=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <c6d527bbd3d3896375079f5dbc8b7f96734a3ba5 || >=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <9e3114958d87ea88383cbbf38c89e04b8ea1bce5 || >=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <d49798ecd26e0ee7995a7fc1e90ca5cd9b4402d6 || >=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <d4ca2fd218caafbf50e3343ba1260c6a23b5676a || >=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <522e9ed157e3c21b4dd623c79967f72c21e45b78 | ed503d340a501e414114ddc614a3aae4f6e9eae2, 24b2cdfc16e9bd6ab3d03b8e01c590755bd3141f, c6d527bbd3d3896375079f5dbc8b7f96734a3ba5, 9e3114958d87ea88383cbbf38c89e04b8ea1bce5, d49798ecd26e0ee7995a7fc1e90ca5cd9b4402d6, d4ca2fd218caafbf50e3343ba1260c6a23b5676a, 522e9ed157e3c21b4dd623c79967f72c21e45b78 |
| Linux/Linuxgeneric | 5.11 | Not reported |
Published upstream
Sep 24, 2025
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: l2cap: Check encryption key size on incoming connection This is required for passing GAP/SEC/SEM/BI-04-C PTS test case: Security Mode 4 Level 4, Responder - Invalid Encryption Key Size - 128 bit This tests the security key with size from 1 to 15 bytes while the Security Mode 4 Level 4 requests 16 bytes key size. Currently PTS fails with the following logs: - expected:Connection Response: Code: [3 (0x03)] Code Identifier: (lt)WildCard: Exists(gt) Length: [8 (0x0008)] Destination CID: (lt)WildCard: Exists(gt) Source CID: [64 (0x0040)] Result: [3 (0x0003)] Connection refused - Security block Status: (lt)WildCard: Exists(gt), but received:Connection Response: Code: [3 (0x03)] Code Identifier: [1 (0x01)] Length: [8 (0x0008)] Destination CID: [64 (0x0040)] Source CID: [64 (0x0040)] Result: [0 (0x0000)] Connection Successful Status: [0 (0x0000)] No further information available And HCI logs: < HCI Command: Read Encrypti.. (0x05|0x0008) plen 2 Handle: 14 Address: 00:1B:DC:F2:24:10 (Vencer Co., Ltd.) > HCI Event: Command Complete (0x0e) plen 7 Read Encryption Key Size (0x05|0x0008) ncmd 1 Status: Success (0x00) Handle: 14 Address: 00:1B:DC:F2:24:10 (Vencer Co., Ltd.) Key size: 7 > ACL Data RX: Handle 14 flags 0x02 dlen 12 L2CAP: Connection Request (0x02) ident 1 len 4 PSM: 4097 (0x1001) Source CID: 64 < ACL Data TX: Handle 14 flags 0x00 dlen 16 L2CAP: Connection Response (0x03) ident 1 len 8 Destination CID: 64 Source CID: 64 Result: Connection successful (0x0000) Status: No further information available (0x0000)
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 | >=4f911a538e089cce808a15dc3277250f4f8daef9 <ed503d340a501e414114ddc614a3aae4f6e9eae2 || >=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <24b2cdfc16e9bd6ab3d03b8e01c590755bd3141f || >=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <c6d527bbd3d3896375079f5dbc8b7f96734a3ba5 || >=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <9e3114958d87ea88383cbbf38c89e04b8ea1bce5 || >=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <d49798ecd26e0ee7995a7fc1e90ca5cd9b4402d6 || >=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <d4ca2fd218caafbf50e3343ba1260c6a23b5676a || >=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <522e9ed157e3c21b4dd623c79967f72c21e45b78 | ed503d340a501e414114ddc614a3aae4f6e9eae2, 24b2cdfc16e9bd6ab3d03b8e01c590755bd3141f, c6d527bbd3d3896375079f5dbc8b7f96734a3ba5, 9e3114958d87ea88383cbbf38c89e04b8ea1bce5, d49798ecd26e0ee7995a7fc1e90ca5cd9b4402d6, d4ca2fd218caafbf50e3343ba1260c6a23b5676a, 522e9ed157e3c21b4dd623c79967f72c21e45b78 |
| Linux/Linuxgeneric | 5.11 | Not reported |
Published upstream
Sep 24, 2025
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: l2cap: Check encryption key size on incoming connection This is required for passing GAP/SEC/SEM/BI-04-C PTS test case: Security Mode 4 Level 4, Responder - Invalid Encryption Key Size - 128 bit This tests the security key with size from 1 to 15 bytes while the Security Mode 4 Level 4 requests 16 bytes key size. Currently PTS fails with the following logs: - expected:Connection Response: Code: [3 (0x03)] Code Identifier: (lt)WildCard: Exists(gt) Length: [8 (0x0008)] Destination CID: (lt)WildCard: Exists(gt) Source CID: [64 (0x0040)] Result: [3 (0x0003)] Connection refused - Security block Status: (lt)WildCard: Exists(gt), but received:Connection Response: Code: [3 (0x03)] Code Identifier: [1 (0x01)] Length: [8 (0x0008)] Destination CID: [64 (0x0040)] Source CID: [64 (0x0040)] Result: [0 (0x0000)] Connection Successful Status: [0 (0x0000)] No further information available And HCI logs: < HCI Command: Read Encrypti.. (0x05|0x0008) plen 2 Handle: 14 Address: 00:1B:DC:F2:24:10 (Vencer Co., Ltd.) > HCI Event: Command Complete (0x0e) plen 7 Read Encryption Key Size (0x05|0x0008) ncmd 1 Status: Success (0x00) Handle: 14 Address: 00:1B:DC:F2:24:10 (Vencer Co., Ltd.) Key size: 7 > ACL Data RX: Handle 14 flags 0x02 dlen 12 L2CAP: Connection Request (0x02) ident 1 len 4 PSM: 4097 (0x1001) Source CID: 64 < ACL Data TX: Handle 14 flags 0x00 dlen 16 L2CAP: Connection Response (0x03) ident 1 len 8 Destination CID: 64 Source CID: 64 Result: Connection successful (0x0000) Status: No further information available (0x0000)
Quoted source text, attributed separately from HOL analysis.