CVE Catalog

CVE-2026-90221

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel, the NFC NCI functions parsing the CORE_INIT_RSP packet do not validate the skb length. A malformed response can declare a large number of RF interfaces with insufficient data, causing reads of uninitialized memory.

Risk Assessment

Reading uninitialized kernel memory may leak sensitive data or cause system instability; the attack vector includes injecting a crafted response via virtual_ncidev.

Recommendation

Update the Linux kernel to a version containing skb length checks before accessing CORE_INIT_RSP packet fields.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: nfc: nci: fix use of uninitialized memory in CORE_INIT_RSP parsing nci_core_init_rsp_packet_v1() and nci_core_init_rsp_packet_v2() parse the CORE_INIT_RSP packet without validating that the skb contains enough data. A malformed response (e.g. injected via virtual_ncidev) can declare a large num_supported_rf_interfaces while providing insufficient data, causing reads of uninitialized slab memory. This is later used in nci_init_complete_req(), triggering a KMSAN uninit-value warning. Add skb length checks before accessing packet fields: - Validate the skb has at least 1 byte for the status field. - Validate the skb can hold the fixed-size header before parsing. - In v2, bounds-check each variable-length rf_interface entry and its extension parameters within the parsing loop. - In v1, verify the skb is large enough for both the variable-length rf_interfaces array and the trailing rsp_2 structure.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS