L2CAP response-limit bypass via counter wraparound
Published Nov 27, 2022 · Updated Apr 29, 2025
Integer wraparound in Linux kernel through 6.0.10 allows attackers to bypass the L2CAP configuration-response limit with repeated requests. The l2cap_config_req function increments the eight-bit chan->num_conf_rsp counter without stopping at L2CAP_MAX_CONF_RSP, allowing repeated L2CAP_CONF_REQ packets to wrap it to zero. Exploitation requires access to a Bluetooth L2CAP connection; public records establish the limit bypass but document no resulting crash, code execution, or data access.
Summary
What happened
Integer wraparound in Linux kernel through 6.0.10 allows attackers to bypass the L2CAP configuration-response limit with repeated requests. The l2cap_config_req function increments the eight-bit chan->num_conf_rsp counter without stopping at L2CAP_MAX_CONF_RSP, allowing repeated L2CAP_CONF_REQ packets to wrap it to zero. Exploitation requires access to a Bluetooth L2CAP connection; public records establish the limit bypass but document no resulting crash, code execution, or data access.
The record
- CVE
- CVE-2022-45934
- Published
- Nov 27, 2022
- Updated
- Apr 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 27, 2022CVE publishedPublication date reported by the CVE source.
- Apr 29, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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