# ata: libata-transport: fix error handling in ata_tport_add()

CVE record · `CVE-2022-49825`

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

Published by the CVE Program (CNA: Linux) at 1 May 2025, 14:09 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: `d9027470b88631d0956ac37cdadfdeb9cdcf2c99 to before b5362dc1634d8b8d5f30920f33ac11a3276b7ed9` (git)
  - affected: `d9027470b88631d0956ac37cdadfdeb9cdcf2c99 to before e7bb1b7a7bf26f6b7372b7b683daece4a42fda02` (git)
  - affected: `d9027470b88631d0956ac37cdadfdeb9cdcf2c99 to before 52d9bb0adae9359711a0c5271430afd3754069e7` (git)
  - affected: `d9027470b88631d0956ac37cdadfdeb9cdcf2c99 to before 3613dbe3909dcc637fe6be00e4dc43b4aa0470ee` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `2.6.37`
  - unaffected: `before 2.6.37` (semver)
  - unaffected: `5.10.156 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.80 to 5.15.*, inclusive` (semver)
  - unaffected: `6.0.10 to 6.0.*, inclusive` (semver)
  - unaffected: `6.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 libata transport code does not check the return value of transport_add_device() in ata_tport_add(). Removing the libata module afterwards can cause a NULL pointer dereference and a kernel crash. Upgrade to 5.10.156, 5.15.80, 6.0.10, 6.1, or a later release in the same series.

Written 16 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.0022, the 12th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 1 May 2025, 14:09 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-49825)
- 1 May 2025, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-49825)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/b5362dc1634d8b8d5f30920f33ac11a3276b7ed9>
- <https://git.kernel.org/stable/c/e7bb1b7a7bf26f6b7372b7b683daece4a42fda02>
- <https://git.kernel.org/stable/c/52d9bb0adae9359711a0c5271430afd3754069e7>
- <https://git.kernel.org/stable/c/3613dbe3909dcc637fe6be00e4dc43b4aa0470ee>

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

---

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