LiveActive security incident?Get immediate response
CVE Record

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).

HighCVSS 8.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
medium
Sources
9

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.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
8.3CVSS 3.1HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H2.85.5Linux

Vulnerability scoring details

Base CVSS 3.1 score

8.3High
CVSS 3.1 vector shape for CVE-2026-43291Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8fcc7315a10a84264e55bb65ede10f0af20a983f, bfdda0123dde406dbff62e7e9136037e97998a15, 0ba68bea1e356f466ad29449938bea12f5f3711f, 74837bca0748763a77f77db47a0bdbe63b347628, 9c328f54741bd5465ca1dc717c84c04242fac2e1, 9c328f54741bd5465ca1dc717c84c04242fac2e1, 9c328f54741bd5465ca1dc717c84c04242fac2e1, c395d1e548cc68e84584ffa2e3ca9796a78bf7b9, 5.15.195, 6.1.156, 6.6.112, 6.12.53, 6.17.3unaffected
LinuxLinux6.18, 0, 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.16, 6.19.6, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.