Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected bcd684aace34fedbd473fbd9b21ed06b0c2d2212 – < baed3fdf6ed2195c56f25ae18a086b938dcd3983
    • affected bcd684aace34fedbd473fbd9b21ed06b0c2d2212 – < 2f434478771a4ebdd535033561c0590bcde39753
    • affected bcd684aace34fedbd473fbd9b21ed06b0c2d2212 – < 5487f04c1ccbfa15aa6e531eb1ec9c9ec9c7bf31
    • affected bcd684aace34fedbd473fbd9b21ed06b0c2d2212 – < bbe68e8249e2c76d65adfd9224fa95f1ca0fbe4e
    • affected bcd684aace34fedbd473fbd9b21ed06b0c2d2212 – < 4f0483bbcdaccc9d4aee30df7351863334cecfa7
    • affected bcd684aace34fedbd473fbd9b21ed06b0c2d2212 – < 7d44b897bff84edcd4814899314d661ad4956a8e
    • affected bcd684aace34fedbd473fbd9b21ed06b0c2d2212 – < d56575a2595ee1f597f39e8a1cfb67ed3501678d
  • Linux · Linux

    • affected 5.11
    • unaffected < 5.11
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90221 badge
[![CVE-2026-90221](https://cveledger.app/badge/CVE-2026-90221.svg)](https://cveledger.app/cve/CVE-2026-90221)

Record last updated .