Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-80798: nfc: llcp: reject PDUs shorter than the LLCP header

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.23% (FIRST EPSS).
  • Fixed version: Linux Linux 3793d768b40f38bb97265dd5b9a8b8655c4e1b1d, 95674f506c6376d6722a23144c9acd26609771ed, a7b9b449f5a5132221fff6adc11a9431ab8cd914.

Low priority for now. Upgrade to Linux Linux 3793d768b40f38bb97265dd5b9a8b8655c4e1b1d, 95674f506c6376d6722a23144c9acd26609771ed, a7b9b449f5a5132221fff6adc11a9431ab8cd914 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: 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).

—No exploit Fix available
Published
Sep 4, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 14th 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-80798

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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

    • 3.3affected
    • d646960f7986fefb460a2b062d5ccc8ccfeacc3a and later · before e6ec76a68dce04884dfeccfe5a5f0e9f67c0ec82affected · git
    • d646960f7986fefb460a2b062d5ccc8ccfeacc3a and later · before f36cffea24bf3e2cc29a00d4b51dbcadc087d810affected · git
    • d646960f7986fefb460a2b062d5ccc8ccfeacc3a and later · before a7b9b449f5a5132221fff6adc11a9431ab8cd914affected · git
    • d646960f7986fefb460a2b062d5ccc8ccfeacc3a and later · before 3793d768b40f38bb97265dd5b9a8b8655c4e1b1daffected · git
    • d646960f7986fefb460a2b062d5ccc8ccfeacc3a and later · before eab47618e282602197db287ecbd1b09d356a2515affected · git
    • d646960f7986fefb460a2b062d5ccc8ccfeacc3a and later · before e969e98410051b1ef8cc318bfe0c7e3f24ec766daffected · git
    • d646960f7986fefb460a2b062d5ccc8ccfeacc3a and later · before ae5f20f5842f440b72d030e3a34fe182dd8eae42affected · git
    • d646960f7986fefb460a2b062d5ccc8ccfeacc3a and later · before d3d90243393c48146911c67fd3792b549d21d9e6affected · git
    • d646960f7986fefb460a2b062d5ccc8ccfeacc3a and later · before 95674f506c6376d6722a23144c9acd26609771edaffected · git

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.107-1~deb12u16.12.107-1~deb12u1
Debian:13linuxbefore 6.12.107-16.12.107-1
Debian:14linuxbefore 7.1.12-17.1.12-1

Same product

linux: all records

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-80796Sep 4, 2026 · nfc: nci: add data_len bound checks to activation parameter extractors
    0Monitor
  • ← EarlierCVE-2026-80797Sep 4, 2026 · nfc: pn533: purge fragmented skbs during cleanup
    0Monitor
  • Later →CVE-2026-80799Sep 4, 2026 · nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers
    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 Linux3793d768b40f38bb97265dd5b9a8b8655c4e1b1dVendor (CNA)
Linux Linux95674f506c6376d6722a23144c9acd26609771edVendor (CNA)
Linux Linuxa7b9b449f5a5132221fff6adc11a9431ab8cd914Vendor (CNA)
Linux Linuxae5f20f5842f440b72d030e3a34fe182dd8eae42Vendor (CNA)
Linux Linuxd3d90243393c48146911c67fd3792b549d21d9e6Vendor (CNA)
Linux Linuxe6ec76a68dce04884dfeccfe5a5f0e9f67c0ec82Vendor (CNA)
Linux Linuxe969e98410051b1ef8cc318bfe0c7e3f24ec766dVendor (CNA)
Linux Linuxeab47618e282602197db287ecbd1b09d356a2515Vendor (CNA)
Linux Linuxf36cffea24bf3e2cc29a00d4b51dbcadc087d810Vendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0—Microsoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.107-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.

Credits

All researchers

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

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records