[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025072511-CVE-2025-38416-e4bb@gregkh>
Date: Fri, 25 Jul 2025 16:00:12 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38416: NFC: nci: uart: Set tty->disc_data only in success path
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
NFC: nci: uart: Set tty->disc_data only in success path
Setting tty->disc_data before opening the NCI device means we need to
clean it up on error paths. This also opens some short window if device
starts sending data, even before NCIUARTSETDRIVER IOCTL succeeded
(broken hardware?). Close the window by exposing tty->disc_data only on
the success path, when opening of the NCI device and try_module_get()
succeeds.
The code differs in error path in one aspect: tty->disc_data won't be
ever assigned thus NULL-ified. This however should not be relevant
difference, because of "tty->disc_data=NULL" in nci_uart_tty_open().
The Linux kernel CVE team has assigned CVE-2025-38416 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.2 with commit 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 and fixed in 5.4.295 with commit a514fca2b8e95838a3ba600f31a18fa60b76d893
Issue introduced in 4.2 with commit 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 and fixed in 5.10.239 with commit 000bfbc6bc334a93fffca8f5aa9583e7b6356cb5
Issue introduced in 4.2 with commit 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 and fixed in 5.15.186 with commit ac6992f72bd8e22679c1e147ac214de6a7093c23
Issue introduced in 4.2 with commit 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 and fixed in 6.1.142 with commit dc7722619a9c307e9938d735cf4a2210d3d48dcb
Issue introduced in 4.2 with commit 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 and fixed in 6.6.95 with commit a8acc7080ad55c5402a1b818b3008998247dda87
Issue introduced in 4.2 with commit 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 and fixed in 6.12.35 with commit 55c3dbd8389636161090a2b2b6d2d709b9602e9c
Issue introduced in 4.2 with commit 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 and fixed in 6.15.4 with commit e9799db771b2d574d5bf0dfb3177485e5f40d4d6
Issue introduced in 4.2 with commit 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 and fixed in 6.16-rc3 with commit fc27ab48904ceb7e4792f0c400f1ef175edf16fe
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-2025-38416
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:
net/nfc/nci/uart.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/a514fca2b8e95838a3ba600f31a18fa60b76d893
https://git.kernel.org/stable/c/000bfbc6bc334a93fffca8f5aa9583e7b6356cb5
https://git.kernel.org/stable/c/ac6992f72bd8e22679c1e147ac214de6a7093c23
https://git.kernel.org/stable/c/dc7722619a9c307e9938d735cf4a2210d3d48dcb
https://git.kernel.org/stable/c/a8acc7080ad55c5402a1b818b3008998247dda87
https://git.kernel.org/stable/c/55c3dbd8389636161090a2b2b6d2d709b9602e9c
https://git.kernel.org/stable/c/e9799db771b2d574d5bf0dfb3177485e5f40d4d6
https://git.kernel.org/stable/c/fc27ab48904ceb7e4792f0c400f1ef175edf16fe
Powered by blists - more mailing lists