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-80798nfc: llcp: reject PDUs shorter than the LLCP header

Description

In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: reject PDUs shorter than the LLCP header Every LLCP PDU begins with a two-byte header (DSAP/SSAP + PTYPE), but the receive path never checked that a frame is at least LLCP_HEADER_SIZE bytes before parsing it. nfc_llcp_rx_skb() reads the header via nfc_llcp_ptype()/nfc_llcp_dsap()/ nfc_llcp_ssap(), which dereference pdu->data[0] and pdu->data[1], and a CONNECT or CC PDU then computes tlv_array_len = skb->len - LLCP_HEADER_SIZE; as a size_t and hands it to the TLV walk. When the frame is shorter than the header the subtraction wraps to a huge value and the walk runs far past the buffer, an out-of-bounds read. A nearby NFC device can reach this without authentication; LLCP link activation happens automatically after NFC-DEP. Guard the common receive choke point __nfc_llcp_recv(), shared by both the target (nfc_llcp_data_received()) and initiator (nfc_llcp_recv()) paths, so a short skb is dropped before the rx_work worker parses it. Use pskb_may_pull() rather than a skb->len test so the two header bytes are guaranteed to sit in the skb linear area even for a non-linear skb, matching how the sibling NCI and HCI receive paths validate their headers. Reproduced with a KFENCE out-of-bounds read via /dev/virtual_nci on linux-next. Found by 0sec automated security-research tooling (https://0sec.ai).

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 45 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.23% · top 86% of all CVEs (14 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 d646960f7986fefb460a2b062d5ccc8ccfeacc3a – < e6ec76a68dce04884dfeccfe5a5f0e9f67c0ec82
    • affected d646960f7986fefb460a2b062d5ccc8ccfeacc3a – < f36cffea24bf3e2cc29a00d4b51dbcadc087d810
    • affected d646960f7986fefb460a2b062d5ccc8ccfeacc3a – < a7b9b449f5a5132221fff6adc11a9431ab8cd914
    • affected d646960f7986fefb460a2b062d5ccc8ccfeacc3a – < 3793d768b40f38bb97265dd5b9a8b8655c4e1b1d
    • affected d646960f7986fefb460a2b062d5ccc8ccfeacc3a – < eab47618e282602197db287ecbd1b09d356a2515
    • affected d646960f7986fefb460a2b062d5ccc8ccfeacc3a – < e969e98410051b1ef8cc318bfe0c7e3f24ec766d
    • affected d646960f7986fefb460a2b062d5ccc8ccfeacc3a – < ae5f20f5842f440b72d030e3a34fe182dd8eae42
    • affected d646960f7986fefb460a2b062d5ccc8ccfeacc3a – < d3d90243393c48146911c67fd3792b549d21d9e6
    • affected d646960f7986fefb460a2b062d5ccc8ccfeacc3a – < 95674f506c6376d6722a23144c9acd26609771ed
  • Linux · Linux

    • affected 3.3
    • unaffected < 3.3
    • unaffected 5.10.267 – ≤ 5.10.*
    • unaffected 5.15.218 – ≤ 5.15.*
    • unaffected 6.1.185 – ≤ 6.1.*
    • unaffected 6.6.154 – ≤ 6.6.*
    • unaffected 6.12.106 – ≤ 6.12.*
    • unaffected 6.18.47 – ≤ 6.18.*
    • unaffected 7.1.11 – ≤ 7.1.*
    • unaffected 7.2.1 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .