CVE-2026-43291: net: nfc: nci: Fix parameter validation for packet data
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).
Security readout for executives and security teams
Plain-English summary
A Linux kernel NFC validation error can disrupt communication with NCI-based NFC chips. The supplied CVSS rates potential confidentiality, integrity, and availability impact highly, but the technical description primarily documents broken NFC communication. Systems without active NCI NFC functionality are less likely to be exposed.
Executive priority
Prioritize promptly where NFC is operational, especially on managed devices handling sensitive information or essential workflows. Treat other Linux systems as lower urgency after confirming they lack NCI NFC exposure. Require vendor-confirmed version mapping because the supplied version list is not sufficiently clear for package-level decisions.
Technical view
Commit 9c328f54741b added packet validation to prevent uninitialized-data access but incorrectly compared variable-length NCI packets against a fixed structure size. The supplied record says later stable-kernel commits correct this validation. CVSS 3.1 is 8.3 with adjacent access, low complexity, no privileges, and no user interaction.
Likely exposure
Exposure is limited to Linux systems using the affected NFC NCI kernel path and relevant kernel builds. The adjacent-network vector does not indicate internet-remote exploitation. The flattened version metadata contains ambiguous release boundaries, so validate distribution kernel packages against vendor advisories and referenced fixes.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation, public exploit code, or observed attacks. Successful exploitation conditions are not explained beyond the CVSS adjacent-access requirement. Do not treat the CVSS impact claims as proof of demonstrated exploitation.
Researcher notes
The description characterizes a regression in a prior safety fix: fixed-size validation rejects valid variable-length packet data. No CWE is assigned. The record’s CVSS claims high confidentiality and availability impact, but the supplied narrative does not explain those security outcomes. Review the referenced kernel diffs and vendor backports before concluding exploitability or exact affected ranges.
Mitigation direction
Check the Linux distribution or device vendor advisory for an explicitly fixed kernel package.
Apply the vendor-supported kernel update containing the corresponding stable-kernel correction.
Prioritize systems that actively use NCI-based NFC hardware or expose NFC functionality.
Follow vendor guidance for temporary risk reduction when immediate kernel replacement is impractical.
Validation and detection
Inventory kernel versions and identify systems with enabled NCI NFC drivers or hardware.
Compare packaged kernel changelogs against the referenced Linux stable correction commits.
Test NFC communication after updating, including legitimate variable-length NCI packet handling.
Confirm monitoring shows no recurring NFC driver failures after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43291 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
8Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.