Service interruption via L2CAP response-counter wraparound
Published Oct 21, 2024 · Updated May 11, 2026
Integer overflow in Linux Bluetooth L2CAP allows local users to interrupt system availability through repeated configuration requests. In l2cap_config_req, every L2CAP_CONF_REQ response increments the eight-bit chan->num_conf_rsp counter without a ceiling, so sustained requests wrap it after 255. Low-privileged local access to the Bluetooth configuration channel is required; published assessments report availability impact only, with no confidentiality or integrity effect.
Summary
What happened
Integer overflow in Linux Bluetooth L2CAP allows local users to interrupt system availability through repeated configuration requests. In l2cap_config_req, every L2CAP_CONF_REQ response increments the eight-bit chan->num_conf_rsp counter without a ceiling, so sustained requests wrap it after 255. Low-privileged local access to the Bluetooth configuration channel is required; published assessments report availability impact only, with no confidentiality or integrity effect.
The record
- CVE
- CVE-2022-48947
- Published
- Oct 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-190, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=2.6.32
- Affected versionversion=f2fcfcd670257236ebf2088bbdf26f6a8ef459fe <19a78143961a197de8502f4f29c453b913dc3c29
- Affected versionversion=f2fcfcd670257236ebf2088bbdf26f6a8ef459fe <49d5867819ab7c744852b45509e8469839c07e0e
- Affected versionversion=f2fcfcd670257236ebf2088bbdf26f6a8ef459fe <5550bbf709c323194881737fd290c4bada9e6ead
- Affected versionversion=f2fcfcd670257236ebf2088bbdf26f6a8ef459fe <95f1847a361c7b4bf7d74c06ecb6968455082c1a
- Affected versionversion=f2fcfcd670257236ebf2088bbdf26f6a8ef459fe <9fdc79b571434af7bc742da40a3405f038b637a7
- Affected versionversion=f2fcfcd670257236ebf2088bbdf26f6a8ef459fe <ad528fde0702903208d0a79d88d5a42ae3fc235b
- Affected versionversion=f2fcfcd670257236ebf2088bbdf26f6a8ef459fe <bcd70260ef56e0aee8a4fc6cd214a419900b0765
- Affected versionversion=f2fcfcd670257236ebf2088bbdf26f6a8ef459fe <f3fe6817156a2ad4b06f01afab04638a34d7c9a6
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