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-98579nfc: llcp: fix sdreq TLV list leak on parse/alloc/send failure

Description

In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: fix sdreq TLV list leak on parse/alloc/send failure nfc_genl_llc_sdreq() builds a list of TLV nodes while walking nested netlink attrs, but 3 error paths (nested-attr parse failure, TLV alloc ENOMEM, nfc_llcp_send_snl_sdreq() failure) all skip freeing what was already queued. Route them through a new free_list label, mirroring the SDRES path in the same file which already does this. Harmless on the success path too -- send_snl_sdreq() drains the list as it moves nodes, so it's already empty by the time free_list runs.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 1 day 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.22% · top 88% of all CVEs (16 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 d9b8d8e19b073096d3609bbd60f82148d128b555 – < 5b1eca82085134bd92cd3810b0ef003c91e3f668
    • affected d9b8d8e19b073096d3609bbd60f82148d128b555 – < d3f60a7fc291d08cd9192a3b4cd5d3a223fa7d02
    • affected d9b8d8e19b073096d3609bbd60f82148d128b555 – < 755bfc409748d8f3df64eb0eb26926270de3dd77
    • affected d9b8d8e19b073096d3609bbd60f82148d128b555 – < e43ec0191c1630f41e7043ac729ea6f1b8044a7f
    • affected d9b8d8e19b073096d3609bbd60f82148d128b555 – < 08d2c069239ab425fdd333784a6a3b3e034e4aa0
    • affected d9b8d8e19b073096d3609bbd60f82148d128b555 – < cbde7f5d326172d6dbb55cca0df42fa7e1ed8115
    • affected d9b8d8e19b073096d3609bbd60f82148d128b555 – < 0b01a946b0f234f5badd25968610b585a4895f08
    • affected d9b8d8e19b073096d3609bbd60f82148d128b555 – < 66f4300206b82b0b143ef0d9be90cd8d29f23a47
  • Linux · Linux

    • affected 3.10
    • unaffected < 3.10
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.55 – ≤ 6.18.*
    • unaffected 7.2.9 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .