CVE-2026-90221

nfc: nci: fix use of uninitialized memory in CORE_INIT_RSP parsing

N/A
Published: September 17, 2026 at 04:07 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.11bcd684aace34fedbd473fbd9b21ed06b0c2d2212
Vendor states this is fixed in 2f434478771a4ebdd535033561c0590bcde39753 (fixed)
Vendor states this is fixed in 4f0483bbcdaccc9d4aee30df7351863334cecfa7 (fixed)
Vendor states this is fixed in 5487f04c1ccbfa15aa6e531eb1ec9c9ec9c7bf31 (fixed)
Vendor states this is fixed in 7d44b897bff84edcd4814899314d661ad4956a8e (fixed)
Vendor states this is fixed in baed3fdf6ed2195c56f25ae18a086b938dcd3983 (fixed)
Vendor states this is fixed in bbe68e8249e2c76d65adfd9224fa95f1ca0fbe4e (fixed)
Vendor states this is fixed in d56575a2595ee1f597f39e8a1cfb67ed3501678d (fixed)
Vendor states this is fixed in 5.11 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card