Security policy bypass via unchecked encryption key
Published Sep 24, 2025 · Updated Sep 24, 2025
Inadequate encryption-strength validation in affected Linux kernel versions allows physically proximate attackers to establish an L2CAP connection. The l2cap_connect function checks ACL link mode but fails to call l2cap_check_enc_key_size before accepting a non-SDP connection. The peer must be within Bluetooth range and negotiate Security Mode 4 Level 4 with a 1-to-15-byte key; the observed consequence is acceptance of a channel that should receive a security-block refusal.
Summary
What happened
Inadequate encryption-strength validation in affected Linux kernel versions allows physically proximate attackers to establish an L2CAP connection. The l2cap_connect function checks ACL link mode but fails to call l2cap_check_enc_key_size before accepting a non-SDP connection. The peer must be within Bluetooth range and negotiate Security Mode 4 Level 4 with a 1-to-15-byte key; the observed consequence is acceptance of a channel that should receive a security-block refusal.
The record
- CVE
- CVE-2025-39889
- Published
- Sep 24, 2025
- Updated
- Sep 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-326
- Attack vector
- adjacent
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 24, 2025CVE publishedPublication date reported by the CVE source.
- Sep 24, 2025Record 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=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <24b2cdfc16e9bd6ab3d03b8e01c590755bd3141f
- Affected versionversion=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <522e9ed157e3c21b4dd623c79967f72c21e45b78
- Affected versionversion=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <9e3114958d87ea88383cbbf38c89e04b8ea1bce5
- Affected versionversion=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <c6d527bbd3d3896375079f5dbc8b7f96734a3ba5
- Affected versionversion=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <d49798ecd26e0ee7995a7fc1e90ca5cd9b4402d6
- Affected versionversion=288c06973daae4637f25a0d1bdaf65fdbf8455f9 <d4ca2fd218caafbf50e3343ba1260c6a23b5676a
- Affected versionversion=5.11
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
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