CVE-2026-80794: nfc: nci: fix uninit-value in the RF discover/activated NTF handlers
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 0d4b5cfab6891a5ca0f6aef209beebba4bd7c095, 1007a6b429d756513abd25bd00290908f2e89a4a, 4bda9ef8392710f21e99027467f3f4afdfb5c99a.
Low priority for now. Upgrade to Linux Linux 0d4b5cfab6891a5ca0f6aef209beebba4bd7c095, 1007a6b429d756513abd25bd00290908f2e89a4a, 4bda9ef8392710f21e99027467f3f4afdfb5c99a 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: fix uninit-value in the RF discover/activated NTF handlers nci_rf_discover_ntf_packet() and nci_rf_intf_activated_ntf_packet() each parse a notification into an on-stack struct (nci_rf_discover_ntf / nci_rf_intf_activated_ntf) that is not initialised. The RF technology-specific parameters are only extracted when rf_tech_specific_params_len is non-zero, so a notification that reports a zero length leaves the rf_tech_specific_params union uninitialised - and both handlers then pass it to nci_add_new_protocol(), which reads it: - discover: nci_add_new_target() -> nci_add_new_protocol(); - activated: nci_target_auto_activated() -> nci_add_new_protocol(). nci_add_new_protocol() uses nfca_poll->nfcid1_len as both a branch condition and a memcpy() length and copies nfcid1/sens_res/sel_res into ndev->targets, which is later exposed to user space via NFC_CMD_GET_TARGET. BUG: KMSAN: uninit-value in nci_add_new_protocol+0x624/0x6c0 nci_add_new_protocol+0x624/0x6c0 nci_ntf_packet+0x25b2/0x3c30 nci_rx_work+0x318/0x5d0 process_scheduled_works+0x84b/0x17a0 worker_thread+0xc10/0x11b0 kthread+0x376/0x500 Local variable ntf.i created at: nci_ntf_packet+0xbc2/0x3c30 Zero-initialise both on-stack notifications so the union reads back as zero when no technology-specific parameters are present.
- 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 1007a6b429d756513abd25bd00290908f2e89a4aaffected · git
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before 4bda9ef8392710f21e99027467f3f4afdfb5c99aaffected · git
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before fe69fed3495f676578d49414a069ad7d8468e2ceaffected · git
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before 7489f59d1ea2d3298aa41de7baf193e5e6e132f6affected · git
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before 7086dab72b3ed95df96842801e10e935cfeb27a3affected · git
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before 0d4b5cfab6891a5ca0f6aef209beebba4bd7c095affected · git
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before 5bd00c0e1470d90d77a7c60242854257ddf14e00affected · git
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before d6f743d3d388913135681cde051c08823730194faffected · git
- e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and later · before 8cbe06c1e699c0a165dae5093a2550e65f914818affected · 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-80792Sep 4, 2026 · ipv6: fix use-after-free in ip6_finish_output2()0Monitor
- ← EarlierCVE-2026-80793Sep 4, 2026 · ipv4: reject undersized MTUs in ip_do_fragment()0Monitor
- Later →CVE-2026-80795Sep 4, 2026 · nfc: nci: fix out-of-bounds write in nci_target_auto_activated()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 / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0d4b5cfab6891a5ca0f6aef209beebba4bd7c095 | Vendor (CNA) |
| Linux Linux | 1007a6b429d756513abd25bd00290908f2e89a4a | Vendor (CNA) |
| Linux Linux | 4bda9ef8392710f21e99027467f3f4afdfb5c99a | Vendor (CNA) |
| Linux Linux | 5bd00c0e1470d90d77a7c60242854257ddf14e00 | Vendor (CNA) |
| Linux Linux | 7086dab72b3ed95df96842801e10e935cfeb27a3 | Vendor (CNA) |
| Linux Linux | 7489f59d1ea2d3298aa41de7baf193e5e6e132f6 | Vendor (CNA) |
| Linux Linux | 8cbe06c1e699c0a165dae5093a2550e65f914818 | Vendor (CNA) |
| Linux Linux | d6f743d3d388913135681cde051c08823730194f | Vendor (CNA) |
| Linux Linux | fe69fed3495f676578d49414a069ad7d8468e2ce | 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.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/1007a6b429d756513abd25bd00290908f2e89a4a
- git.kernel.org/stable/c/4bda9ef8392710f21e99027467f3f4afdfb5c99a
- git.kernel.org/stable/c/5bd00c0e1470d90d77a7c60242854257ddf14e00
- git.kernel.org/stable/c/7086dab72b3ed95df96842801e10e935cfeb27a3
- git.kernel.org/stable/c/7489f59d1ea2d3298aa41de7baf193e5e6e132f6
- git.kernel.org/stable/c/8cbe06c1e699c0a165dae5093a2550e65f914818
- git.kernel.org/stable/c/d6f743d3d388913135681cde051c08823730194f
- git.kernel.org/stable/c/fe69fed3495f676578d49414a069ad7d8468e2ce
Vendor advisories and official records. Exploit/PoC links are deliberately left out.