Strix
63K

CVE-2026-80796

Unknown

Last modified

CVE-2026-80796 is a vulnerability of currently unknown severity. 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.

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20, < 1168484fe2b3828bf24a46f3c42a8719fade679b; >= e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20, < be311c0cfeadfbe815ea22d2914a98d06e3fab0e; >= e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20, < 04e51353cb9fa321caaeeed8331d4cd041fbaca7; >= e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20, < e25b44bd8b8cc666b49a3fe0ef547e64d5b1e300; >= e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20, < 9b01f5af0dc59263b59391b148bc78d83c0354a9; >= e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20, < 9620a91f8d643b680f417a435db399a04d1e06d8; >= e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20, < cf9d44be50b9074a5abdc301b4a3ba3e283591df; >= e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20, < f5c534b53f8c424a8e7633c9b585475c4bf4ee18; >= e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20, < 0428fa2c22e2ba0cff766d3b80d461e149102045
LinuxLinux3.3

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-80796?
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.
How severe is CVE-2026-80796?
Severity scoring for CVE-2026-80796 is pending analysis.
How do I fix CVE-2026-80796?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-80796?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST