<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-20T21:03:46.374039+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-99673</id>
    <title>fkie_cve-2026-99673</title>
    <updated>2026-11-20T21:03:46.379963+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>can: replace ARPHRD_CAN type checks with can_get_ml_priv()</p>
<p>Commit 4e096a18867a ("net: introduce CAN specific pointer in the struct
net_device") introduced an explicit way to assign the midlayer private
pointer (dev-&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.</p>
<p>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-&gt;type == ARPHRD_CAN.</p>
<p>The TUNSETLINK ioctl allows a down TUN/TAP device to set its hardware
type to ARPHRD_CAN while dev-&gt;ml_priv remains NULL. Such a repurposed
netdevice passes the ARPHRD_CAN checks.</p>
<p>Commit 8aa59e355949 ("can: af_can: fix NULL pointer dereference in
can_rx_register()") already made can_rx_register() reject such devices.
But can_rx_unregister() still only checks dev-&gt;type and dereferences
the NULL ml_priv when it walks the receive lists of the device.</p>
<p>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.</p>
<p>Convert the remaining ARPHRD_CAN checks in af_c…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99673"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-3fc3-mxch-r9mj</id>
    <title>GHSA-3fc3-mxch-r9mj</title>
    <updated>2026-11-20T21:03:46.380082+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>can: replace ARPHRD_CAN type checks with can_get_ml_priv()</p>
<p>Commit 4e096a18867a ("net: introduce CAN specific pointer in the struct
net_device") introduced an explicit way to assign the midlayer private
pointer (dev-&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.</p>
<p>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-&gt;type == ARPHRD_CAN.</p>
<p>The TUNSETLINK ioctl allows a down TUN/TAP device to set its hardware
type to ARPHRD_CAN while dev-&gt;ml_priv remains NULL. Such a repurposed
netdevice passes the ARPHRD_CAN checks.</p>
<p>Commit 8aa59e355949 ("can: af_can: fix NULL pointer dereference in
can_rx_register()") already made can_rx_register() reject such devices.
But can_rx_unregister() still only checks dev-&gt;type and dereferences
the NULL ml_priv when it walks the receive lists of the device.</p>
<p>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.</p>
<p>Convert the remaining ARPHRD_CAN checks in af_c…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-3fc3-mxch-r9mj"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</id>
    <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
    <updated>2026-11-20T21:03:46.380140+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/wid-sec-w-2026-4695"/>
  </entry>
</feed>
