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

> A type confusion in the Linux kernel Bluetooth L2CAP module causes valid packets to be rejected and incorrect data to be read, potentially leading to denial of service or information disclosure.

- **Severity:** High 7.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 May 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-43062, DEBIAN-CVE-2026-43062, GHSA-6mf2-xqwv-jhq3, ROOT-OS-DEBIAN-11-CVE-2026-43062, ROOT-OS-UBUNTU-2204-CVE-2026-43062, ROOT-OS-UBUNTU-2404-CVE-2026-43062, UBUNTU-CVE-2026-43062

## What is CVE-2026-43062?

CVE-2026-43062 is a high-severity vulnerability in Linux kernel, published on 5 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

## Which versions are affected by CVE-2026-43062?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-43062?

Apply the vendor's patch.

## Is CVE-2026-43062 being exploited?

There is no known exploitation of CVE-2026-43062 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-43062 and fix it if it is affected.

What it is: CVE-2026-43062 is a high-severity vulnerability in Linux kernel, published on 5 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-43062 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-43062/ (Markdown: https://insights.sbomify.com/CVE-2026-43062/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-43062
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-43062
- OSV: https://osv.dev/vulnerability/CVE-2026-43062

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-43062/
Summaries are generated and may contain mistakes; the official description above is the record.