CVE-2026-80796

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

State
Published
Severity
Not scored
Published
Sep 4, 2026
Updated
Oct 19, 2026
Reserved
Aug 26, 2026

Read the record on cve.org

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 to before 1168484fe2b3828bf24a46f3c42a8719fade679bAffected
  • e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 to before be311c0cfeadfbe815ea22d2914a98d06e3fab0eAffected
  • e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 to before 04e51353cb9fa321caaeeed8331d4cd041fbaca7Affected
  • e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 to before e25b44bd8b8cc666b49a3fe0ef547e64d5b1e300Affected
  • e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 to before 9b01f5af0dc59263b59391b148bc78d83c0354a9Affected
  • e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 to before 9620a91f8d643b680f417a435db399a04d1e06d8Affected
  • e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 to before cf9d44be50b9074a5abdc301b4a3ba3e283591dfAffected
  • e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 to before f5c534b53f8c424a8e7633c9b585475c4bf4ee18Affected
  • e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 to before 0428fa2c22e2ba0cff766d3b80d461e149102045Affected
LinuxLinux
  • 3.3Affected
  • before 3.3Not affected
  • 5.10.269 through 5.10.*Not affected
  • 5.15.220 through 5.15.*Not affected
  • 6.1.187 through 6.1.*Not affected
  • 6.6.156 through 6.6.*Not affected
  • 6.12.108 through 6.12.*Not affected
  • 6.18.47 through 6.18.*Not affected
  • 7.1.11 through 7.1.*Not affected
  • 7.2.1 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.