<?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, 20 Nov 2026 21:20:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99673 — can: replace ARPHRD_CAN type checks with can_get_ml_priv()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99673</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;can: replace ARPHRD_CAN type checks with can_get_ml_priv()&lt;/p&gt;
&lt;p&gt;Commit 4e096a18867a (&amp;#34;net: introduce CAN specific pointer in the struct
net_device&amp;#34;) introduced an explicit way to assign the midlayer private
pointer (dev-&amp;gt;ml_priv) to named users like ML_PRIV_CAN. A valid pointer
returned by can_get_ml_priv() therefore identifies a real CAN device.&lt;/p&gt;
&lt;p&gt;The referenced commit only converted the j1939 and proc code to this
check, while the other parts of the CAN subsystem still rely on
dev-&amp;gt;type == ARPHRD_CAN.&lt;/p&gt;
&lt;p&gt;The TUNSETLINK ioctl allows a down TUN/TAP device to set its hardware
type to ARPHRD_CAN while dev-&amp;gt;ml_priv remains NULL. Such a repurposed
netdevice passes the ARPHRD_CAN checks.&lt;/p&gt;
&lt;p&gt;Commit 8aa59e355949 (&amp;#34;can: af_can: fix NULL pointer dereference in
can_rx_register()&amp;#34;) already made can_rx_register() reject such devices.
But can_rx_unregister() still only checks dev-&amp;gt;type and dereferences
the NULL ml_priv when it walks the receive lists of the device.&lt;/p&gt;
&lt;p&gt;CAN_ISOTP reaches this path: isotp_bind() ignores the return values of
can_rx_register() and binds the socket anyway. When the socket is
released or the device is unregistered, isotp_release() and
isotp_notify() remove the filters that have never been registered and
trigger the NULL pointer dereference in can_rx_unregister(). This only
requires owning a TUN/TAP device or CAP_NET_ADMIN in an unprivileged
user namespace.&lt;/p&gt;
&lt;p&gt;Convert the remaining ARPHRD_CAN checks in af_c…&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;can: replace ARPHRD_CAN type checks with can_get_ml_priv()&lt;/p&gt;
&lt;p&gt;Commit 4e096a18867a (&amp;#34;net: introduce CAN specific pointer in the struct
net_device&amp;#34;) introduced an explicit way to assign the midlayer private
pointer (dev-&amp;gt;ml_priv) to named users like ML_PRIV_CAN. A valid pointer
returned by can_get_ml_priv() therefore identifies a real CAN device.&lt;/p&gt;
&lt;p&gt;The referenced commit only converted the j1939 and proc code to this
check, while the other parts of the CAN subsystem still rely on
dev-&amp;gt;type == ARPHRD_CAN.&lt;/p&gt;
&lt;p&gt;The TUNSETLINK ioctl allows a down TUN/TAP device to set its hardware
type to ARPHRD_CAN while dev-&amp;gt;ml_priv remains NULL. Such a repurposed
netdevice passes the ARPHRD_CAN checks.&lt;/p&gt;
&lt;p&gt;Commit 8aa59e355949 (&amp;#34;can: af_can: fix NULL pointer dereference in
can_rx_register()&amp;#34;) already made can_rx_register() reject such devices.
But can_rx_unregister() still only checks dev-&amp;gt;type and dereferences
the NULL ml_priv when it walks the receive lists of the device.&lt;/p&gt;
&lt;p&gt;CAN_ISOTP reaches this path: isotp_bind() ignores the return values of
can_rx_register() and binds the socket anyway. When the socket is
released or the device is unregistered, isotp_release() and
isotp_notify() remove the filters that have never been registered and
trigger the NULL pointer dereference in can_rx_unregister(). This only
requires owning a TUN/TAP device or CAP_NET_ADMIN in an unprivileged
user namespace.&lt;/p&gt;
&lt;p&gt;Convert the remaining ARPHRD_CAN checks in af_c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99673</guid>
    </item>
  </channel>
</rss>
