# Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout

CVE record · `CVE-2022-49474`

- **Identifiers:** `CVE-2022-49474`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-416](https://cwe.mitre.org/data/definitions/416.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 26 Feb 2025
- **Updated:** 5 Aug 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 02:13 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: `22c66af08230a7030bdb88accffaec3424695631 to before 9de3dc09e56f8deacd2bdbf4cecb71e11a312405` (git)
  - affected: `0115a66ebb44bd9127ccb58cf43ed23c795eb1f0 to before 7d61dbd7311ab978d8ddac1749a758de4de00374` (git)
  - affected: `bc4b08383046f3282b6fa58cfcef05bd13e52b93 to before 390d82733a953c1fabf3de9c9618091a7a9c90a6` (git)
  - affected: `5ccb04c6e1fb7b97fa2e1785b67c3a1cb3527ef7 to before 6f55fac0af3531cf60d11369454c41f5fc81ab3f` (git)
  - affected: `059c2c09f4b7f97711d0d8eaa0b9877f5e7d0a75 to before 36c644c63bfcaee2d3a426f45e89a9cd09799318` (git)
  - affected: `e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 to before 65d347cb39e2e6bd0c2a745ad7c928998ebb0162` (git)
  - affected: `e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 to before 537f619dea4e3fa8ed1f8f938abffe3615794bcc` (git)
  - affected: `e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 to before 99df16007f4bbf9abfc3478cb17d10f0d7f8906e` (git)
  - affected: `e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 to before 7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2` (git)
  - affected: `98ae477ed1540d3acbbf44d88ee237ad64275158` (git)
  - affected: `f0c389e23e2475e5837716a629c81b7a9d90cc94` (git)
  - affected: `0b9da4bde0d59c61b3675bdd80a05a726beb875a` (git)
  - and 8 more
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.15`
  - unaffected: `before 5.15` (semver)
  - unaffected: `4.9.318 to 4.9.*, inclusive` (semver)
  - unaffected: `4.14.283 to 4.14.*, inclusive` (semver)
  - unaffected: `4.19.247 to 4.19.*, inclusive` (semver)
  - unaffected: `5.4.198 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.121 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.46 to 5.15.*, inclusive` (semver)
  - unaffected: `5.17.14 to 5.17.*, inclusive` (semver)
  - unaffected: `5.18.3 to 5.18.*, inclusive` (semver)
  - unaffected: `5.19 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.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux) (used for this record)
- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0028, the 21st percentile, on 20 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 26 Feb 2025. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/9de3dc09e56f8deacd2bdbf4cecb71e11a312405>
- <https://git.kernel.org/stable/c/7d61dbd7311ab978d8ddac1749a758de4de00374>
- <https://git.kernel.org/stable/c/390d82733a953c1fabf3de9c9618091a7a9c90a6>
- <https://git.kernel.org/stable/c/6f55fac0af3531cf60d11369454c41f5fc81ab3f>
- <https://git.kernel.org/stable/c/36c644c63bfcaee2d3a426f45e89a9cd09799318>
- <https://git.kernel.org/stable/c/65d347cb39e2e6bd0c2a745ad7c928998ebb0162>
- <https://git.kernel.org/stable/c/537f619dea4e3fa8ed1f8f938abffe3615794bcc>
- <https://git.kernel.org/stable/c/99df16007f4bbf9abfc3478cb17d10f0d7f8906e>
- <https://git.kernel.org/stable/c/7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2>

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

---

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