<?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://db.gcve.eu</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>Fri, 02 Oct 2026 06:59:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-52927 — netfilter: ebtables: fix OOB read in compat_mtw_from_user</title>
      <link>https://db.gcve.eu/vuln/cve-2026-52927</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;netfilter: ebtables: fix OOB read in compat_mtw_from_user&lt;/p&gt;
&lt;p&gt;Luxiao Xu says:&lt;/p&gt;
&lt;p&gt;The function compat_mtw_from_user() converts ebtables extensions from
 32-bit user structures to kernel native structures. However, it lacks
 proper validation of the user-supplied match_size/target_size.&lt;/p&gt;
&lt;p&gt;When certain extensions are processed, the kernel-side translation
 logic may perform memory accesses based on the extension&amp;#39;s expected
 size. If the user provides a size smaller than what the extension
 requires, it results in an out-of-bounds read as reported by KASAN.&lt;/p&gt;
&lt;p&gt;This fix introduces a check to ensure match_size is at least as large
 as the extension&amp;#39;s required compatsize. This covers matches, watchers,
 and targets, while maintaining compatibility with standard targets.&lt;/p&gt;
&lt;p&gt;AFAIU this is relevant for matches that need to go though
match-&amp;gt;compat_from_user() call.  Those that use plain memcpy with the
user-provided size are ok because the caller checks that size vs the
start of the next rule entry offset (which itself is checked vs. total
size copied from userspace).&lt;/p&gt;
&lt;p&gt;The -&amp;gt;compat_from_user() callbacks assume they can read compatsize bytes,
so they need this extra check.&lt;/p&gt;
&lt;p&gt;Based on an earlier patch from Luxiao Xu.&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;netfilter: ebtables: fix OOB read in compat_mtw_from_user&lt;/p&gt;
&lt;p&gt;Luxiao Xu says:&lt;/p&gt;
&lt;p&gt;The function compat_mtw_from_user() converts ebtables extensions from
 32-bit user structures to kernel native structures. However, it lacks
 proper validation of the user-supplied match_size/target_size.&lt;/p&gt;
&lt;p&gt;When certain extensions are processed, the kernel-side translation
 logic may perform memory accesses based on the extension&amp;#39;s expected
 size. If the user provides a size smaller than what the extension
 requires, it results in an out-of-bounds read as reported by KASAN.&lt;/p&gt;
&lt;p&gt;This fix introduces a check to ensure match_size is at least as large
 as the extension&amp;#39;s required compatsize. This covers matches, watchers,
 and targets, while maintaining compatibility with standard targets.&lt;/p&gt;
&lt;p&gt;AFAIU this is relevant for matches that need to go though
match-&amp;gt;compat_from_user() call.  Those that use plain memcpy with the
user-provided size are ok because the caller checks that size vs the
start of the next rule entry offset (which itself is checked vs. total
size copied from userspace).&lt;/p&gt;
&lt;p&gt;The -&amp;gt;compat_from_user() callbacks assume they can read compatsize bytes,
so they need this extra check.&lt;/p&gt;
&lt;p&gt;Based on an earlier patch from Luxiao Xu.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-52927</guid>
    </item>
  </channel>
</rss>
