<?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 10:29:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-27414 — rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-27414</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;rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back&lt;/p&gt;
&lt;p&gt;In the commit d73ef2d69c0d (&amp;#34;rtnetlink: let rtnl_bridge_setlink checks
IFLA_BRIDGE_MODE length&amp;#34;), an adjustment was made to the old loop logic
in the function `rtnl_bridge_setlink` to enable the loop to also check
the length of the IFLA_BRIDGE_MODE attribute. However, this adjustment
removed the `break` statement and led to an error logic of the flags
writing back at the end of this function.&lt;/p&gt;
&lt;p&gt;if (have_flags)
    memcpy(nla_data(attr), &amp;amp;flags, sizeof(flags));
    // attr should point to IFLA_BRIDGE_FLAGS NLA !!!&lt;/p&gt;
&lt;p&gt;Before the mentioned commit, the `attr` is granted to be IFLA_BRIDGE_FLAGS.
However, this is not necessarily true fow now as the updated loop will let
the attr point to the last NLA, even an invalid NLA which could cause
overflow writes.&lt;/p&gt;
&lt;p&gt;This patch introduces a new variable `br_flag` to save the NLA pointer
that points to IFLA_BRIDGE_FLAGS and uses it to resolve the mentioned
error logic.&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;rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back&lt;/p&gt;
&lt;p&gt;In the commit d73ef2d69c0d (&amp;#34;rtnetlink: let rtnl_bridge_setlink checks
IFLA_BRIDGE_MODE length&amp;#34;), an adjustment was made to the old loop logic
in the function `rtnl_bridge_setlink` to enable the loop to also check
the length of the IFLA_BRIDGE_MODE attribute. However, this adjustment
removed the `break` statement and led to an error logic of the flags
writing back at the end of this function.&lt;/p&gt;
&lt;p&gt;if (have_flags)
    memcpy(nla_data(attr), &amp;amp;flags, sizeof(flags));
    // attr should point to IFLA_BRIDGE_FLAGS NLA !!!&lt;/p&gt;
&lt;p&gt;Before the mentioned commit, the `attr` is granted to be IFLA_BRIDGE_FLAGS.
However, this is not necessarily true fow now as the updated loop will let
the attr point to the last NLA, even an invalid NLA which could cause
overflow writes.&lt;/p&gt;
&lt;p&gt;This patch introduces a new variable `br_flag` to save the NLA pointer
that points to IFLA_BRIDGE_FLAGS and uses it to resolve the mentioned
error logic.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-27414</guid>
    </item>
  </channel>
</rss>
