linux-cve-announce - CVE-2022-49825: ata: libata-transport: fix error handling in ata_tport

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025050134-CVE-2022-49825-38fd@gregkh>
Date: Thu,  1 May 2025 16:10:15 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-49825: ata: libata-transport: fix error handling in ata_tport_add()

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

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

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

In ata_tport_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: 12 PID: 13605 Comm: rmmod Kdump: loaded Tainted: G        W          6.1.0-rc3+ #8
pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : device_del+0x48/0x39c
lr : device_del+0x44/0x39c
Call trace:
 device_del+0x48/0x39c
 attribute_container_class_device_del+0x28/0x40
 transport_remove_classdev+0x60/0x7c
 attribute_container_device_trigger+0x118/0x120
 transport_remove_device+0x20/0x30
 ata_tport_delete+0x34/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_tport_add().

The Linux kernel CVE team has assigned CVE-2022-49825 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 2.6.37 with commit d9027470b88631d0956ac37cdadfdeb9cdcf2c99 and fixed in 5.10.156 with commit b5362dc1634d8b8d5f30920f33ac11a3276b7ed9
	Issue introduced in 2.6.37 with commit d9027470b88631d0956ac37cdadfdeb9cdcf2c99 and fixed in 5.15.80 with commit e7bb1b7a7bf26f6b7372b7b683daece4a42fda02
	Issue introduced in 2.6.37 with commit d9027470b88631d0956ac37cdadfdeb9cdcf2c99 and fixed in 6.0.10 with commit 52d9bb0adae9359711a0c5271430afd3754069e7
	Issue introduced in 2.6.37 with commit d9027470b88631d0956ac37cdadfdeb9cdcf2c99 and fixed in 6.1 with commit 3613dbe3909dcc637fe6be00e4dc43b4aa0470ee

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2022-49825
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/ata/libata-transport.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	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