<?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:04:32 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99674</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99674</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: dev: can_dropped_invalid_skb: drop CAN XL frames on non-CAN XL devices&lt;/p&gt;
&lt;p&gt;Sending a PF_PACKET bypasses the CAN framework logic and can directly
reach a CAN driver&amp;#39;s xmit() function. The PF_PACKET framework only
checks that skb-&amp;gt;len does not exceed the net_device MTU.&lt;/p&gt;
&lt;p&gt;For a CAN device that is not CAN XL capable, anything above CANFD_MTU
(72 bytes) is therefore dropped before it reaches the driver. However,
CAN XL frames are variable length. can_is_canxl_skb() accepts lengths in
the range CANXL_HDR_SIZE + CANXL_MIN_DLEN up to CANXL_MTU, i.e. 13 to
2060 bytes.&lt;/p&gt;
&lt;p&gt;As a result, an ETH_P_CANXL skb with a length between 13 and 72 bytes
can pass both the MTU and the can_dropped_invalid_skb() checks.&lt;/p&gt;
&lt;p&gt;A driver that does not support CAN XL will interpret canxl_frame-&amp;gt;flags
as a length because of the overlap with can_frame-&amp;gt;len. And because
CANXL_XLF is set, the resulting length is between 128 and 255. For
drivers that do not check can_frame-&amp;gt;len before copying can_frame-&amp;gt;data,
as most drivers do, this results in a buffer overflow of up to 247
bytes.&lt;/p&gt;
&lt;p&gt;Drop ETH_P_CANXL skbs if the device does not have the CAN_CAP_XL
capability. Keep can_is_canxl_skb() for the validation of CAN XL skbs.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: dev: can_dropped_invalid_skb: drop CAN XL frames on non-CAN XL devices&lt;/p&gt;
&lt;p&gt;Sending a PF_PACKET bypasses the CAN framework logic and can directly
reach a CAN driver&amp;#39;s xmit() function. The PF_PACKET framework only
checks that skb-&amp;gt;len does not exceed the net_device MTU.&lt;/p&gt;
&lt;p&gt;For a CAN device that is not CAN XL capable, anything above CANFD_MTU
(72 bytes) is therefore dropped before it reaches the driver. However,
CAN XL frames are variable length. can_is_canxl_skb() accepts lengths in
the range CANXL_HDR_SIZE + CANXL_MIN_DLEN up to CANXL_MTU, i.e. 13 to
2060 bytes.&lt;/p&gt;
&lt;p&gt;As a result, an ETH_P_CANXL skb with a length between 13 and 72 bytes
can pass both the MTU and the can_dropped_invalid_skb() checks.&lt;/p&gt;
&lt;p&gt;A driver that does not support CAN XL will interpret canxl_frame-&amp;gt;flags
as a length because of the overlap with can_frame-&amp;gt;len. And because
CANXL_XLF is set, the resulting length is between 128 and 255. For
drivers that do not check can_frame-&amp;gt;len before copying can_frame-&amp;gt;data,
as most drivers do, this results in a buffer overflow of up to 247
bytes.&lt;/p&gt;
&lt;p&gt;Drop ETH_P_CANXL skbs if the device does not have the CAN_CAP_XL
capability. Keep can_is_canxl_skb() for the validation of CAN XL skbs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99674</guid>
    </item>
    <item>
      <title>GHSA-f6h3-jpxj-r8ww</title>
      <link>https://db.gcve.eu/vuln/ghsa-f6h3-jpxj-r8ww</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: dev: can_dropped_invalid_skb: drop CAN XL frames on non-CAN XL devices&lt;/p&gt;
&lt;p&gt;Sending a PF_PACKET bypasses the CAN framework logic and can directly
reach a CAN driver&amp;#39;s xmit() function. The PF_PACKET framework only
checks that skb-&amp;gt;len does not exceed the net_device MTU.&lt;/p&gt;
&lt;p&gt;For a CAN device that is not CAN XL capable, anything above CANFD_MTU
(72 bytes) is therefore dropped before it reaches the driver. However,
CAN XL frames are variable length. can_is_canxl_skb() accepts lengths in
the range CANXL_HDR_SIZE + CANXL_MIN_DLEN up to CANXL_MTU, i.e. 13 to
2060 bytes.&lt;/p&gt;
&lt;p&gt;As a result, an ETH_P_CANXL skb with a length between 13 and 72 bytes
can pass both the MTU and the can_dropped_invalid_skb() checks.&lt;/p&gt;
&lt;p&gt;A driver that does not support CAN XL will interpret canxl_frame-&amp;gt;flags
as a length because of the overlap with can_frame-&amp;gt;len. And because
CANXL_XLF is set, the resulting length is between 128 and 255. For
drivers that do not check can_frame-&amp;gt;len before copying can_frame-&amp;gt;data,
as most drivers do, this results in a buffer overflow of up to 247
bytes.&lt;/p&gt;
&lt;p&gt;Drop ETH_P_CANXL skbs if the device does not have the CAN_CAP_XL
capability. Keep can_is_canxl_skb() for the validation of CAN XL skbs.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: dev: can_dropped_invalid_skb: drop CAN XL frames on non-CAN XL devices&lt;/p&gt;
&lt;p&gt;Sending a PF_PACKET bypasses the CAN framework logic and can directly
reach a CAN driver&amp;#39;s xmit() function. The PF_PACKET framework only
checks that skb-&amp;gt;len does not exceed the net_device MTU.&lt;/p&gt;
&lt;p&gt;For a CAN device that is not CAN XL capable, anything above CANFD_MTU
(72 bytes) is therefore dropped before it reaches the driver. However,
CAN XL frames are variable length. can_is_canxl_skb() accepts lengths in
the range CANXL_HDR_SIZE + CANXL_MIN_DLEN up to CANXL_MTU, i.e. 13 to
2060 bytes.&lt;/p&gt;
&lt;p&gt;As a result, an ETH_P_CANXL skb with a length between 13 and 72 bytes
can pass both the MTU and the can_dropped_invalid_skb() checks.&lt;/p&gt;
&lt;p&gt;A driver that does not support CAN XL will interpret canxl_frame-&amp;gt;flags
as a length because of the overlap with can_frame-&amp;gt;len. And because
CANXL_XLF is set, the resulting length is between 128 and 255. For
drivers that do not check can_frame-&amp;gt;len before copying can_frame-&amp;gt;data,
as most drivers do, this results in a buffer overflow of up to 247
bytes.&lt;/p&gt;
&lt;p&gt;Drop ETH_P_CANXL skbs if the device does not have the CAN_CAP_XL
capability. Keep can_is_canxl_skb() for the validation of CAN XL skbs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-f6h3-jpxj-r8ww</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;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&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
