Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 43 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 448325199f574d33824dbf9121efb03558412966 – < e0653c8f718109d140e806daac166c43e2b2b8bd
    • affected 448325199f574d33824dbf9121efb03558412966 – < 953e85da53541a8dc3e7ad4e8532f29a34a32eae
    • affected 448325199f574d33824dbf9121efb03558412966 – < 003bf840ed3326bd01396ce7d5b431cef0d371e7
    • affected 448325199f574d33824dbf9121efb03558412966 – < 5e9f69829835521aa2942d1d14bd0990fbc6991e
    • affected 448325199f574d33824dbf9121efb03558412966 – < ff3f22ed8d2f350b4c24ee26e33daea5f08d58ef
    • affected 448325199f574d33824dbf9121efb03558412966 – < 7cf9cd98cf6f0df3befc167ca6b54c07014d71de
  • Linux · Linux

    • affected 6.1
    • unaffected < 6.1
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93174 badge
[![CVE-2026-93174](https://cveledger.app/badge/CVE-2026-93174.svg)](https://cveledger.app/cve/CVE-2026-93174)

Record last updated .