CVE-2026-80796: nfc: nci: add data_len bound checks to activation parameter extractors
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.19% (FIRST EPSS).
- Fixed version: Linux Linux 0428fa2c22e2ba0cff766d3b80d461e149102045, 04e51353cb9fa321caaeeed8331d4cd041fbaca7, 1168484fe2b3828bf24a46f3c42a8719fade679b.
Low priority for now. Upgrade to Linux Linux 0428fa2c22e2ba0cff766d3b80d461e149102045, 04e51353cb9fa321caaeeed8331d4cd041fbaca7, 1168484fe2b3828bf24a46f3c42a8719fade679b 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: nci: add data_len bound checks to activation parameter extractors nci_extract_activation_params_iso_dep() and nci_extract_activation_params_nfc_dep() read an inner length byte from the NCI RF_INTF_ACTIVATED_NTF payload and use it to memcpy() into fixed kernel buffers, but neither function receives the caller-validated activation_params_len. A crafted NCI notification with activation_params_len=1 and an inner length byte of up to 20 (NFC-A) or 50 (NFC-B) causes memcpy() to read that many bytes past the one valid byte in the activation params region -- a slab out-of-bounds read of kernel memory adjacent to the NCI skb. The sibling nci_extract_rf_params_*() family was given equivalent protection by commit 571dcbeb8e63 ("net: nfc: nci: Fix parameter validation for packet data"), but the two activation parameter extractors were not updated at that time. Add a data_len parameter to both functions, guard against an empty region before consuming the inner length byte, decrement the remaining count after consuming it, and clamp the copy length to what is actually available. Update both call sites to pass ntf.activation_params_len, which is already validated against the skb at ntf.c:801.
- Published
- Sep 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 9th 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.1%
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
- 3.3affected
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before 1168484fe2b3828bf24a46f3c42a8719fade679baffected · git
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before be311c0cfeadfbe815ea22d2914a98d06e3fab0eaffected · git
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before 04e51353cb9fa321caaeeed8331d4cd041fbaca7affected · git
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before e25b44bd8b8cc666b49a3fe0ef547e64d5b1e300affected · git
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before 9b01f5af0dc59263b59391b148bc78d83c0354a9affected · git
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before 9620a91f8d643b680f417a435db399a04d1e06d8affected · git
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before cf9d44be50b9074a5abdc301b4a3ba3e283591dfaffected · git
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before f5c534b53f8c424a8e7633c9b585475c4bf4ee18affected · git
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before 0428fa2c22e2ba0cff766d3b80d461e149102045affected · 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.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-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-80794Sep 4, 2026 · nfc: nci: fix uninit-value in the RF discover/activated NTF handlers0Monitor
- ← EarlierCVE-2026-80795Sep 4, 2026 · nfc: nci: fix out-of-bounds write in nci_target_auto_activated()0Monitor
- Later →CVE-2026-80797Sep 4, 2026 · nfc: pn533: purge fragmented skbs during cleanup0Monitor
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 | 0428fa2c22e2ba0cff766d3b80d461e149102045 | Vendor (CNA) |
| Linux Linux | 04e51353cb9fa321caaeeed8331d4cd041fbaca7 | Vendor (CNA) |
| Linux Linux | 1168484fe2b3828bf24a46f3c42a8719fade679b | Vendor (CNA) |
| Linux Linux | 9620a91f8d643b680f417a435db399a04d1e06d8 | Vendor (CNA) |
| Linux Linux | 9b01f5af0dc59263b59391b148bc78d83c0354a9 | Vendor (CNA) |
| Linux Linux | be311c0cfeadfbe815ea22d2914a98d06e3fab0e | Vendor (CNA) |
| Linux Linux | cf9d44be50b9074a5abdc301b4a3ba3e283591df | Vendor (CNA) |
| Linux Linux | e25b44bd8b8cc666b49a3fe0ef547e64d5b1e300 | Vendor (CNA) |
| Linux Linux | f5c534b53f8c424a8e7633c9b585475c4bf4ee18 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-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/04e51353cb9fa321caaeeed8331d4cd041fbaca7
- git.kernel.org/stable/c/1168484fe2b3828bf24a46f3c42a8719fade679b
- git.kernel.org/stable/c/9620a91f8d643b680f417a435db399a04d1e06d8
- git.kernel.org/stable/c/9b01f5af0dc59263b59391b148bc78d83c0354a9
- git.kernel.org/stable/c/be311c0cfeadfbe815ea22d2914a98d06e3fab0e
- git.kernel.org/stable/c/cf9d44be50b9074a5abdc301b4a3ba3e283591df
- git.kernel.org/stable/c/e25b44bd8b8cc666b49a3fe0ef547e64d5b1e300
- git.kernel.org/stable/c/f5c534b53f8c424a8e7633c9b585475c4bf4ee18
Vendor advisories and official records. Exploit/PoC links are deliberately left out.