LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23330: nfc: nci: complete pending data exchange on device close

In the Linux kernel, the following vulnerability has been resolved: nfc: nci: complete pending data exchange on device close In nci_close_device(), complete any pending data exchange before closing. The data exchange callback (e.g. rawsock_data_exchange_complete) holds a socket reference. NIPA occasionally hits this leak: unreferenced object 0xff1100000f435000 (size 2048): comm "nci_dev", pid 3954, jiffies 4295441245 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 27 00 01 40 00 00 00 00 00 00 00 00 00 00 00 00 '..@............ backtrace (crc ec2b3c5): __kmalloc_noprof+0x4db/0x730 sk_prot_alloc.isra.0+0xe4/0x1d0 sk_alloc+0x36/0x760 rawsock_create+0xd1/0x540 nfc_sock_create+0x11f/0x280 __sock_create+0x22d/0x630 __sys_socket+0x115/0x1d0 __x64_sys_socket+0x72/0xd0 do_syscall_64+0x117/0xfc0 entry_SYSCALL_64_after_hwframe+0x4b/0x53

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a resource leak in the NFC NCI subsystem. When an NFC device is closed with a pending data exchange, a socket reference may not be released. The main business concern is reliability degradation on systems using affected kernel NFC functionality, not confirmed data theft or remote takeover.

Executive priority

Treat as a maintenance-priority kernel reliability issue. Prioritize systems where NFC functionality is enabled, exposed to untrusted local users, or part of sensitive embedded workflows. Escalate if vendors later assign high severity or report exploitation.

Technical view

The fix changes nci_close_device() to complete pending data exchanges before closing. The CVE text says the data exchange callback, such as rawsock_data_exchange_complete, holds a socket reference, and NIPA observed an unreferenced 2048-byte object leak through NFC raw socket creation paths.

Likely exposure

Exposure is most likely on Linux systems with the NFC NCI subsystem enabled and reachable by local users or workloads. The CVE record lists Linux kernel versions as affected, but distro-specific fixed builds and backports must be confirmed with vendor advisories.

Exploitation context

The provided sources do not report active exploitation, KEV listing, exploit availability, or remote attackability. The described condition is tied to NFC NCI device close handling during pending data exchange, suggesting a local or subsystem-access reliability risk unless vendor guidance states otherwise.

Researcher notes

No CWE, CVSS vector, or exploit status is provided. The evidence supports a kernel memory/socket reference leak fixed by completing pending NFC NCI data exchange callbacks during device close. Exact affected branch ranges are unclear from the bundled version markers alone.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable kernel fixes.
  • Map distro kernel packages to the fixed upstream commits before declaring systems remediated.
  • If NFC is not required, review vendor-supported options to disable or restrict NFC/NCI exposure.
  • Monitor vendor advisories for CVSS, affected branch, and backport clarification.

Validation and detection

  • Inventory Linux hosts and identify kernels with NFC/NCI support enabled.
  • Check whether the running kernel includes one of the referenced stable fixes.
  • Confirm distribution advisories mark the installed kernel package as fixed.
  • Review reliability telemetry for memory growth or NFC-related socket leaks.
Prepared
Confidence
medium
Sources
7

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-2026-23330 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux38f04c6b1b682f1879441e2925403ad9aff9e229, 38f04c6b1b682f1879441e2925403ad9aff9e229, 38f04c6b1b682f1879441e2925403ad9aff9e229, 38f04c6b1b682f1879441e2925403ad9aff9e229, 38f04c6b1b682f1879441e2925403ad9aff9e229unaffected
LinuxLinux3.2, 0, 6.6.136, 6.12.82, 6.18.17, 6.19.7, 7.0affected
Weakness

CWE details

No CWE listed

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