CVE-2022-49826

ata: libata-transport: fix double ata_host_put() in ata_tport_add()

HIGH
7.8
CVSS Score
Published: May 1, 2025 at 02:09 PM UTC
Updated: August 5, 2026 at 09:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ata: libata-transport: fix double ata_host_put() in ata_tport_add() In the error path in ata_tport_add(), when calling put_device(), ata_tport_release() is called, it will put the refcount of 'ap->host'. And then ata_host_put() is called again, the refcount is decreased to 0, ata_host_release() is called, all ports are freed and set to null. When unbinding the device after failure, ata_host_stop() is called to release the resources, it leads a null-ptr-deref(), because all the ports all freed and null. Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008 CPU: 7 PID: 18671 Comm: modprobe Kdump: loaded Tainted: G E 6.1.0-rc3+ #8 pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : ata_host_stop+0x3c/0x84 [libata] lr : release_nodes+0x64/0xd0 Call trace: ata_host_stop+0x3c/0x84 [libata] release_nodes+0x64/0xd0 devres_release_all+0xbc/0x1b0 device_unbind_cleanup+0x20/0x70 really_probe+0x158/0x320 __driver_probe_device+0x84/0x120 driver_probe_device+0x44/0x120 __driver_attach+0xb4/0x220 bus_for_each_dev+0x78/0xdc driver_attach+0x2c/0x40 bus_add_driver+0x184/0x240 driver_register+0x80/0x13c __pci_register_driver+0x4c/0x60 ahci_pci_driver_init+0x30/0x1000 [ahci] Fix this by removing redundant ata_host_put() in the error path.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.17 ≤ v < 4.19.2674.17 ≤ v < 5.10.1564.17 ≤ v < 5.15.804.17 ≤ v < 5.4.2254.17 ≤ v < 6.0.104.17 ≤ v < 6.14.20 ≤ v < 5.4.2255.11 ≤ v < 5.15.805.16 ≤ v < 6.0.105.5 ≤ v < 5.10.1562623c7a5f2799569d8bb05eb211da524a8144cb36.1 rc16.1 rc26.1 rc36.1 rc4
Vendor states this is fixed in 30e12e2be27ac6c4be2af4163c70db381364706f (fixed)
Vendor states this is fixed in 377ff82c33c0cb74562a353361b64b33c09562cf (fixed)
Vendor states this is fixed in 865a6da40ba092c18292ae5f6194756131293745 (fixed)
Vendor states this is fixed in 8c76310740807ade5ecdab5888f70ecb6d35732e (fixed)
Vendor states this is fixed in ac471468f7c16cda2525909946ca13ddbcd14000 (fixed)
Vendor states this is fixed in bec9ded5404cb14e5f5470103d0973a2ff83d6a5 (fixed)
Vendor states this is fixed in 4.17 (unaffected)
Vendor states this is fixed in 4.19.267 (unaffected)
Vendor states this is fixed in 5.10.156 (unaffected)
Vendor states this is fixed in 5.15.80 (unaffected)
Vendor states this is fixed in 5.4.225 (unaffected)
Vendor states this is fixed in 6.0.10 (unaffected)
Vendor states this is fixed in 6.1 (unaffected)

References (6)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/30e12e2be27ac6c4be2af4163c70db381364706f
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/377ff82c33c0cb74562a353361b64b33c09562cf
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/865a6da40ba092c18292ae5f6194756131293745
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/8c76310740807ade5ecdab5888f70ecb6d35732e
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/ac471468f7c16cda2525909946ca13ddbcd14000
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/bec9ded5404cb14e5f5470103d0973a2ff83d6a5

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-415

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card