LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43062: Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp()

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() l2cap_ecred_reconf_rsp() casts the incoming data to struct l2cap_ecred_conn_rsp (the ECRED *connection* response, 8 bytes with result at offset 6) instead of struct l2cap_ecred_reconf_rsp (2 bytes with result at offset 0). This causes two problems: - The sizeof(*rsp) length check requires 8 bytes instead of the correct 2, so valid L2CAP_ECRED_RECONF_RSP packets are rejected with -EPROTO. - rsp->result reads from offset 6 instead of offset 0, returning wrong data when the packet is large enough to pass the check. Fix by using the correct type. Also pass the already byte-swapped result variable to BT_DBG instead of the raw __le16 field.

HighCVSS 7.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux Bluetooth flaw mishandles a nearby device’s L2CAP reconfiguration response. Valid responses may be rejected or interpreted incorrectly, potentially affecting connection integrity and availability. It requires Bluetooth proximity; the supplied evidence does not establish remote internet exposure or code execution.

Executive priority

Prioritize Bluetooth-enabled Linux endpoints used in public, shared, industrial, or otherwise proximity-accessible locations. Patch through normal emergency security processes where exposure exists. Systems without Bluetooth capability, or with Bluetooth reliably disabled, warrant lower immediate priority after validation.

Technical view

l2cap_ecred_reconf_rsp() treats a two-byte ECRED reconfiguration response as an eight-byte connection response. It therefore applies the wrong length check and reads the result from offset 6 instead of offset 0. The correction uses the proper response structure and logs the byte-swapped result.

Likely exposure

Potentially exposed systems run an affected Linux kernel with Bluetooth and the relevant L2CAP ECRED functionality available to nearby devices. The supplied affected-version data is ambiguous, so kernel applicability should be confirmed against distribution guidance and the referenced stable commits.

Exploitation context

CVSS 3.1 rates this 7.1 with adjacent-network access, low complexity, no privileges, and no user interaction. KEV is false, and the supplied sources do not report active exploitation or a public exploit. Physical proximity and reachable Bluetooth functionality limit exposure.

Researcher notes

The issue is a protocol-structure type confusion producing an excessive length requirement and incorrect field offset. The supplied material supports malformed state processing, not memory corruption or code execution. Exact vulnerable release boundaries are unclear because the affected-version list mixes release and commit-like data; distribution-level confirmation is necessary.

Mitigation direction

  • Install a vendor-supported kernel containing the referenced correction.
  • Confirm distribution backport status rather than relying only on upstream version numbers.
  • Disable Bluetooth on systems where it is unnecessary until remediation is confirmed.
  • Restrict Bluetooth availability in sensitive or publicly accessible environments.

Validation and detection

  • Record each system’s kernel package, build, and distribution security status.
  • Verify whether Bluetooth is enabled and operational on affected assets.
  • Compare vendor kernel fixes with the referenced stable commits.
  • Test ECRED reconfiguration handling safely in an isolated compatibility environment.
Prepared
Confidence
medium
Sources
10

Public sources used

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-2026-43062 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
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L2.84.2Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2026-43062Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux15f02b91056253e8cdc592888f431da0731337b8, 15f02b91056253e8cdc592888f431da0731337b8, 15f02b91056253e8cdc592888f431da0731337b8, 15f02b91056253e8cdc592888f431da0731337b8, 15f02b91056253e8cdc592888f431da0731337b8, 15f02b91056253e8cdc592888f431da0731337b8, 15f02b91056253e8cdc592888f431da0731337b8, 15f02b91056253e8cdc592888f431da0731337b8unaffected
LinuxLinux5.7, 0, 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, 6.18.20, 6.19.10, 7.0affected
Weakness

CWE details

No CWE listed

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