<?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>Wed, 30 Sep 2026 17:32:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93125 — bpf: Reject rdonly/rdwr_buf_size kfunc arguments that exceed u32 max</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-93125</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: Reject rdonly/rdwr_buf_size kfunc arguments that exceed u32 max&lt;/p&gt;
&lt;p&gt;check_kfunc_args() detects a kfunc argument named rdonly_buf_size or
rdwr_buf_size and stores reg-&amp;gt;var_off.value into meta-&amp;gt;r0_size, a u64,
and does not bound it. check_kfunc_call() later copies that value into
the returned register&amp;#39;s mem_size field:&lt;/p&gt;
&lt;p&gt;meta-&amp;gt;r0_size = reg-&amp;gt;var_off.value;
  ...
  regs[BPF_REG_0].mem_size = meta.r0_size;&lt;/p&gt;
&lt;p&gt;regs[BPF_REG_0].mem_size is u32. A constant whose upper 32 bits are set
gets truncated instead of causing a load-time rejection, so the verifier
records a PTR_TO_MEM register with an approximately 4 GiB mem_size for
whatever allocation the kfunc returned. A later access check against
that register uses the truncated, wrong bound.&lt;/p&gt;
&lt;p&gt;Reject rdonly_buf_size/rdwr_buf_size values that exceed U32_MAX at the
point meta-&amp;gt;r0_size is set.&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: Reject rdonly/rdwr_buf_size kfunc arguments that exceed u32 max&lt;/p&gt;
&lt;p&gt;check_kfunc_args() detects a kfunc argument named rdonly_buf_size or
rdwr_buf_size and stores reg-&amp;gt;var_off.value into meta-&amp;gt;r0_size, a u64,
and does not bound it. check_kfunc_call() later copies that value into
the returned register&amp;#39;s mem_size field:&lt;/p&gt;
&lt;p&gt;meta-&amp;gt;r0_size = reg-&amp;gt;var_off.value;
  ...
  regs[BPF_REG_0].mem_size = meta.r0_size;&lt;/p&gt;
&lt;p&gt;regs[BPF_REG_0].mem_size is u32. A constant whose upper 32 bits are set
gets truncated instead of causing a load-time rejection, so the verifier
records a PTR_TO_MEM register with an approximately 4 GiB mem_size for
whatever allocation the kfunc returned. A later access check against
that register uses the truncated, wrong bound.&lt;/p&gt;
&lt;p&gt;Reject rdonly_buf_size/rdwr_buf_size values that exceed U32_MAX at the
point meta-&amp;gt;r0_size is set.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-93125</guid>
    </item>
  </channel>
</rss>
