VulnerabilityPublished 17 Sep 2026Updated 19 Oct 2026

CVE-2026-93174: Linux kernel · bpf: Copy per-CPU map value padding in copy_map_value_long()

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in ff3f22ed8d2f350b4c24ee26e33daea5f08d58ef : update Linux kernel when convenient.

Data as of 26 Oct 2026, 12:55 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in ff3f22ed8d2f350b4c24ee26e33daea5f08d58ef, 953e85da53541a8dc3e7ad4e8532f29a34a32eae, 7cf9cd98cf6f0df3befc167ca6b54c07014d71de +2

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 448325199f574d33824dbf9121efb03558412966, < ff3f22ed8d2f350b4c24ee26e33daea5f08d58ef	Fixed in ff3f22ed8d2f350b4c24ee26e33daea5f08d58ef
LinuxLinux	Affected ≥ 448325199f574d33824dbf9121efb03558412966, < 953e85da53541a8dc3e7ad4e8532f29a34a32eae	Fixed in 953e85da53541a8dc3e7ad4e8532f29a34a32eae
LinuxLinux	Affected ≥ 448325199f574d33824dbf9121efb03558412966, < 7cf9cd98cf6f0df3befc167ca6b54c07014d71de	Fixed in 7cf9cd98cf6f0df3befc167ca6b54c07014d71de
LinuxLinux	Affected ≥ 448325199f574d33824dbf9121efb03558412966, < 5e9f69829835521aa2942d1d14bd0990fbc6991e	Fixed in 5e9f69829835521aa2942d1d14bd0990fbc6991e
LinuxLinux	Affected ≥ 448325199f574d33824dbf9121efb03558412966, < 003bf840ed3326bd01396ce7d5b431cef0d371e7	Fixed in 003bf840ed3326bd01396ce7d5b431cef0d371e7
LinuxLinux	Affected =6.1	Fixed in–

Description

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.

References

Community reviews

Loading reviews…