Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 13 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38416, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.25% · top 84% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 – < a514fca2b8e95838a3ba600f31a18fa60b76d893
    • affected 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 – < 000bfbc6bc334a93fffca8f5aa9583e7b6356cb5
    • affected 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 – < ac6992f72bd8e22679c1e147ac214de6a7093c23
    • affected 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 – < dc7722619a9c307e9938d735cf4a2210d3d48dcb
    • affected 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 – < a8acc7080ad55c5402a1b818b3008998247dda87
    • affected 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 – < 55c3dbd8389636161090a2b2b6d2d709b9602e9c
    • affected 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 – < e9799db771b2d574d5bf0dfb3177485e5f40d4d6
    • affected 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 – < fc27ab48904ceb7e4792f0c400f1ef175edf16fe
  • Linux · Linux

    • affected 4.2
    • unaffected < 4.2
    • unaffected 5.4.295 – ≤ 5.4.*
    • unaffected 5.10.239 – ≤ 5.10.*
    • unaffected 5.15.186 – ≤ 5.15.*
    • unaffected 6.1.142 – ≤ 6.1.*
    • unaffected 6.6.95 – ≤ 6.6.*
    • unaffected 6.12.35 – ≤ 6.12.*
    • unaffected 6.15.4 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38416 badge
[![CVE-2025-38416](https://cveledger.app/badge/CVE-2025-38416.svg)](https://cveledger.app/cve/CVE-2025-38416)

Record last updated .