# CVE-2022-49823: ata: libata-transport: fix error handling in ata_tdev_add()

Status: published. Published: 2025-05-01. Updated: 2026-11-05.

In the Linux kernel, the following vulnerability has been resolved:

ata: libata-transport: fix error handling in ata_tdev_add()

In ata_tdev_add(), the return value of transport_add_device() is
not checked. As a result, it causes null-ptr-deref while removing
the module, because transport_remove_device() is called to remove
the device that was not added.

Unable to handle kernel NULL pointer dereference at virtual address 00000000000000d0
CPU: 13 PID: 13603 Comm: rmmod Kdump: loaded Tainted: G        W          6.1.0-rc3+ #36
pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : device_del+0x48/0x3a0
lr : device_del+0x44/0x3a0
Call trace:
 device_del+0x48/0x3a0
 attribute_container_class_device_del+0x28/0x40
 transport_remove_classdev+0x60/0x7c
 attribute_container_device_trigger+0x118/0x120
 transport_remove_device+0x20/0x30
 ata_tdev_delete+0x24/0x50 [libata]
 ata_tlink_delete+0x40/0xa0 [libata]
 ata_tport_delete+0x2c/0x60 [libata]
 ata_port_detach+0x148/0x1b0 [libata]
 ata_pci_remove_one+0x50/0x80 [libata]
 ahci_remove_one+0x4c/0x8c [ahci]

Fix this by checking and handling return value of transport_add_device()
in ata_tdev_add(). In the error path, device_del() is called to delete
the device which was added earlier in this function, and ata_tdev_free()
is called to free ata_dev.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ d9027470b88631d0956ac37cdadfdeb9cdcf2c99; < ef2ac07ab83163b9a53f45da20e14302591ad9cc (affected, git); ≥ d9027470b88631d0956ac37cdadfdeb9cdcf2c99; < f23058dc2398db1d8faca9a2b1ce30b85cdd8b22 (affected, git); ≥ d9027470b88631d0956ac37cdadfdeb9cdcf2c99; < f54331962883f4fc4bf5e487e6e7cf07c4567fef (affected, git); ≥ d9027470b88631d0956ac37cdadfdeb9cdcf2c99; < 1ff36351309e3eadcff297480baf4785e726de9b (affected, git). Source: CNA: Linux
- Linux / Linux: 2.6.37 (affected); ≥ 0; < 2.6.37 (unaffected, semver); ≥ 5.10.156; ≤ 5.10.* (unaffected, semver); ≥ 5.15.80; ≤ 5.15.* (unaffected, semver); ≥ 6.0.10; ≤ 6.0.* (unaffected, semver); ≥ 6.1; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.21% as of 2026-11-05; percentile 12.00%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/ef2ac07ab83163b9a53f45da20e14302591ad9cc (CNA: Linux)

- https://git.kernel.org/stable/c/f23058dc2398db1d8faca9a2b1ce30b85cdd8b22 (CNA: Linux)

- https://git.kernel.org/stable/c/f54331962883f4fc4bf5e487e6e7cf07c4567fef (CNA: Linux)

- https://git.kernel.org/stable/c/1ff36351309e3eadcff297480baf4785e726de9b (CNA: Linux)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2022-49823; retrieved 2026-11-05; source updated 2026-11-05

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2022-49823; retrieved 2026-11-05; source updated Not reported

Revision: 63f033da7d20ee10c4b052a057a5b05057772534381b524e654eb732368c3633

Canonical: https://y2.dev/cve/CVE-2022-49823

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.