LiveActive security incident?Get immediate response
CVE Record

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

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

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux NFC UART initialization flaw briefly exposes internal state before setup succeeds. If data arrives during that window, the kernel may process it against an incompletely opened device. The supplied assessment rates potential confidentiality, integrity, and availability impact as high, but exploitation requires local access and the relevant NFC UART functionality.

Executive priority

Treat this as a high-priority kernel maintenance issue for Linux endpoints or appliances using NFC over UART. It does not justify an internet-wide emergency response because the documented attack vector is local and active exploitation is unsupported. Accelerate vendor-approved updates on exposed systems, then validate backport status for managed distribution kernels.

Technical view

The NCI UART line discipline assigned tty->disc_data before NCI device opening and module-reference acquisition completed. Error handling could therefore leave a short interval where incoming device data reached partially initialized state. The stable fix assigns disc_data only after both operations succeed. The bundle does not identify a CWE or document a demonstrated exploitation method.

Likely exposure

Exposure is most plausible on affected Linux systems using the NFC NCI UART path. The supplied version data lists multiple affected kernel releases, but does not provide reliable distribution-specific package boundaries. Systems without this functionality may have lower practical exposure. Confirm kernel packages, NFC configuration, and vendor backports rather than relying only on upstream version numbers.

Exploitation context

The CVSS 3.1 vector is 7.8 and indicates local access, low privileges, low complexity, and no user interaction. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public proof of concept. Physical or logical access to the relevant local interface may constrain practical attacks, but exact prerequisites are not documented.

Researcher notes

The central issue is premature publication of tty->disc_data during NCI UART setup, creating a race-like exposure to inbound data before initialization succeeds. The fix narrows object visibility to the successful path. The supplied record does not establish the exact unsafe consequence, reachable failure states, hardware requirements, affected configurations, or exploitation reliability, so those details require code-level validation.

Mitigation direction

  • Apply the distribution kernel security update containing the applicable upstream stable fix.
  • Check vendor advisories for exact fixed package versions and supported release branches.
  • If patching is delayed, request vendor-supported mitigations; none are specified in the supplied sources.
  • Prioritize systems where NFC NCI UART functionality is present or operationally required.

Validation and detection

  • Inventory kernel versions and distribution package revisions across Linux systems.
  • Determine whether NFC NCI UART functionality is configured, loaded, or attached to hardware.
  • Confirm the installed kernel contains the applicable referenced stable commit or vendor backport.
  • Review vendor security notices for package-specific remediation status.
  • After updating, verify systems boot normally and required NFC functions still operate.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38416 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
11Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-38416Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9961127d4bce6325e9a0b0fb105e0c85a6c62cb7, 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7, 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7, 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7, 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7, 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7, 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7, 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7unaffected
LinuxLinux4.2, 0, 5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.95, 6.12.35, 6.15.4, 6.16affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.