CVE-2026-93174: bpf: Copy per-CPU map value padding in copy_map_value_long()
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.17% (FIRST EPSS).
- Fixed version: Linux Linux 003bf840ed3326bd01396ce7d5b431cef0d371e7, 5e9f69829835521aa2942d1d14bd0990fbc6991e, 7cf9cd98cf6f0df3befc167ca6b54c07014d71de.
Low priority for now. Upgrade to Linux Linux 003bf840ed3326bd01396ce7d5b431cef0d371e7, 5e9f69829835521aa2942d1d14bd0990fbc6991e, 7cf9cd98cf6f0df3befc167ca6b54c07014d71de 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: Copy per-CPU map value padding in copy_map_value_long() In kernel, per-CPU map elements are stored with round_up(map->value_size, 8) bytes. On UAPI lookup paths, it copies the rounded size for each CPU into a temporary buffer. However, copy_map_value_long() passes 'map->value_size' to bpf_obj_memcpy(). When the map has special fields, bpf_obj_memcpy() copies around those fields with memcpy(), and does not copy the tail padding between 'map->value_size' and round_up(map->value_size, 8). The temporary UAPI lookup buffers are allocated without __GFP_ZERO. As a result, when the per-CPU map's value size is not equal to round_up(map->value_size, 8), UAPI LOOKUP_ELEM and its variants can return stale heap contents from that padding to user space. The same issue applies to bpf_iter for per-CPU maps. Pass round_up(map->value_size, 8) to bpf_obj_memcpy() from copy_map_value_long(), so per-CPU maps both with and without special fields copy the entire per-CPU slot. Remove the now redundant round_up() from bpf_obj_memcpy()'s long_memcpy path.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 6th 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
- 6.1affected
- 448325199f574d33824dbf9121efb03558412966 and later · before e0653c8f718109d140e806daac166c43e2b2b8bdaffected · git
- 448325199f574d33824dbf9121efb03558412966 and later · before 953e85da53541a8dc3e7ad4e8532f29a34a32eaeaffected · git
- 448325199f574d33824dbf9121efb03558412966 and later · before 003bf840ed3326bd01396ce7d5b431cef0d371e7affected · git
- 448325199f574d33824dbf9121efb03558412966 and later · before 5e9f69829835521aa2942d1d14bd0990fbc6991eaffected · git
- 448325199f574d33824dbf9121efb03558412966 and later · before ff3f22ed8d2f350b4c24ee26e33daea5f08d58efaffected · git
- 448325199f574d33824dbf9121efb03558412966 and later · before 7cf9cd98cf6f0df3befc167ca6b54c07014d71deaffected · git
- before 6.1not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.157 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 | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-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-93172Sep 17, 2026 · mm/mm_init: handle alloc_percpu failure in free_area_init_core_hotplug0Monitor
- ← EarlierCVE-2026-93173Sep 17, 2026 · bpf,lsm: Drop bpf_prog_free from sleepable_lsm_hooks0Monitor
- Later →CVE-2026-93175Sep 17, 2026 · drm/amd/display: Fix dangling pointer in CRTC reset function31Monitor
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 | 003bf840ed3326bd01396ce7d5b431cef0d371e7 | Vendor (CNA) |
| Linux Linux | 5e9f69829835521aa2942d1d14bd0990fbc6991e | Vendor (CNA) |
| Linux Linux | 7cf9cd98cf6f0df3befc167ca6b54c07014d71de | Vendor (CNA) |
| Linux Linux | 953e85da53541a8dc3e7ad4e8532f29a34a32eae | Vendor (CNA) |
| Linux Linux | e0653c8f718109d140e806daac166c43e2b2b8bd | Vendor (CNA) |
| Linux Linux | ff3f22ed8d2f350b4c24ee26e33daea5f08d58ef | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-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 (5 more)Show less
- git.kernel.org/stable/c/5e9f69829835521aa2942d1d14bd0990fbc6991e
- git.kernel.org/stable/c/7cf9cd98cf6f0df3befc167ca6b54c07014d71de
- git.kernel.org/stable/c/953e85da53541a8dc3e7ad4e8532f29a34a32eae
- git.kernel.org/stable/c/e0653c8f718109d140e806daac166c43e2b2b8bd
- git.kernel.org/stable/c/ff3f22ed8d2f350b4c24ee26e33daea5f08d58ef
Vendor advisories and official records. Exploit/PoC links are deliberately left out.