LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26825: nfc: nci: free rx_data_reassembly skb on NCI device cleanup

In the Linux kernel, the following vulnerability has been resolved: nfc: nci: free rx_data_reassembly skb on NCI device cleanup rx_data_reassembly skb is stored during NCI data exchange for processing fragmented packets. It is dropped only when the last fragment is processed or when an NTF packet with NCI_OP_RF_DEACTIVATE_NTF opcode is received. However, the NCI device may be deallocated before that which leads to skb leak. As by design the rx_data_reassembly skb is bound to the NCI device and nothing prevents the device to be freed before the skb is processed in some way and cleaned, free it on the NCI device cleanup. Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-26825 is a Linux kernel NFC/NCI cleanup flaw. During fragmented NFC data handling, a stored network buffer may not be freed if the NCI device is removed first. The described impact is a kernel memory leak, so business urgency is mainly availability and hygiene, not confirmed data theft or remote takeover.

Executive priority

Treat this as a routine but real kernel maintenance item. It is not listed as actively exploited in the provided sources, but affected Linux systems should receive normal security updates, especially devices with NFC capabilities or long-lived kernels.

Technical view

The Linux NFC NCI path stores rx_data_reassembly skb while processing fragmented packets. It was freed after final fragment handling or RF deactivate notification, but not necessarily during NCI device cleanup. The fix frees that skb when the NCI device is cleaned up. Syzkaller found the issue via Linux Verification Center.

Likely exposure

Exposure is likely limited to systems running affected Linux kernel versions with NFC/NCI functionality present or enabled. The CVE source lists Linux kernel versions including 3.2 through 6.8 and multiple stable-branch fixes. Distribution exposure depends on vendor backports and package status.

Exploitation context

The source bundle does not show CISA KEV listing, public exploitation, CVSS, or a weaponized exploit. Evidence supports a memory-leak condition in kernel NFC/NCI cleanup, not confirmed active exploitation. Practical impact depends on whether an attacker can trigger relevant NFC/NCI device and fragmented packet behavior.

Researcher notes

Focus review on nfc/nci device lifecycle handling and rx_data_reassembly skb ownership. The evidence describes a leak when NCI device deallocation occurs before normal fragment completion or deactivate notification cleanup. Impact beyond resource leakage is not established in the provided sources.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • For Debian LTS systems, review the cited Debian advisories and update affected kernel packages.
  • Confirm whether NFC/NCI support is present on exposed Linux assets.
  • If patch timing is constrained, request vendor guidance for temporary NFC/NCI risk reduction.

Validation and detection

  • Inventory Linux kernel versions across servers, workstations, and embedded devices.
  • Check vendor package changelogs for CVE-2024-26825 or the referenced kernel commits.
  • Identify systems with NFC hardware, NFC services, or NCI kernel support enabled.
  • Prioritize validation on endpoints and embedded devices more likely to include NFC.
  • Re-scan after patching to confirm fixed kernel packages are installed.
Prepared
Confidence
high
Sources
12

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-2024-26825 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
2ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6a2968aaf50c7a22fced77a5e24aa636281efca8, 6a2968aaf50c7a22fced77a5e24aa636281efca8, 6a2968aaf50c7a22fced77a5e24aa636281efca8, 6a2968aaf50c7a22fced77a5e24aa636281efca8, 6a2968aaf50c7a22fced77a5e24aa636281efca8, 6a2968aaf50c7a22fced77a5e24aa636281efca8, 6a2968aaf50c7a22fced77a5e24aa636281efca8, 6a2968aaf50c7a22fced77a5e24aa636281efca8unaffected
LinuxLinux3.2, 0, 4.19.307, 5.4.269, 5.10.210, 5.15.149, 6.1.79, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

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