CVE-2026-93174
Last modified
CVE-2026-93174 is a vulnerability of currently unknown severity. 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().
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 448325199f574d33824dbf9121efb03558412966, < 953e85da53541a8dc3e7ad4e8532f29a34a32eae; >= 448325199f574d33824dbf9121efb03558412966, < 003bf840ed3326bd01396ce7d5b431cef0d371e7; >= 448325199f574d33824dbf9121efb03558412966, < 5e9f69829835521aa2942d1d14bd0990fbc6991e; >= 448325199f574d33824dbf9121efb03558412966, < ff3f22ed8d2f350b4c24ee26e33daea5f08d58ef; >= 448325199f574d33824dbf9121efb03558412966, < 7cf9cd98cf6f0df3befc167ca6b54c07014d71de |
| Linux | Linux | 6.1 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-93174?
How severe is CVE-2026-93174?
How do I fix CVE-2026-93174?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-93169In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9317Nango before 0.71.6 contains a missing authentication vulner…8.1
- CVE-2026-93170In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-93171In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93172In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93173In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93175In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-93176In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-93177In the Linux kernel, the following vulnerability has been re…7.3
- CVE-2026-93178In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-93179In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9318tablib prior to 3.10.0 contains a stored cross-site scriptin…5.4
Are you affected by CVE-2026-93174?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
