# Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp()

CVE record · `CVE-2026-43062`

- **Identifiers:** `CVE-2026-43062`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-843](https://cwe.mitre.org/data/definitions/843.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 5 May 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 5 May 2026, 15:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `15f02b91056253e8cdc592888f431da0731337b8 to before 21d3ba696918d6373233aac0b9d51fcabdedddc0` (git)
  - affected: `15f02b91056253e8cdc592888f431da0731337b8 to before 3b94e62caa1dc1198d0d55d97bd710da1dee15d7` (git)
  - affected: `15f02b91056253e8cdc592888f431da0731337b8 to before 111f74547eee8cfedfb854284e80f35c8a491186` (git)
  - affected: `15f02b91056253e8cdc592888f431da0731337b8 to before dd3b221e21079ade8263fbb7176f3d55ad75d3b6` (git)
  - affected: `15f02b91056253e8cdc592888f431da0731337b8 to before d90150c72d2e6a8a3079e88755dafcfbe91c746d` (git)
  - affected: `15f02b91056253e8cdc592888f431da0731337b8 to before 5a1ea296f8589ce8f1e3141b2b123b34ad010e19` (git)
  - affected: `15f02b91056253e8cdc592888f431da0731337b8 to before f110b8f58b254bf997cec1bd60701b7798e9bb82` (git)
  - affected: `15f02b91056253e8cdc592888f431da0731337b8 to before 15145675690cab2de1056e7ed68e59cbd0452529` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.7`
  - unaffected: `before 5.7` (semver)
  - unaffected: `5.10.253 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.203 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.167 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.130 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.78 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.20 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.10 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 7.1 High, CVSS 3.1: `CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0022, the 12th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 5 May 2026, 16:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-43062)

## Sources

- [CVE List: CVE-2026-43062](https://www.cve.org/CVERecord?id=CVE-2026-43062)
- [NVD: CVE-2026-43062](https://nvd.nist.gov/vuln/detail/CVE-2026-43062)

### References from the CNA

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

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-43062>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-43062/>. Everything for agents: <https://agentprime.io/llms.txt>.
