Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-90221: nfc: nci: fix use of uninitialized memory in CORE_INIT_RSP parsing

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 2f434478771a4ebdd535033561c0590bcde39753, 4f0483bbcdaccc9d4aee30df7351863334cecfa7, 5487f04c1ccbfa15aa6e531eb1ec9c9ec9c7bf31.

Low priority for now. Upgrade to Linux Linux 2f434478771a4ebdd535033561c0590bcde39753, 4f0483bbcdaccc9d4aee30df7351863334cecfa7, 5487f04c1ccbfa15aa6e531eb1ec9c9ec9c7bf31 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Sep 17, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-90221

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.11affected
    • bcd684aace34fedbd473fbd9b21ed06b0c2d2212 and later · before baed3fdf6ed2195c56f25ae18a086b938dcd3983affected · git
    • bcd684aace34fedbd473fbd9b21ed06b0c2d2212 and later · before 2f434478771a4ebdd535033561c0590bcde39753affected · git
    • bcd684aace34fedbd473fbd9b21ed06b0c2d2212 and later · before 5487f04c1ccbfa15aa6e531eb1ec9c9ec9c7bf31affected · git
    • bcd684aace34fedbd473fbd9b21ed06b0c2d2212 and later · before bbe68e8249e2c76d65adfd9224fa95f1ca0fbe4eaffected · git
    • bcd684aace34fedbd473fbd9b21ed06b0c2d2212 and later · before 4f0483bbcdaccc9d4aee30df7351863334cecfa7affected · git
    • bcd684aace34fedbd473fbd9b21ed06b0c2d2212 and later · before 7d44b897bff84edcd4814899314d661ad4956a8eaffected · git
    • bcd684aace34fedbd473fbd9b21ed06b0c2d2212 and later · before d56575a2595ee1f597f39e8a1cfb67ed3501678daffected · git
    • before 5.11not affected · semver
    • 5.15.221 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-90219Sep 17, 2026 · RDMA/cxgb4: Free debugfs on registration failure
    0Monitor
  • ← EarlierCVE-2026-90220Sep 17, 2026 · ALSA: seq: Don't leak the extension cell pointer in the bounce payload
    0Monitor
  • Later →CVE-2026-90222Sep 17, 2026 · nfc: pn533: hold a reference to the request skb during send_frame
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2f434478771a4ebdd535033561c0590bcde39753Vendor (CNA)
Linux Linux4f0483bbcdaccc9d4aee30df7351863334cecfa7Vendor (CNA)
Linux Linux5487f04c1ccbfa15aa6e531eb1ec9c9ec9c7bf31Vendor (CNA)
Linux Linux7d44b897bff84edcd4814899314d661ad4956a8eVendor (CNA)
Linux Linuxbaed3fdf6ed2195c56f25ae18a086b938dcd3983Vendor (CNA)
Linux Linuxbbe68e8249e2c76d65adfd9224fa95f1ca0fbe4eVendor (CNA)
Linux Linuxd56575a2595ee1f597f39e8a1cfb67ed3501678dVendor (CNA)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records