CVE-2026-80794
nfc: nci: fix uninit-value in the RF discover/activated NTF handlers
No known exploitation. EPSS puts it in the 9th percentile. Fixed versions are out.
No public exploit knownFix1 product4 fixed builds listed below
e.g. OID 1.3.6.1.4.1.25623.1.1.10.2026.0506
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20, < 1007a6b429d756513abd25bd00290908f2e89a4aUpgrade to: 1007a6b429d756513abd25bd00290908f2e89a4aAffected: ≥ e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20, < 4bda9ef8392710f21e99027467f3f4afdfb5c99aUpgrade to: 4bda9ef8392710f21e99027467f3f4afdfb5c99aAffected: ≥ e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20, < fe69fed3495f676578d49414a069ad7d8468e2ceUpgrade to: fe69fed3495f676578d49414a069ad7d8468e2ceAffected: ≥ e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20, < 7489f59d1ea2d3298aa41de7baf193e5e6e132f6Upgrade to: 7489f59d1ea2d3298aa41de7baf193e5e6e132f6 + 5 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 9th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
4 events over 45 days, from the signal feeds we watch.
- Record updated
- OpenVAS check added
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/0d4b5cfab6891a5ca0f6aef209beebba4bd7c095
- git.kernel.org/stable/c/1007a6b429d756513abd25bd00290908f2e89a4a
- git.kernel.org/stable/c/4bda9ef8392710f21e99027467f3f4afdfb5c99a
And 6 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI