# Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_state_change_cb()

CVE record · `CVE-2026-45834`

- **Identifiers:** `CVE-2026-45834`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 26 May 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 26 May 2026, 16:14 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: `89bc500e41fc5b48e0573e6b0d927fc97b8951dc to before 1b1c0da227bf63479bac9982fc8d12df9aaea0fb` (git)
  - affected: `89bc500e41fc5b48e0573e6b0d927fc97b8951dc to before 85426e97dc72f2088ba6d27e74cd58c3fbd43e31` (git)
  - affected: `89bc500e41fc5b48e0573e6b0d927fc97b8951dc to before 0c17c8832562b2aac288e89cefd0f46074f54bcb` (git)
  - affected: `89bc500e41fc5b48e0573e6b0d927fc97b8951dc to before 5105f3e6b2df619c635b5f6a49fac131a36c7952` (git)
  - affected: `89bc500e41fc5b48e0573e6b0d927fc97b8951dc to before c88c185ae0a1067823661b220aeea613df2c127b` (git)
  - affected: `89bc500e41fc5b48e0573e6b0d927fc97b8951dc to before 1810e42ff6716f320c7269d5850eca48b07b7427` (git)
  - affected: `89bc500e41fc5b48e0573e6b0d927fc97b8951dc to before a2dcf1a61d056aef15b63c6eae9441344d624389` (git)
  - affected: `89bc500e41fc5b48e0573e6b0d927fc97b8951dc to before 2ff1a41a912de8517b4482e946dd951b7d80edbf` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.1`
  - unaffected: `before 3.1` (semver)
  - unaffected: `5.10.258 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.209 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.175 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.140 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.88 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.30 to 6.18.*, inclusive` (semver)
  - unaffected: `7.0.7 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's Bluetooth L2CAP component has a null pointer dereference in l2cap_sock_state_change_cb(), affecting versions from 3.1 until fixed. The source gives few details on what an attacker needs or what they can do. Upgrade to 5.10.258, 5.15.209, 6.1.175, 6.6.140, or a later release in those series.

Written 17 Nov 2026.

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

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0013, the 2nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 26 May 2026, 16:14 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-45834)
- 26 May 2026, 17:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-45834)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/1b1c0da227bf63479bac9982fc8d12df9aaea0fb>
- <https://git.kernel.org/stable/c/85426e97dc72f2088ba6d27e74cd58c3fbd43e31>
- <https://git.kernel.org/stable/c/0c17c8832562b2aac288e89cefd0f46074f54bcb>
- <https://git.kernel.org/stable/c/5105f3e6b2df619c635b5f6a49fac131a36c7952>
- <https://git.kernel.org/stable/c/c88c185ae0a1067823661b220aeea613df2c127b>
- <https://git.kernel.org/stable/c/1810e42ff6716f320c7269d5850eca48b07b7427>
- <https://git.kernel.org/stable/c/a2dcf1a61d056aef15b63c6eae9441344d624389>
- <https://git.kernel.org/stable/c/2ff1a41a912de8517b4482e946dd951b7d80edbf>

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-45834>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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