Description
In the Linux kernel, the following vulnerability has been resolved:

nfc: nci: add data_len bound checks to activation parameter extractors

nci_extract_activation_params_iso_dep() and
nci_extract_activation_params_nfc_dep() read an inner length byte from
the NCI RF_INTF_ACTIVATED_NTF payload and use it to memcpy() into fixed
kernel buffers, but neither function receives the caller-validated
activation_params_len. A crafted NCI notification with
activation_params_len=1 and an inner length byte of up to 20 (NFC-A) or
50 (NFC-B) causes memcpy() to read that many bytes past the one valid
byte in the activation params region -- a slab out-of-bounds read of
kernel memory adjacent to the NCI skb.

The sibling nci_extract_rf_params_*() family was given equivalent
protection by commit 571dcbeb8e63 ("net: nfc: nci: Fix parameter
validation for packet data"), but the two activation parameter
extractors were not updated at that time.

Add a data_len parameter to both functions, guard against an empty
region before consuming the inner length byte, decrement the remaining
count after consuming it, and clamp the copy length to what is actually
available. Update both call sites to pass ntf.activation_params_len,
which is already validated against the skb at ntf.c:801.
Published: 2026-09-04
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A crafted NFC notification can cause the Linux kernel to read up to 20 or 50 bytes beyond a single-byte activation parameter region, leading to an out‑of‑bounds kernel memory read. The vulnerability lies in missing bounds checks in two nfc/nci activation parameter extractors, allowing an attacker to expose kernel data adjacent to the sk_buff. This read can leak sensitive information, facilitate privilege escalation, or aid further exploitation, impacting confidentiality system‑wide.

Affected Systems

All Linux kernel builds that include the nfc/nci subsystem prior to the patch that adds bound checks are affected. The fix is applied in all downstream distributions that update to a kernel containing the commit implementing the data_len parameter validation. Versions without the patch have the vulnerability present.

Risk and Exploitability

The relative severity is not scored (no CVSS provided) and the EPSS score is unavailable, but the vulnerability is not currently listed in CISA KEV. The exploit requires crafting a malicious NFC notification, which could be delivered locally by a nearby NFC device or remotely if the system accepts NFC traffic from untrusted sources. The lack of publicly known exploits and the dependence on physical or proximate access suggest a moderate risk, provided the nfc/nci stack is active and the kernel is vulnerable.

Generated by OpenCVE AI on September 4, 2026 at 17:44 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update to the latest Linux kernel release that incorporates the commit adding data_len bounds checks to the nfc/nci activation parameter extractors.
  • If an upgrade is not immediately possible, disable or unload the nfc and nci kernel modules to eliminate the vulnerable code path.
  • Restrict or block unsolicited NFC traffic from untrusted devices using firewall or device‑level access controls to reduce the likelihood of an attacker delivering a crafted notification.

Generated by OpenCVE AI on September 4, 2026 at 17:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 04 Sep 2026 18:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-119

Fri, 04 Sep 2026 15:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: nfc: nci: add data_len bound checks to activation parameter extractors nci_extract_activation_params_iso_dep() and nci_extract_activation_params_nfc_dep() read an inner length byte from the NCI RF_INTF_ACTIVATED_NTF payload and use it to memcpy() into fixed kernel buffers, but neither function receives the caller-validated activation_params_len. A crafted NCI notification with activation_params_len=1 and an inner length byte of up to 20 (NFC-A) or 50 (NFC-B) causes memcpy() to read that many bytes past the one valid byte in the activation params region -- a slab out-of-bounds read of kernel memory adjacent to the NCI skb. The sibling nci_extract_rf_params_*() family was given equivalent protection by commit 571dcbeb8e63 ("net: nfc: nci: Fix parameter validation for packet data"), but the two activation parameter extractors were not updated at that time. Add a data_len parameter to both functions, guard against an empty region before consuming the inner length byte, decrement the remaining count after consuming it, and clamp the copy length to what is actually available. Update both call sites to pass ntf.activation_params_len, which is already validated against the skb at ntf.c:801.
Title nfc: nci: add data_len bound checks to activation parameter extractors
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-04T15:13:09.857Z

Reserved: 2026-08-26T14:34:25.793Z

Link: CVE-2026-80796

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-04T16:18:06.180

Modified: 2026-09-04T16:18:06.180

Link: CVE-2026-80796

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-04T23:00:15Z

Weaknesses
  • CWE-119

    Improper Restriction of Operations within the Bounds of a Memory Buffer