CVE-2026-80795 — nfc: nci: fix out-of-bounds write in nci_target_auto_activated()
In the Linux kernel, the following vulnerability has been resolved: nfc: nci: fix out-of-bounds write in nci_target_auto_activated() nci_target_auto_activated() appends a target to the fixed-size array ndev->targets[NCI_MAX_DISCOVERED_TARGETS] and increments ndev->n_targets without first checking the array is full; unlike its sibling nci_add_new_target(), which bails out when n_targets already equals NCI_MAX_DISCOVERED_TARGETS. ndev->n_targets is only cleared by nci_clear_target_list(), so an NFCC that repeatedly re-runs discovery (RF_DISCOVER_RSP, which re-enters NCI_DISCOVERY without clearing the target list) and reports an auto-activated target (RF_INTF_ACTIVATED_NTF) drives n_targets past the limit. The append then writes a struct nfc_target past the end of the array (a slab out-of-bounds write), and nfc_targets_found() goes on to walk the array with the inflated count: BUG: KASAN: slab-out-of-bounds in nci_add_new_protocol+0x94/0x2ac [nci] Write of size 2 at addr ffff0000c7299a18 by task kworker/u8:0/12 Workqueue: nfc0_nci_rx_wq nci_rx_work [nci] Call trace: nci_add_new_protocol+0x94/0x2ac [nci] nci_ntf_packet+0xddc/0x11a0 [nci] nci_rx_work+0x15c/0x1e0 [nci] process_one_work+0x2dc/0x500 worker_thread+0x240/0x460 kthread+0x1c0/0x1d0 ret_from_fork+0x10/0x20 The buggy address belongs to the cache kmalloc-2k of size 2048 The buggy address is located 1024 bytes to the right of allocated 1560-byte region [ffff0000c7299000, ffff0000c7299618) Guard nci_target_auto_activated() with the same check used by nci_add_new_target().
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
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.
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 |
≥ 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and < 0dc59de0075f88404a0f4a2b5233104ef459fbb2≥ 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and < 94530ffabfca57e9bff1d207106010014cc84032≥ 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and < afd8605fb43becb892311102844955c3b127fc7e≥ 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and < 24761d3a5f692df5f7d848caeabcb2afd10917aa≥ 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and < 50e87e1c0e18d791dcd7dccf30f9a2f3e2cf3951≥ 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and < 2f08dbce3b37624ec6b424d759336a99586170ec≥ 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and < d7083f41c21b30582e91b2e6de4d54dce74f6f9c≥ 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and < 129032c0616d83a5e3e304f6ebf88f14ba01e5f7 and 2 more≥ 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and < ac200079db50af81e6b04d058b33ec92901d8eddversion 3.4 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 29, 2026 · 14 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.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
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
- git.kernel.org/stable/c/0dc59de0075f88404a0f4a2b5233104ef459fbb2
- git.kernel.org/stable/c/d7083f41c21b30582e91b2e6de4d54dce74f6f9c
- git.kernel.org/stable/c/129032c0616d83a5e3e304f6ebf88f14ba01e5f7
- git.kernel.org/stable/c/afd8605fb43becb892311102844955c3b127fc7e
- nvd.nist.gov/vuln/detail/CVE-2026-80795
- github.com/advisories/GHSA-rj9g-hqc5-rqg9
- git.kernel.org/stable/c/ac200079db50af81e6b04d058b33ec92901d8edd
- git.kernel.org/stable/c/24761d3a5f692df5f7d848caeabcb2afd10917aa
- git.kernel.org/stable/c/50e87e1c0e18d791dcd7dccf30f9a2f3e2cf3951
- git.kernel.org/stable/c/94530ffabfca57e9bff1d207106010014cc84032
- git.kernel.org/stable/c/2f08dbce3b37624ec6b424d759336a99586170ec
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
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-80795 is "nfc: nci: fix out-of-bounds write in nci_target_auto_activated()", 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.
Sign in or create an account to comment and suggest corrections.