Adjacent L2CAP security bypass via undersized keys
Published May 6, 2026 · Updated May 6, 2026
Improper validation in Linux kernel Bluetooth L2CAP allows adjacent attackers to establish channels with undersized encryption keys. The l2cap_le_connect_req function accepts L2CAP_LE_CONN_REQ messages without checking the channel's encryption key size. Bluetooth proximity and an LE link are required; accepted channels expose protected service data to reading or modification.
Summary
What happened
Improper validation in Linux kernel Bluetooth L2CAP allows adjacent attackers to establish channels with undersized encryption keys. The l2cap_le_connect_req function accepts L2CAP_LE_CONN_REQ messages without checking the channel's encryption key size. Bluetooth proximity and an LE link are required; accepted channels expose protected service data to reading or modification.
The record
- CVE
- CVE-2026-43134
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <138d7eca445ef37a0333425d269ee59900ca1104
- Affected versionversion=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <335071c0c3637064ec250481f589075db44fe4e6
- Affected versionversion=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <481ea39b342c347b6ac029f3d418486280be4e45
- Affected versionversion=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <8dd43f9a9323f9c01bc8246da8d81a4c783c9e97
- Affected versionversion=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <9118601ff90b79e8df3c0c98f48ae00c1b02ecef
- Affected versionversion=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <96581749c7c14fbec32c35728520867929600041
- Affected versionversion=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <ec91078e132179b04e0c3906b599816c056ceaad
- Affected versionversion=27e2d4c8d28be1d1b4ecfbffab572d7dbd35254d <fa6ad76fa8623c0a50d529cd5726fa5d819a3be4
- Affected versionversion=3.14
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo