<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 03:15:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93174 — bpf: Copy per-CPU map value padding in copy_map_value_long()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-93174</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Copy per-CPU map value padding in copy_map_value_long()&lt;/p&gt;
&lt;p&gt;In kernel, per-CPU map elements are stored with
round_up(map-&amp;gt;value_size, 8) bytes. On UAPI lookup paths, it copies the
rounded size for each CPU into a temporary buffer.&lt;/p&gt;
&lt;p&gt;However, copy_map_value_long() passes &amp;#39;map-&amp;gt;value_size&amp;#39; 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 &amp;#39;map-&amp;gt;value_size&amp;#39; and round_up(map-&amp;gt;value_size, 8).&lt;/p&gt;
&lt;p&gt;The temporary UAPI lookup buffers are allocated without __GFP_ZERO. As a
result, when the per-CPU map&amp;#39;s value size is not equal to
round_up(map-&amp;gt;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.&lt;/p&gt;
&lt;p&gt;Pass round_up(map-&amp;gt;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()&amp;#39;s long_memcpy path.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Copy per-CPU map value padding in copy_map_value_long()&lt;/p&gt;
&lt;p&gt;In kernel, per-CPU map elements are stored with
round_up(map-&amp;gt;value_size, 8) bytes. On UAPI lookup paths, it copies the
rounded size for each CPU into a temporary buffer.&lt;/p&gt;
&lt;p&gt;However, copy_map_value_long() passes &amp;#39;map-&amp;gt;value_size&amp;#39; 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 &amp;#39;map-&amp;gt;value_size&amp;#39; and round_up(map-&amp;gt;value_size, 8).&lt;/p&gt;
&lt;p&gt;The temporary UAPI lookup buffers are allocated without __GFP_ZERO. As a
result, when the per-CPU map&amp;#39;s value size is not equal to
round_up(map-&amp;gt;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.&lt;/p&gt;
&lt;p&gt;Pass round_up(map-&amp;gt;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()&amp;#39;s long_memcpy path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-93174</guid>
    </item>
  </channel>
</rss>
