<?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>Fri, 02 Oct 2026 14:43:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31502 — team: fix header_ops type confusion with non-Ethernet ports</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31502</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;team: fix header_ops type confusion with non-Ethernet ports&lt;/p&gt;
&lt;p&gt;Similar to commit 950803f72547 (&amp;#34;bonding: fix type confusion in
bond_setup_by_slave()&amp;#34;) team has the same class of header_ops type
confusion.&lt;/p&gt;
&lt;p&gt;For non-Ethernet ports, team_setup_by_port() copies port_dev-&amp;gt;header_ops
directly. When the team device later calls dev_hard_header() or
dev_parse_header(), these callbacks can run with the team net_device
instead of the real lower device, so netdev_priv(dev) is interpreted as
the wrong private type and can crash.&lt;/p&gt;
&lt;p&gt;The syzbot report shows a crash in bond_header_create(), but the root
cause is in team: the topology is gre -&amp;gt; bond -&amp;gt; team, and team calls
the inherited header_ops with its own net_device instead of the lower
device, so bond_header_create() receives a team device and interprets
netdev_priv() as bonding private data, causing a type confusion crash.&lt;/p&gt;
&lt;p&gt;Fix this by introducing team header_ops wrappers for create/parse,
selecting a team port under RCU, and calling the lower device callbacks
with port-&amp;gt;dev, so each callback always sees the correct net_device
context.&lt;/p&gt;
&lt;p&gt;Also pass the selected lower device to the lower parse callback, so
recursion is bounded in stacked non-Ethernet topologies and parse
callbacks always run with the correct device context.&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;team: fix header_ops type confusion with non-Ethernet ports&lt;/p&gt;
&lt;p&gt;Similar to commit 950803f72547 (&amp;#34;bonding: fix type confusion in
bond_setup_by_slave()&amp;#34;) team has the same class of header_ops type
confusion.&lt;/p&gt;
&lt;p&gt;For non-Ethernet ports, team_setup_by_port() copies port_dev-&amp;gt;header_ops
directly. When the team device later calls dev_hard_header() or
dev_parse_header(), these callbacks can run with the team net_device
instead of the real lower device, so netdev_priv(dev) is interpreted as
the wrong private type and can crash.&lt;/p&gt;
&lt;p&gt;The syzbot report shows a crash in bond_header_create(), but the root
cause is in team: the topology is gre -&amp;gt; bond -&amp;gt; team, and team calls
the inherited header_ops with its own net_device instead of the lower
device, so bond_header_create() receives a team device and interprets
netdev_priv() as bonding private data, causing a type confusion crash.&lt;/p&gt;
&lt;p&gt;Fix this by introducing team header_ops wrappers for create/parse,
selecting a team port under RCU, and calling the lower device callbacks
with port-&amp;gt;dev, so each callback always sees the correct net_device
context.&lt;/p&gt;
&lt;p&gt;Also pass the selected lower device to the lower parse callback, so
recursion is bounded in stacked non-Ethernet topologies and parse
callbacks always run with the correct device context.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31502</guid>
    </item>
  </channel>
</rss>
