CVE-2026-80799: nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers
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 2c1456fe09ab1a5a9fe1d8339ca6d509589b56e1, 2d239590d1845a706304833d40dd6d4fec20ad88, 382eaa770335acf4f16a5a55524500f2bb4207df.
Low priority for now. Upgrade to Linux Linux 2c1456fe09ab1a5a9fe1d8339ca6d509589b56e1, 2d239590d1845a706304833d40dd6d4fec20ad88, 382eaa770335acf4f16a5a55524500f2bb4207df 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: fix OOB read and u8 offset wrap in TLV parsers nfc_llcp_parse_gb_tlv() and nfc_llcp_parse_connection_tlv() contain three related bugs in their TLV parsing loops: 1. 'offset' is declared u8 but tlv_array_len is u16. When TLV data advances offset past 255 it silently wraps to zero, causing infinite loops or double-processing of buffer data. 2. Before reading tlv[0] (type) and tlv[1] (length) there is no check that offset+2 <= tlv_array_len. A truncated TLV causes an OOB read of one byte past the buffer end. 3. After reading the length field, the value bytes are accessed without checking offset+2+length <= tlv_array_len. A crafted length=0xFF on a short buffer causes up to 255 bytes of OOB read past the buffer end. Both functions are reachable without authentication via nfc_llcp_set_remote_gb() which feeds remote LLCP general bytes directly into nfc_llcp_parse_gb_tlv() with no additional validation. Fix all three issues by widening offset from u8 to u16 and adding bounds checks for both the TLV header and value field before each access.
- Published
- Sep 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- —
Report tools
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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
- 1deacb5e031e289ca5636f2db4fcae6612c05d34, 66a1be74230bbe098e651766c9a0cf4038db8442, 5.15affected
- 0be9de2ea01e8d52646e7310a7eef5459cf07ea8 and later · before 2c1456fe09ab1a5a9fe1d8339ca6d509589b56e1affected · git
- 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 and later · before 7f6f3d087c67a4346189ef2c36481455bbc59a74affected · git
- 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 and later · before 9c47d667963542c3cf8e3007b7f10c0904d08238affected · git
- 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 and later · before a209334ed929941b20810c17c3a507445b0a7c85affected · git
- 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 and later · before 382eaa770335acf4f16a5a55524500f2bb4207dfaffected · git
- 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 and later · before 2d239590d1845a706304833d40dd6d4fec20ad88affected · git
- 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 and later · before e84cdfdc4a6c88e8b751144458f2e04e24415a28affected · git
- 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 and later · before 875285a165fd3b402de2ab3be0deb355d6f4caf5affected · git
- 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 and later · before 78b20c8eeacd2e44a2d8a4cb5316d3c521d90911affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.107-1 | 6.12.107-1 |
| Debian:14 | linux | before 7.1.12-1 | 7.1.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80797Sep 4, 2026 · nfc: pn533: purge fragmented skbs during cleanup0Monitor
- ← EarlierCVE-2026-80798Sep 4, 2026 · nfc: llcp: reject PDUs shorter than the LLCP header0Monitor
- Later →CVE-2026-80800Sep 4, 2026 · nfc: llcp: bound the connect_sn TLV walk to the skb0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2c1456fe09ab1a5a9fe1d8339ca6d509589b56e1 | Vendor (CNA) |
| Linux Linux | 2d239590d1845a706304833d40dd6d4fec20ad88 | Vendor (CNA) |
| Linux Linux | 382eaa770335acf4f16a5a55524500f2bb4207df | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 5.10.267 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 78b20c8eeacd2e44a2d8a4cb5316d3c521d90911 | Vendor (CNA) |
| Linux Linux | 7f6f3d087c67a4346189ef2c36481455bbc59a74 | Vendor (CNA) |
| Linux Linux | 875285a165fd3b402de2ab3be0deb355d6f4caf5 | Vendor (CNA) |
| Linux Linux | 9c47d667963542c3cf8e3007b7f10c0904d08238 | Vendor (CNA) |
| Linux Linux | a209334ed929941b20810c17c3a507445b0a7c85 | Vendor (CNA) |
| Linux Linux | e84cdfdc4a6c88e8b751144458f2e04e24415a28 | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package 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.
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 researchersFinders, 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/2d239590d1845a706304833d40dd6d4fec20ad88
- git.kernel.org/stable/c/382eaa770335acf4f16a5a55524500f2bb4207df
- git.kernel.org/stable/c/78b20c8eeacd2e44a2d8a4cb5316d3c521d90911
- git.kernel.org/stable/c/7f6f3d087c67a4346189ef2c36481455bbc59a74
- git.kernel.org/stable/c/875285a165fd3b402de2ab3be0deb355d6f4caf5
- git.kernel.org/stable/c/9c47d667963542c3cf8e3007b7f10c0904d08238
- git.kernel.org/stable/c/a209334ed929941b20810c17c3a507445b0a7c85
- git.kernel.org/stable/c/e84cdfdc4a6c88e8b751144458f2e04e24415a28
Vendor advisories and official records. Exploit/PoC links are deliberately left out.