KernelScan.io

HIGH Introduced in 5.11

nfc CoreInitRsp OOB

CVE-2026-90221

CVSS 7.8 / 10.0 KernelScan AI

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

01

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.

02

Engine v0.6.0

Risk summary

A malformed NFC CORE_INIT_RSP packet can cause reads of uninitialized kernel memory in the NCI (NFC Controller Interface) subsystem. This can lead to information disclosure, memory corruption, and kernel crashes. The vulnerability is reachable through the NFC device interface, which can be triggered by local users with access to NFC hardware or virtual NFC devices.

Affectednet/nfc/nci/rsp.c (NFC NCI subsystem)

Vulnerability analysis

The NFC NCI subsystem parses initialization response packets from NFC controllers without first checking that the packet contains enough data. A malicious or malformed response can claim to have more RF interfaces than it actually contains, causing the kernel to read past the end of the packet buffer into uninitialized memory. These uninitialized values are then stored and later used in subsequent operations. The fix adds length checks before accessing any packet fields, ensuring the full fixed-size header is present, validating each variable-length entry fits within the packet bounds, and truncating the interface count to only valid entries rather than the attacker-declared value.

03

BranchIntroducedFixed inPatch commit
5.155.115.15.221baed3fdf6ed2
6.15.116.1.1882f434478771a
6.125.116.12.110bbe68e8249e2
6.185.116.18.524f0483bbcdac
6.65.116.6.1575487f04c1ccb
7.25.117.2.67d44b897bff8
mainline5.117.3d56575a2595e
cip/6.15.116.1.189-cip612f434478771a
cip/6.1-rt5.116.1.189-cip61-rt322f434478771a
cip/6.125.116.12.111-cip32bbe68e8249e2

04

State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.

CIP treeState
cip/6.12Fixed in 6.12.111-cip32
cip/6.1Fixed in 6.1.189-cip61
cip/6.1-rtFixed in 6.1.189-cip61-rt32