<?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>Mon, 02 Nov 2026 20:22:35 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1375 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://db.gcve.eu/vuln/certfr-2026-avi-1375</link>
      <description>certfr-2026-avi-1375</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2026-avi-1375</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98600</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98600</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame()&lt;/p&gt;
&lt;p&gt;While rfcomm_recv_frame() verifies that skb-&amp;gt;len is at least
sizeof(*hdr) + 1 (4 bytes: 3-byte header + 1-byte FCS), an RFCOMM frame
with an extended 2-byte length field (!__test_ea(hdr-&amp;gt;len)) has a 4-byte
header plus a 1-byte FCS (5 bytes minimum, sizeof(*hdr) + 2).&lt;/p&gt;
&lt;p&gt;When a 4-byte RFCOMM frame with EA == 0 arrives:
1. The initial skb-&amp;gt;len &amp;lt; sizeof(*hdr) + 1 check passes (4 &amp;lt; 4 is false).
2. Trimming the FCS byte decrements skb-&amp;gt;len to 3.
3. If __check_fcs() succeeds, skb_pull(skb, 4) fails (4 &amp;gt; 3) and returns
   NULL without advancing skb-&amp;gt;data.
4. Because the return value of skb_pull() is ignored, the un-pulled
   3-byte struct rfcomm_hdr remains at skb-&amp;gt;data and is either queued as
   application payload via rfcomm_recv_data() or parsed as a multiplexer
   control command via rfcomm_recv_mcc() on DLCI 0.&lt;/p&gt;
&lt;p&gt;Fix this by extending the length check in rfcomm_recv_frame() to also
require skb-&amp;gt;len &amp;gt;= sizeof(*hdr) + 2 when !__test_ea(hdr-&amp;gt;len).&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;Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame()&lt;/p&gt;
&lt;p&gt;While rfcomm_recv_frame() verifies that skb-&amp;gt;len is at least
sizeof(*hdr) + 1 (4 bytes: 3-byte header + 1-byte FCS), an RFCOMM frame
with an extended 2-byte length field (!__test_ea(hdr-&amp;gt;len)) has a 4-byte
header plus a 1-byte FCS (5 bytes minimum, sizeof(*hdr) + 2).&lt;/p&gt;
&lt;p&gt;When a 4-byte RFCOMM frame with EA == 0 arrives:
1. The initial skb-&amp;gt;len &amp;lt; sizeof(*hdr) + 1 check passes (4 &amp;lt; 4 is false).
2. Trimming the FCS byte decrements skb-&amp;gt;len to 3.
3. If __check_fcs() succeeds, skb_pull(skb, 4) fails (4 &amp;gt; 3) and returns
   NULL without advancing skb-&amp;gt;data.
4. Because the return value of skb_pull() is ignored, the un-pulled
   3-byte struct rfcomm_hdr remains at skb-&amp;gt;data and is either queued as
   application payload via rfcomm_recv_data() or parsed as a multiplexer
   control command via rfcomm_recv_mcc() on DLCI 0.&lt;/p&gt;
&lt;p&gt;Fix this by extending the length check in rfcomm_recv_frame() to also
require skb-&amp;gt;len &amp;gt;= sizeof(*hdr) + 2 when !__test_ea(hdr-&amp;gt;len).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98600</guid>
    </item>
    <item>
      <title>GHSA-hpgr-cqmv-php2</title>
      <link>https://db.gcve.eu/vuln/ghsa-hpgr-cqmv-php2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame()&lt;/p&gt;
&lt;p&gt;While rfcomm_recv_frame() verifies that skb-&amp;gt;len is at least
sizeof(*hdr) + 1 (4 bytes: 3-byte header + 1-byte FCS), an RFCOMM frame
with an extended 2-byte length field (!__test_ea(hdr-&amp;gt;len)) has a 4-byte
header plus a 1-byte FCS (5 bytes minimum, sizeof(*hdr) + 2).&lt;/p&gt;
&lt;p&gt;When a 4-byte RFCOMM frame with EA == 0 arrives:
1. The initial skb-&amp;gt;len &amp;lt; sizeof(*hdr) + 1 check passes (4 &amp;lt; 4 is false).
2. Trimming the FCS byte decrements skb-&amp;gt;len to 3.
3. If __check_fcs() succeeds, skb_pull(skb, 4) fails (4 &amp;gt; 3) and returns
   NULL without advancing skb-&amp;gt;data.
4. Because the return value of skb_pull() is ignored, the un-pulled
   3-byte struct rfcomm_hdr remains at skb-&amp;gt;data and is either queued as
   application payload via rfcomm_recv_data() or parsed as a multiplexer
   control command via rfcomm_recv_mcc() on DLCI 0.&lt;/p&gt;
