Unknown

CVE-2026-80794 — nfc: nci: fix uninit-value in the RF discover/activated NTF handlers

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 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+2

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.24%

ahead of 15% of scored CVEs · Oct 27, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and < 1007a6b429d756513abd25bd00290908f2e89a4a≥ e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and < 4bda9ef8392710f21e99027467f3f4afdfb5c99a≥ e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and < fe69fed3495f676578d49414a069ad7d8468e2ce≥ e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and < 7489f59d1ea2d3298aa41de7baf193e5e6e132f6≥ e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and < 7086dab72b3ed95df96842801e10e935cfeb27a3≥ e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and < 0d4b5cfab6891a5ca0f6aef209beebba4bd7c095≥ e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and < 5bd00c0e1470d90d77a7c60242854257ddf14e00≥ e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and < d6f743d3d388913135681cde051c08823730194f and 2 more ≥ e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 and < 8cbe06c1e699c0a165dae5093a2550e65f914818version 3.3	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 27, 2026 · 12 reading(s) · max 0.24%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 15, 2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Sep 4, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 19, 2026 – Oct 19, 2026
1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

11 on the record

nvd.nist.gov/vuln/detail/CVE-2026-80794
GitHub Security Advisories
git.kernel.org/stable/c/4bda9ef8392710f21e99027467f3f4afdfb5c99a
NIST National Vulnerability Database
git.kernel.org/stable/c/1007a6b429d756513abd25bd00290908f2e89a4a
NIST National Vulnerability Database
git.kernel.org/stable/c/7489f59d1ea2d3298aa41de7baf193e5e6e132f6
NIST National Vulnerability Database
git.kernel.org/stable/c/8cbe06c1e699c0a165dae5093a2550e65f914818
NIST National Vulnerability Database
git.kernel.org/stable/c/0d4b5cfab6891a5ca0f6aef209beebba4bd7c095
NIST National Vulnerability Database
github.com/advisories/GHSA-p4rx-vcw4-7733
GitHub Security Advisories
git.kernel.org/stable/c/5bd00c0e1470d90d77a7c60242854257ddf14e00
NIST National Vulnerability Database
git.kernel.org/stable/c/7086dab72b3ed95df96842801e10e935cfeb27a3
NIST National Vulnerability Database
git.kernel.org/stable/c/fe69fed3495f676578d49414a069ad7d8468e2ce
NIST National Vulnerability Database
git.kernel.org/stable/c/d6f743d3d388913135681cde051c08823730194f
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-99100 wifi: p54: validate firmware record lengths 6h
Unknown CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 1d
Unknown CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 1d
Unknown CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 1d
Unknown CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 1d
Unknown CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-80794 is "nfc: nci: fix uninit-value in the RF discover/activated NTF handlers", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.24% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.