CVE-2025-38416
What it is
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().
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 5.4.295
- Linux Kernel < 5.10.239
- Linux Kernel < 5.15.186
- Linux Kernel < 6.1.142
- Linux Kernel < 6.6.95
- Linux Kernel < 6.12.35
- Linux Kernel < 6.15.4
- Linux Kernel 6.16
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-38416.md and follow it. Check whether this project is affected by CVE-2025-38416. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/000bfbc6bc334a93fffca8f5aa9583e7b6356cb5
- https://git.kernel.org/stable/c/55c3dbd8389636161090a2b2b6d2d709b9602e9c
- https://git.kernel.org/stable/c/a514fca2b8e95838a3ba600f31a18fa60b76d893
- https://git.kernel.org/stable/c/a8acc7080ad55c5402a1b818b3008998247dda87
- https://git.kernel.org/stable/c/ac6992f72bd8e22679c1e147ac214de6a7093c23
- https://git.kernel.org/stable/c/dc7722619a9c307e9938d735cf4a2210d3d48dcb
- https://git.kernel.org/stable/c/e9799db771b2d574d5bf0dfb3177485e5f40d4d6
- https://git.kernel.org/stable/c/fc27ab48904ceb7e4792f0c400f1ef175edf16fe
References
- https://git.kernel.org/stable/c/000bfbc6bc334a93fffca8f5aa9583e7b6356cb5
- https://git.kernel.org/stable/c/55c3dbd8389636161090a2b2b6d2d709b9602e9c
- https://git.kernel.org/stable/c/a514fca2b8e95838a3ba600f31a18fa60b76d893
- https://git.kernel.org/stable/c/a8acc7080ad55c5402a1b818b3008998247dda87
- https://git.kernel.org/stable/c/ac6992f72bd8e22679c1e147ac214de6a7093c23
- https://git.kernel.org/stable/c/dc7722619a9c307e9938d735cf4a2210d3d48dcb
- https://git.kernel.org/stable/c/e9799db771b2d574d5bf0dfb3177485e5f40d4d6
- https://git.kernel.org/stable/c/fc27ab48904ceb7e4792f0c400f1ef175edf16fe
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html