<?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>Sat, 03 Oct 2026 11:15:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-39917 — bpf: Fix out-of-bounds dynptr write in bpf_crypto_crypt</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-39917</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: Fix out-of-bounds dynptr write in bpf_crypto_crypt&lt;/p&gt;
&lt;p&gt;Stanislav reported that in bpf_crypto_crypt() the destination dynptr&amp;#39;s
size is not validated to be at least as large as the source dynptr&amp;#39;s
size before calling into the crypto backend with &amp;#39;len = src_len&amp;#39;. This
can result in an OOB write when the destination is smaller than the
source.&lt;/p&gt;
&lt;p&gt;Concretely, in mentioned function, psrc and pdst are both linear
buffers fetched from each dynptr:&lt;/p&gt;
&lt;p&gt;psrc = __bpf_dynptr_data(src, src_len);
  [...]
  pdst = __bpf_dynptr_data_rw(dst, dst_len);
  [...]
  err = decrypt ?
        ctx-&amp;gt;type-&amp;gt;decrypt(ctx-&amp;gt;tfm, psrc, pdst, src_len, piv) :
        ctx-&amp;gt;type-&amp;gt;encrypt(ctx-&amp;gt;tfm, psrc, pdst, src_len, piv);&lt;/p&gt;
&lt;p&gt;The crypto backend expects pdst to be large enough with a src_len length
that can be written. Add an additional src_len &amp;gt; dst_len check and bail
out if it&amp;#39;s the case. Note that these kfuncs are accessible under root
privileges only.&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: Fix out-of-bounds dynptr write in bpf_crypto_crypt&lt;/p&gt;
&lt;p&gt;Stanislav reported that in bpf_crypto_crypt() the destination dynptr&amp;#39;s
size is not validated to be at least as large as the source dynptr&amp;#39;s
size before calling into the crypto backend with &amp;#39;len = src_len&amp;#39;. This
can result in an OOB write when the destination is smaller than the
source.&lt;/p&gt;
&lt;p&gt;Concretely, in mentioned function, psrc and pdst are both linear
buffers fetched from each dynptr:&lt;/p&gt;
&lt;p&gt;psrc = __bpf_dynptr_data(src, src_len);
  [...]
  pdst = __bpf_dynptr_data_rw(dst, dst_len);
  [...]
  err = decrypt ?
        ctx-&amp;gt;type-&amp;gt;decrypt(ctx-&amp;gt;tfm, psrc, pdst, src_len, piv) :
        ctx-&amp;gt;type-&amp;gt;encrypt(ctx-&amp;gt;tfm, psrc, pdst, src_len, piv);&lt;/p&gt;
&lt;p&gt;The crypto backend expects pdst to be large enough with a src_len length
that can be written. Add an additional src_len &amp;gt; dst_len check and bail
out if it&amp;#39;s the case. Note that these kfuncs are accessible under root
privileges only.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-39917</guid>
    </item>
  </channel>
</rss>
