LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48947: Bluetooth: L2CAP: Fix u8 overflow

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix u8 overflow By keep sending L2CAP_CONF_REQ packets, chan->num_conf_rsp increases multiple times and eventually it will wrap around the maximum number (i.e., 255). This patch prevents this by adding a boundary check with L2CAP_MAX_CONF_RSP Btmon log: Bluetooth monitor ver 5.64 = Note: Linux version 6.1.0-rc2 (x86_64) 0.264594 = Note: Bluetooth subsystem version 2.22 0.264636 @ MGMT Open: btmon (privileged) version 1.22 {0x0001} 0.272191 = New Index: 00:00:00:00:00:00 (Primary,Virtual,hci0) [hci0] 13.877604 @ RAW Open: 9496 (privileged) version 2.22 {0x0002} 13.890741 = Open Index: 00:00:00:00:00:00 [hci0] 13.900426 (...) > ACL Data RX: Handle 200 flags 0x00 dlen 1033 #32 [hci0] 14.273106 invalid packet size (12 != 1033) 08 00 01 00 02 01 04 00 01 10 ff ff ............ > ACL Data RX: Handle 200 flags 0x00 dlen 1547 #33 [hci0] 14.273561 invalid packet size (14 != 1547) 0a 00 01 00 04 01 06 00 40 00 00 00 00 00 ........@..... > ACL Data RX: Handle 200 flags 0x00 dlen 2061 #34 [hci0] 14.274390 invalid packet size (16 != 2061) 0c 00 01 00 04 01 08 00 40 00 00 00 00 00 00 04 ........@....... > ACL Data RX: Handle 200 flags 0x00 dlen 2061 #35 [hci0] 14.274932 invalid packet size (16 != 2061) 0c 00 01 00 04 01 08 00 40 00 00 00 07 00 03 00 ........@....... = bluetoothd: Bluetooth daemon 5.43 14.401828 > ACL Data RX: Handle 200 flags 0x00 dlen 1033 #36 [hci0] 14.275753 invalid packet size (12 != 1033) 08 00 01 00 04 01 04 00 40 00 00 00 ........@...

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-48947 is a Linux kernel Bluetooth issue in L2CAP configuration handling. Repeated L2CAP configuration requests can make an internal 8-bit counter wrap past 255. The public record does not state a proven business impact, CVSS score, or active exploitation, so urgency depends on Bluetooth exposure and vendor kernel status.

Executive priority

Treat as exposure-driven. It is a kernel Bluetooth flaw with an upstream fix, but public severity and exploitation evidence are incomplete. Prioritize patch validation on Bluetooth-capable Linux assets and defer emergency handling unless vendor advisories indicate higher impact.

Technical view

The issue is in Linux kernel Bluetooth L2CAP. Repeated L2CAP_CONF_REQ packets can increment chan->num_conf_rsp until the u8 value wraps. The upstream fix adds a boundary check using L2CAP_MAX_CONF_RSP. Affected Linux kernel entries are listed, with multiple stable commit references available.

Likely exposure

Exposure is most relevant to Linux systems with Bluetooth enabled or otherwise reachable at the L2CAP layer. Servers without Bluetooth hardware or disabled Bluetooth are less likely to be exposed, but the source bundle does not define exact prerequisites, attack range, or impact.

Exploitation context

The bundle marks this CVE as not in KEV and provides no cited evidence of active exploitation. It includes a btmon log showing malformed or repeated Bluetooth traffic, but does not provide exploit status, exploit maturity, or confirmed real-world abuse.

Researcher notes

The useful anchor is the counter wrap in chan->num_conf_rsp and the L2CAP_MAX_CONF_RSP boundary check. The source bundle does not state consequence, privilege requirements, range, or reliability. Avoid assuming denial of service, code execution, or local versus adjacent attack requirements without vendor evidence.

Mitigation direction

  • Update affected Linux kernels to builds containing the referenced stable fixes.
  • Check distribution vendor advisories for the correct fixed package version.
  • Prioritize systems where Bluetooth is enabled, paired, or operationally required.
  • Where Bluetooth is unnecessary, follow vendor guidance to reduce Bluetooth exposure.

Validation and detection

  • Inventory Linux kernel versions across endpoints, appliances, and embedded systems.
  • Identify systems with Bluetooth hardware, drivers, or services enabled.
  • Confirm kernel changelogs include one of the referenced stable fix commits.
  • Track vendor package status rather than relying only on upstream version numbers.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-48947 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf2fcfcd670257236ebf2088bbdf26f6a8ef459fe, f2fcfcd670257236ebf2088bbdf26f6a8ef459fe, f2fcfcd670257236ebf2088bbdf26f6a8ef459fe, f2fcfcd670257236ebf2088bbdf26f6a8ef459fe, f2fcfcd670257236ebf2088bbdf26f6a8ef459fe, f2fcfcd670257236ebf2088bbdf26f6a8ef459fe, f2fcfcd670257236ebf2088bbdf26f6a8ef459fe, f2fcfcd670257236ebf2088bbdf26f6a8ef459feunaffected
LinuxLinux2.6.32, 0, 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.161, 5.15.85, 6.0.15, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.