CVE-2026-80865: bpf: Add missing access_ok call to copy_user_syms
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.16% (FIRST EPSS).
- Fixed version: Linux Linux 0b6252afcd1965f77c6a6f8a802a2e1381822b98, 128391b57e0977c35243672a6f970073651f3831, 28ce7bcf8a29aa395b60764df4c97be745de89d0.
Low priority for now. Upgrade to Linux Linux 0b6252afcd1965f77c6a6f8a802a2e1381822b98, 128391b57e0977c35243672a6f970073651f3831, 28ce7bcf8a29aa395b60764df4c97be745de89d0 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: bpf: Add missing access_ok call to copy_user_syms As reported by sashiko we use __get_user without prior access_ok call on the user space pointer. Adding the missing call for the whole pointer array. Plus removing the err check in the error path, because it's not needed and also we can return -ENOMEM directly from the first kvmalloc_array fail path. [1] https://lore.kernel.org/bpf/20260611115503.AC16D1F00893@smtp.kernel.org/
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- EPSS
- 0.1% · 5th 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.1%
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
- 5.19affected
- 0236fec57a15dc2a068dfe4488e0c2ab4559b1ec and later · before a67f7f9647cb243b3be32163e88e5bc76e3d51e9affected · git
- 0236fec57a15dc2a068dfe4488e0c2ab4559b1ec and later · before 8b719cef5ac30ab83ce5693c5faf10e4944874afaffected · git
- 0236fec57a15dc2a068dfe4488e0c2ab4559b1ec and later · before 128391b57e0977c35243672a6f970073651f3831affected · git
- 0236fec57a15dc2a068dfe4488e0c2ab4559b1ec and later · before 0b6252afcd1965f77c6a6f8a802a2e1381822b98affected · git
- 0236fec57a15dc2a068dfe4488e0c2ab4559b1ec and later · before 28ce7bcf8a29aa395b60764df4c97be745de89d0affected · git
- 0236fec57a15dc2a068dfe4488e0c2ab4559b1ec and later · before d5dc200c3a3f217de072af269dd90adddf90e48daffected · git
- before 5.19not affected · semver
- 6.1.178 and later · up to and including 6.1.*not affected · semver
- 6.6.145 and later · up to and including 6.6.*not affected · semver
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.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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-80785Sep 4, 2026 · fbdev: serialize mode sysfs access with lock_fb_info()0Monitor
- ← EarlierCVE-2026-80820Sep 4, 2026 · xfs: don't livelock in scrub on a circular unlinked list0Monitor
- Later →CVE-2026-80867Sep 4, 2026 · alpha/PCI: Add security_locked_down() check to pci_mmap_resource()0Monitor
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 | 0b6252afcd1965f77c6a6f8a802a2e1381822b98 | Vendor (CNA) |
| Linux Linux | 128391b57e0977c35243672a6f970073651f3831 | Vendor (CNA) |
| Linux Linux | 28ce7bcf8a29aa395b60764df4c97be745de89d0 | Vendor (CNA) |
| Linux Linux | 8b719cef5ac30ab83ce5693c5faf10e4944874af | Vendor (CNA) |
| Linux Linux | a67f7f9647cb243b3be32163e88e5bc76e3d51e9 | Vendor (CNA) |
| Linux Linux | d5dc200c3a3f217de072af269dd90adddf90e48d | Vendor (CNA) |
| debian:linux | 6.1.180-1 · 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 (5 more)Show less
- git.kernel.org/stable/c/128391b57e0977c35243672a6f970073651f3831
- git.kernel.org/stable/c/28ce7bcf8a29aa395b60764df4c97be745de89d0
- git.kernel.org/stable/c/8b719cef5ac30ab83ce5693c5faf10e4944874af
- git.kernel.org/stable/c/a67f7f9647cb243b3be32163e88e5bc76e3d51e9
- git.kernel.org/stable/c/d5dc200c3a3f217de072af269dd90adddf90e48d
Vendor advisories and official records. Exploit/PoC links are deliberately left out.