CVE-2025-21735: NFC: nci: Add bounds checking in nci_hci_create_pipe()
In the Linux kernel, the following vulnerability has been resolved:
NFC: nci: Add bounds checking in nci_hci_create_pipe()
The "pipe" variable is a u8 which comes from the network. If it's more
than 127, then it results in memory corruption in the caller,
nci_hci_connect_gate().
Security readout for executives and security teams
Plain-English summary
This Linux kernel NFC bug lets a network-supplied pipe value exceed the expected range, causing memory corruption in kernel NFC handling. The sources do not provide CVSS, public exploitation, or impact detail beyond memory corruption, so urgency depends on whether affected systems expose NFC/NCI functionality.
Executive priority
Treat as a targeted kernel update item, not a broad emergency from current evidence. Prioritize mobile, embedded, workstation, or industrial assets with NFC capability, and fold fixes into the next kernel maintenance cycle unless exposure is confirmed.
Technical view
CVE-2025-21735 is a bounds-checking flaw in nci_hci_create_pipe(). A u8 pipe value from the network greater than 127 can corrupt memory in nci_hci_connect_gate(). Kernel stable commits add validation across supported branches.
Likely exposure
Exposure is most likely on Linux systems with NFC/NCI kernel support enabled and reachable NFC-related communication paths. General servers without NFC hardware or enabled NFC stacks are likely lower exposure, but confirm kernel configuration and deployed versions.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of active exploitation or public exploit tooling. The described primitive is memory corruption in kernel code, but practical exploitability is not established by the provided sources.
Researcher notes
The key condition is an attacker-controlled pipe value above 127 reaching nci_hci_create_pipe(). Sources identify memory corruption in nci_hci_connect_gate(), but do not state privilege impact, required proximity, authentication, or reliable exploitation details.
Mitigation direction
Apply vendor kernel updates containing the referenced stable fixes.
Prioritize devices where NFC/NCI support is enabled or physically reachable.
Review Debian LTS advisories if running affected Debian kernels.
Check Siemens guidance for listed industrial product exposure.
Disable unused NFC functionality where vendor-supported until patched.
Validation and detection
Inventory Linux kernel versions across endpoints, appliances, and embedded devices.
Check whether NFC/NCI kernel modules or drivers are enabled.
Map deployed kernels to vendor advisories and stable fix commits.
Confirm Debian LTS or other vendor kernel packages are updated.
Document systems where NFC is absent, disabled, or not reachable.
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-21735 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
2ADP providers
12Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 27, 2025, 02:12 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.