Description
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.
Published: 2026-05-05
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Linux kernel Bluetooth module contains a type confusion bug in the function that processes L2CAP ECRED reconfiguration responses. The code mistakenly interprets the incoming packet as a larger connection‑response structure, causing a size check to reject valid short packets and misread the result field from an incorrect offset. This leads to legitimate frames being dropped or incorrect data being stored, which can disrupt Bluetooth connectivity and potentially allow a malicious actor to induce packet loss or incorrect state handling. The weakness falls under CWE‑754: Use of Object of Incorrect Type; the issue does not provide for arbitrary code execution but can degrade service reliability.

Affected Systems

The vulnerability affects all Linux kernel builds that contain the Linux kernel Bluetooth L2CAP implementation before the applied patch. The Common Platform Enumeration entry identifies the entire Linux kernel family, and there is no finer‑grained version list in the data. Administrators should check that the kernel they run is at or beyond the commit that fixes the bug or verify that the patch is applied manually.

Risk and Exploitability

No CVSS score is provided, and the EPSS score is unavailable, but the vulnerability is known to exist in production kernels. The most likely attack vector is through the Bluetooth interface, where an attacker capable of transmitting crafted L2CAP_RECONF_RSP packets could induce packet rejection or incorrect handling. Attacker sophistication is moderate: a Bluetooth stack is required but no privileged code execution is needed. Because the bug affects only the handling of a specific control packet, the overall exploitation risk is considered moderate; however, the impact on service availability can be significant if an attacker floods the target with malformed frames.

Generated by OpenCVE AI on May 5, 2026 at 17:24 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that contains the l2cap_ecred_reconf_rsp type‑confusion fix, either by installing the latest kernel release or applying the patch from the cited commits.
  • If an immediate kernel update cannot be performed, block or filter incoming L2CAP_ECRED_RECONF_RSP packets on the Bluetooth interface using host‑based firewall rules or disable the ECRED feature in the Bluetooth daemon to prevent the processing of the affected packet type.
  • Monitor Bluetooth logs for repeated EPROTO errors or unusual packet drops that may indicate attempts to trigger the bug, and audit connected devices for any evidence of crafted packet transmission.

Generated by OpenCVE AI on May 5, 2026 at 17:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 05 May 2026 17:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-754

Tue, 05 May 2026 16:15:00 +0000

Type Values Removed Values Added
Description 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.
Title Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-05-05T15:17:27.830Z

Reserved: 2026-05-01T14:12:55.981Z

Link: CVE-2026-43062

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-05-05T16:16:15.340

Modified: 2026-05-05T16:16:15.340

Link: CVE-2026-43062

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-05T17:45:05Z

Weaknesses