Parameter Validation Flaw in Linux Kernel NFC NCI

Publication date: 2026-05-08

Last updated on: 2026-05-11

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: net: nfc: nci: Fix parameter validation for packet data Since commit 9c328f54741b ("net: nfc: nci: Add parameter validation for packet data") communication with nci nfc chips is not working any more. The mentioned commit tries to fix access of uninitialized data, but failed to understand that in some cases the data packet is of variable length and can therefore not be compared to the maximum packet length given by the sizeof(struct).

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-08

Last Modified

2026-05-11

Generated

2026-07-09

AI Q&A

2026-05-08

EPSS Evaluated

2026-07-08

NVD

CVE-2026-43291

EUVD

EUVD-2026-28561

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability relates to the Linux kernel's NFC (Near Field Communication) subsystem, specifically the nci driver. A recent commit intended to fix parameter validation for packet data introduced an issue where communication with nci NFC chips stopped working. The problem arose because the fix did not properly handle variable-length data packets, mistakenly comparing them to a fixed maximum packet length based on the size of a structure. This led to incorrect validation and access of uninitialized data.

Impact Analysis

The vulnerability can cause communication failures with NFC chips due to improper parameter validation. This may result in malfunctioning NFC features or devices relying on the Linux kernel's NFC subsystem. Additionally, accessing uninitialized data could potentially lead to unpredictable behavior or security risks, although specific impacts such as data leakage or privilege escalation are not detailed.

Hi! I’m here to help you understand CVE-2026-43291. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70