nfc: nci: fix out-of-bounds write in nci_target_auto_activated()
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.24% (FIRST EPSS).
- Fixed version: Linux Linux 0dc59de0075f88404a0f4a2b5233104ef459fbb2, 129032c0616d83a5e3e304f6ebf88f14ba01e5f7, 24761d3a5f692df5f7d848caeabcb2afd10917aa; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 0dc59de0075f88404a0f4a2b5233104ef459fbb2, 129032c0616d83a5e3e304f6ebf88f14ba01e5f7, 24761d3a5f692df5f7d848caeabcb2afd10917aa; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 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 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().
- Published
- Sep 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 14th 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.2%
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.4affected
- 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and later · before 0dc59de0075f88404a0f4a2b5233104ef459fbb2affected · git
- 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and later · before 94530ffabfca57e9bff1d207106010014cc84032affected · git
- 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and later · before afd8605fb43becb892311102844955c3b127fc7eaffected · git
- 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and later · before 24761d3a5f692df5f7d848caeabcb2afd10917aaaffected · git
- 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and later · before 50e87e1c0e18d791dcd7dccf30f9a2f3e2cf3951affected · git
- 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and later · before 2f08dbce3b37624ec6b424d759336a99586170ecaffected · git
- 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and later · before d7083f41c21b30582e91b2e6de4d54dce74f6f9caffected · git
- 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and later · before 129032c0616d83a5e3e304f6ebf88f14ba01e5f7affected · git
- 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 and later · before ac200079db50af81e6b04d058b33ec92901d8eddaffected · 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-80793Sep 4, 2026 · ipv4: reject undersized MTUs in ip_do_fragment()0Monitor
- ← EarlierCVE-2026-80794Sep 4, 2026 · nfc: nci: fix uninit-value in the RF discover/activated NTF handlers0Monitor
- Later →CVE-2026-80796Sep 4, 2026 · nfc: nci: add data_len bound checks to activation parameter extractors0Monitor
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 | 0dc59de0075f88404a0f4a2b5233104ef459fbb2 | Vendor (CNA) |
| Linux Linux | 129032c0616d83a5e3e304f6ebf88f14ba01e5f7 | Vendor (CNA) |
| Linux Linux | 24761d3a5f692df5f7d848caeabcb2afd10917aa | Vendor (CNA) |
| Linux Linux | 2f08dbce3b37624ec6b424d759336a99586170ec | Vendor (CNA) |
| Linux Linux | 50e87e1c0e18d791dcd7dccf30f9a2f3e2cf3951 | Vendor (CNA) |
| Linux Linux | 94530ffabfca57e9bff1d207106010014cc84032 | Vendor (CNA) |
| Linux Linux | ac200079db50af81e6b04d058b33ec92901d8edd | Vendor (CNA) |
| Linux Linux | afd8605fb43becb892311102844955c3b127fc7e | Vendor (CNA) |
| Linux Linux | d7083f41c21b30582e91b2e6de4d54dce74f6f9c | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | 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/129032c0616d83a5e3e304f6ebf88f14ba01e5f7
- git.kernel.org/stable/c/24761d3a5f692df5f7d848caeabcb2afd10917aa
- git.kernel.org/stable/c/2f08dbce3b37624ec6b424d759336a99586170ec
- git.kernel.org/stable/c/50e87e1c0e18d791dcd7dccf30f9a2f3e2cf3951
- git.kernel.org/stable/c/94530ffabfca57e9bff1d207106010014cc84032
- git.kernel.org/stable/c/ac200079db50af81e6b04d058b33ec92901d8edd
- git.kernel.org/stable/c/afd8605fb43becb892311102844955c3b127fc7e
- git.kernel.org/stable/c/d7083f41c21b30582e91b2e6de4d54dce74f6f9c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.