CVE-2025-38416
Last modified
CVE-2025-38416 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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?). EPSS estimates a 0.18% chance of exploitation in the next 30 days.
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().
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.2, < 5.4.295 | — |
| Linux | Linux Kernel | >= 5.5, < 5.10.239 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.186 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.142 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.95 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.35 | — |
| Linux | Linux Kernel | >= 6.13, < 6.15.4 | — |
| Linux | Linux Kernel | 6.16 | Rc1 |
| Debian | Debian Linux | 11.0 | — |
References
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlMailing List, Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlMailing List, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-38416?
How severe is CVE-2025-38416?
How do I fix CVE-2025-38416?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-38410In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38411In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38412In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38413In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38414In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38415In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38417In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38418In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38419In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3842A vulnerability was found in panhainan DS-Java 1.0 and class…9.8
- CVE-2025-38420In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38421In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2025-38416?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
