# Bluetooth: L2CAP: Fix div-by-zero in l2cap_le_flowctl_init()

CVE record · `CVE-2024-36968`

- **Identifiers:** `CVE-2024-36968`
- **State:** Confirmed
- **Severity:** CVSS 7.6 High
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 8 Jun 2024
- **Updated:** 30 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 8 Jun 2024, 12:53 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: `6ed58ec520ad2b2fe3f955c8a5fd0eecafccebdf to before e34634fad3792d4d35850cae72b7b7813466844f` (git)
  - affected: `6ed58ec520ad2b2fe3f955c8a5fd0eecafccebdf to before ad3f7986c5a0f82b8b66a0afe1cc1f5421e1d674` (git)
  - affected: `6ed58ec520ad2b2fe3f955c8a5fd0eecafccebdf to before dfece2b4e3759759b2bdfac2cd6d0ee9fbf055f3` (git)
  - affected: `6ed58ec520ad2b2fe3f955c8a5fd0eecafccebdf to before d2b2f7d3936dc5990549bc36ab7ac7ac37f22c30` (git)
  - affected: `6ed58ec520ad2b2fe3f955c8a5fd0eecafccebdf to before 4d3dbaa252257d20611c3647290e6171f1bbd6c8` (git)
  - affected: `6ed58ec520ad2b2fe3f955c8a5fd0eecafccebdf to before a5b862c6a221459d54e494e88965b48dcfa6cc44` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `2.6.39`
  - unaffected: `before 2.6.39` (semver)
  - unaffected: `6.1.191 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.32 to 6.6.*, inclusive` (semver)
  - unaffected: `6.8.11 to 6.8.*, inclusive` (semver)
  - unaffected: `6.9.2 to 6.9.*, inclusive` (semver)
  - unaffected: `6.9.4 to 6.9.*, inclusive` (semver)
  - unaffected: `6.10 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.

> Linux kernel versions from commit 6ed58ec520ad2b2fe3f955c8a5fd0eecafccebdf up to the fixed commits listed, and 2.6.39 with the same bug, are affected by a divide-by-zero in the Bluetooth L2CAP code (l2cap_le_flowctl_init). The flaw occurs when the controller reports an invalid LE MTU, and a nearby device sending a crafted L2CAP connection request over Bluetooth could trigger a kernel crash. Upgrade to a fixed kernel release: 6.1.191 or later in the 6.1 series, 6.6.32 or later in 6.6, 6.8.11 or later in 6.8, or 6.9.2 or later in 6.9.

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

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

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

## Timeline

This record came from the full history of the CVE Program, published 8 Jun 2024. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/e34634fad3792d4d35850cae72b7b7813466844f>
- <https://git.kernel.org/stable/c/ad3f7986c5a0f82b8b66a0afe1cc1f5421e1d674>
- <https://git.kernel.org/stable/c/dfece2b4e3759759b2bdfac2cd6d0ee9fbf055f3>
- <https://git.kernel.org/stable/c/d2b2f7d3936dc5990549bc36ab7ac7ac37f22c30>
- <https://git.kernel.org/stable/c/4d3dbaa252257d20611c3647290e6171f1bbd6c8>
- <https://git.kernel.org/stable/c/a5b862c6a221459d54e494e88965b48dcfa6cc44>

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

---

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