&lt;p&gt;Fix this by extending the length check in rfcomm_recv_frame() to also
require skb-&amp;gt;len &amp;gt;= sizeof(*hdr) + 2 when !__test_ea(hdr-&amp;gt;len).&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;Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame()&lt;/p&gt;
&lt;p&gt;While rfcomm_recv_frame() verifies that skb-&amp;gt;len is at least
sizeof(*hdr) + 1 (4 bytes: 3-byte header + 1-byte FCS), an RFCOMM frame
with an extended 2-byte length field (!__test_ea(hdr-&amp;gt;len)) has a 4-byte
header plus a 1-byte FCS (5 bytes minimum, sizeof(*hdr) + 2).&lt;/p&gt;
&lt;p&gt;When a 4-byte RFCOMM frame with EA == 0 arrives:
1. The initial skb-&amp;gt;len &amp;lt; sizeof(*hdr) + 1 check passes (4 &amp;lt; 4 is false).
2. Trimming the FCS byte decrements skb-&amp;gt;len to 3.
3. If __check_fcs() succeeds, skb_pull(skb, 4) fails (4 &amp;gt; 3) and returns
   NULL without advancing skb-&amp;gt;data.
4. Because the return value of skb_pull() is ignored, the un-pulled
   3-byte struct rfcomm_hdr remains at skb-&amp;gt;data and is either queued as
   application payload via rfcomm_recv_data() or parsed as a multiplexer
   control command via rfcomm_recv_mcc() on DLCI 0.&lt;/p&gt;
&lt;p&gt;Fix this by extending the length check in rfcomm_recv_frame() to also
require skb-&amp;gt;len &amp;gt;= sizeof(*hdr) + 2 when !__test_ea(hdr-&amp;gt;len).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-hpgr-cqmv-php2</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98600</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98600</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 96 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame() While rfcomm_recv_frame() verifies that skb-&amp;gt;len is at least sizeof(*hdr) + 1 (4 bytes: 3-byte header + 1-byte FCS), an RFCOMM frame with an extended 2-byte length field (!__test_ea(hdr-&amp;gt;len)) has a 4-byte header plus a 1-byte FCS (5 bytes minimum, sizeof(*hdr) + 2). When a 4-byte RFCOMM frame with EA == 0 arrives: 1. The initial skb-&amp;gt;len &amp;lt; sizeof(*hdr) + 1 check passes (4 &amp;lt; 4 is false). 2. Trimming the FCS byte decrements skb-&amp;gt;len to 3. 3. If __check_fcs() succeeds, skb_pull(skb, 4) fails (4 &amp;gt; 3) and returns    NULL without advancing skb-&amp;gt;data. 4. Because the return value of skb_pull() is ignored, the un-pulled    3-byte struct rfcomm_hdr remains at skb-&amp;gt;data and is either queued as    application payload via rfcomm_recv_data() or parsed as a multiplexer    control command via rfcomm_recv_mcc() on DLCI 0. Fix this by extending the length check in rfcomm_recv_frame() to also require skb-&amp;gt;len &amp;gt;= sizeof(*hdr) + 2 when !__test_ea(hdr-&amp;gt;len).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 96 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame() While rfcomm_recv_frame() verifies that skb-&amp;gt;len is at least sizeof(*hdr) + 1 (4 bytes: 3-byte header + 1-byte FCS), an RFCOMM frame with an extended 2-byte length field (!__test_ea(hdr-&amp;gt;len)) has a 4-byte header plus a 1-byte FCS (5 bytes minimum, sizeof(*hdr) + 2). When a 4-byte RFCOMM frame with EA == 0 arrives: 1. The initial skb-&amp;gt;len &amp;lt; sizeof(*hdr) + 1 check passes (4 &amp;lt; 4 is false). 2. Trimming the FCS byte decrements skb-&amp;gt;len to 3. 3. If __check_fcs() succeeds, skb_pull(skb, 4) fails (4 &amp;gt; 3) and returns    NULL without advancing skb-&amp;gt;data. 4. Because the return value of skb_pull() is ignored, the un-pulled    3-byte struct rfcomm_hdr remains at skb-&amp;gt;data and is either queued as    application payload via rfcomm_recv_data() or parsed as a multiplexer    control command via rfcomm_recv_mcc() on DLCI 0. Fix this by extending the length check in rfcomm_recv_frame() to also require skb-&amp;gt;len &amp;gt;= sizeof(*hdr) + 2 when !__test_ea(hdr-&amp;gt;len).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-98600</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4019 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4019</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-4019</guid>
    </item>
  </channel>
</rss>
