Answer in brief
CVE-2026-43134 records a Unknown severity vulnerability in Bluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ. 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-43134 records a Unknown severity vulnerability in Bluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ. 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 | >=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <335071c0c3637064ec250481f589075db44fe4e6 || >=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <fa6ad76fa8623c0a50d529cd5726fa5d819a3be4 || >=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <9118601ff90b79e8df3c0c98f48ae00c1b02ecef || >=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <481ea39b342c347b6ac029f3d418486280be4e45 || >=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <ec91078e132179b04e0c3906b599816c056ceaad || >=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <96581749c7c14fbec32c35728520867929600041 || >=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <8dd43f9a9323f9c01bc8246da8d81a4c783c9e97 || >=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <138d7eca445ef37a0333425d269ee59900ca1104 | 335071c0c3637064ec250481f589075db44fe4e6, fa6ad76fa8623c0a50d529cd5726fa5d819a3be4, 9118601ff90b79e8df3c0c98f48ae00c1b02ecef, 481ea39b342c347b6ac029f3d418486280be4e45, ec91078e132179b04e0c3906b599816c056ceaad, 96581749c7c14fbec32c35728520867929600041, 8dd43f9a9323f9c01bc8246da8d81a4c783c9e97, 138d7eca445ef37a0333425d269ee59900ca1104 |
| Linux/Linuxgeneric | 3.14 | Not reported |
Published upstream
May 6, 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: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ This adds a check for encryption key size upon receiving L2CAP_LE_CONN_REQ which is required by L2CAP/LE/CFC/BV-15-C which expects L2CAP_CR_LE_BAD_KEY_SIZE.
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 | >=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <335071c0c3637064ec250481f589075db44fe4e6 || >=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <fa6ad76fa8623c0a50d529cd5726fa5d819a3be4 || >=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <9118601ff90b79e8df3c0c98f48ae00c1b02ecef || >=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <481ea39b342c347b6ac029f3d418486280be4e45 || >=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <ec91078e132179b04e0c3906b599816c056ceaad || >=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <96581749c7c14fbec32c35728520867929600041 || >=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <8dd43f9a9323f9c01bc8246da8d81a4c783c9e97 || >=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <138d7eca445ef37a0333425d269ee59900ca1104 | 335071c0c3637064ec250481f589075db44fe4e6, fa6ad76fa8623c0a50d529cd5726fa5d819a3be4, 9118601ff90b79e8df3c0c98f48ae00c1b02ecef, 481ea39b342c347b6ac029f3d418486280be4e45, ec91078e132179b04e0c3906b599816c056ceaad, 96581749c7c14fbec32c35728520867929600041, 8dd43f9a9323f9c01bc8246da8d81a4c783c9e97, 138d7eca445ef37a0333425d269ee59900ca1104 |
| Linux/Linuxgeneric | 3.14 | Not reported |
Published upstream
May 6, 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: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ This adds a check for encryption key size upon receiving L2CAP_LE_CONN_REQ which is required by L2CAP/LE/CFC/BV-15-C which expects L2CAP_CR_LE_BAD_KEY_SIZE.
Quoted source text, attributed separately from HOL analysis.