CVE-2025-38416

NFC: nci: uart: Set tty->disc_data only in success path

HIGH
7.8
CVSS Score
Published: July 25, 2025 at 02:00 PM UTC
Updated: August 5, 2026 at 12:44 PM UTC
2 products affected across 2 vendorsLinux KernelDebian Linux

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.3%

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().

Affected

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

4.2 ≤ v < 5.10.2394.2 ≤ v < 5.15.1864.2 ≤ v < 5.4.2954.2 ≤ v < 6.1.1424.2 ≤ v < 6.12.354.2 ≤ v < 6.15.44.2 ≤ v < 6.164.2 ≤ v < 6.6.955.11 ≤ v < 5.15.1865.16 ≤ v < 6.1.1425.5 ≤ v < 5.10.2396.13 ≤ v < 6.15.46.2 ≤ v < 6.6.956.7 ≤ v < 6.12.356.16 rc16.16 rc29961127d4bce6325e9a0b0fb105e0c85a6c62cb7
Vendor states this is fixed in 000bfbc6bc334a93fffca8f5aa9583e7b6356cb5 (fixed)
Vendor states this is fixed in 55c3dbd8389636161090a2b2b6d2d709b9602e9c (fixed)
Vendor states this is fixed in a514fca2b8e95838a3ba600f31a18fa60b76d893 (fixed)
Vendor states this is fixed in a8acc7080ad55c5402a1b818b3008998247dda87 (fixed)
Vendor states this is fixed in ac6992f72bd8e22679c1e147ac214de6a7093c23 (fixed)
Vendor states this is fixed in dc7722619a9c307e9938d735cf4a2210d3d48dcb (fixed)
Vendor states this is fixed in e9799db771b2d574d5bf0dfb3177485e5f40d4d6 (fixed)
Vendor states this is fixed in fc27ab48904ceb7e4792f0c400f1ef175edf16fe (fixed)
Vendor states this is fixed in 4.2 (unaffected)
Vendor states this is fixed in 5.10.239 (unaffected)
Vendor states this is fixed in 5.15.186 (unaffected)
Vendor states this is fixed in 5.4.295 (unaffected)
Vendor states this is fixed in 6.1.142 (unaffected)
Vendor states this is fixed in 6.12.35 (unaffected)
Vendor states this is fixed in 6.15.4 (unaffected)
Vendor states this is fixed in 6.16 (unaffected)
Vendor states this is fixed in 6.6.95 (unaffected)

References (10)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/000bfbc6bc334a93fffca8f5aa9583e7b6356cb5
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/55c3dbd8389636161090a2b2b6d2d709b9602e9c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/a514fca2b8e95838a3ba600f31a18fa60b76d893
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/a8acc7080ad55c5402a1b818b3008998247dda87
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/ac6992f72bd8e22679c1e147ac214de6a7093c23
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/dc7722619a9c307e9938d735cf4a2210d3d48dcb
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e9799db771b2d574d5bf0dfb3177485e5f40d4d6
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/fc27ab48904ceb7e4792f0c400f1ef175edf16fe

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

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