CVE-2026-80795 json
nfc: nci: fix out-of-bounds write in nci_target_auto_activated()
published 2026-09-04 2 mo ago modified 2026-10-19 20 d ago also EUVD-2026-71438
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
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().
Patch / fix
- Linux Linux 5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106, 6.18.47, 7.1.11, 7.2.1, 7.3
- linux Debian 12 6.1.187-1
- linux Debian 13 6.12.107-1
- linux Debian 14 7.1.12-1
- linux-6.12 Debian 12 6.12.107-1~deb12u1
debian advisories DEBIAN-CVE-2026-80795
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-gke Ubuntu 22.04 LTS 5.15.0-1115.121
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1113.117
ubuntu advisories UBUNTU-CVE-2026-80795
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source Linux Micro 6.0 6.4.0-159998.55.1
- kernel-default Linux Micro 6.0 6.4.0-159998.55.1
- kernel-kvmsmall Linux Micro 6.0 6.4.0-159998.55.1
- kernel-default-base Linux Micro 6.0 6.4.0-159998.55.1.159998.21.42
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.90.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.90.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.90.1
- kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.90.1
suse advisories SUSE-SU-2026:24550-1SUSE-SU-2026:5091-1
- kernel-source openSUSE Tumbleweed 7.2.5-1.1
opensuse advisories openSUSE-SU-2026:11773-1
- git.kernel.org/stable/c/0dc59de0075f88404a0f4a2b5233104ef459fbb2 commit
- git.kernel.org/stable/c/94530ffabfca57e9bff1d207106010014cc84032 commit
- git.kernel.org/stable/c/afd8605fb43becb892311102844955c3b127fc7e commit
- git.kernel.org/stable/c/24761d3a5f692df5f7d848caeabcb2afd10917aa commit
- git.kernel.org/stable/c/50e87e1c0e18d791dcd7dccf30f9a2f3e2cf3951 commit
- git.kernel.org/stable/c/2f08dbce3b37624ec6b424d759336a99586170ec commit
- git.kernel.org/stable/c/d7083f41c21b30582e91b2e6de4d54dce74f6f9c commit
- git.kernel.org/stable/c/129032c0616d83a5e3e304f6ebf88f14ba01e5f7 commit
- git.kernel.org/stable/c/ac200079db50af81e6b04d058b33ec92901d8edd commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-80795 updated cvss 5.5
kernel: nfc: nci: fix out-of-bounds write in nci_target_auto_activated()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
+1 more productsfewer
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/0dc59de0075f88404a0f4a2b5233104ef459fbb2
- git.kernel.org /stable/c/94530ffabfca57e9bff1d207106010014cc84032
- git.kernel.org /stable/c/afd8605fb43becb892311102844955c3b127fc7e
- git.kernel.org /stable/c/24761d3a5f692df5f7d848caeabcb2afd10917aa
- git.kernel.org /stable/c/50e87e1c0e18d791dcd7dccf30f9a2f3e2cf3951
- git.kernel.org /stable/c/2f08dbce3b37624ec6b424d759336a99586170ec
- git.kernel.org /stable/c/d7083f41c21b30582e91b2e6de4d54dce74f6f9c
- git.kernel.org /stable/c/129032c0616d83a5e3e304f6ebf88f14ba01e5f7
- git.kernel.org /stable/c/ac200079db50af81e6b04d058b33ec92901d8edd
Sources
- CVE List CVE-2026-80795
- NVD CVE-2026-80795
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.