<?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://cve.radiocsirt.org</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>Tue, 17 Nov 2026 10:09:22 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98950</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98950</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-98950</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1537 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</link>
      <description>certfr-2026-avi-1537</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</guid>
    </item>
    <item>
      <title>EUVD-2026-396102</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396102</link>
      <description>EUVD-2026-396102</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396102</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98950</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98950</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()&lt;/p&gt;
&lt;p&gt;bpf_flow_dissect() sanitizes the offsets returned by the BPF program
with clamp_t(u16, ..., hlen).&lt;/p&gt;
&lt;p&gt;If hlen is bigger than 65535, the upper bound is truncated before
the comparison. For instance, with hlen == 65536, both nhoff and
thoff are forced to zero, even if the program returned sane values.&lt;/p&gt;
&lt;p&gt;This is the same class of bug as the one fixed in commit 99bda1ecbd56
(&amp;#34;flow_dissector: avoid u16 truncation of skb-&amp;gt;len when computing
thoff&amp;#34;). That fix does not cover the BPF path, because
__skb_flow_dissect() returns early when a BPF flow dissector
handles the packet.&lt;/p&gt;
&lt;p&gt;struct bpf_flow_keys stores nhoff and thoff as u16, so cap hlen
to U16_MAX before clamping.&lt;/p&gt;
&lt;p&gt;Found by sashiko while reviewing the commit above.&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;flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()&lt;/p&gt;
&lt;p&gt;bpf_flow_dissect() sanitizes the offsets returned by the BPF program
with clamp_t(u16, ..., hlen).&lt;/p&gt;
&lt;p&gt;If hlen is bigger than 65535, the upper bound is truncated before
the comparison. For instance, with hlen == 65536, both nhoff and
thoff are forced to zero, even if the program returned sane values.&lt;/p&gt;
&lt;p&gt;This is the same class of bug as the one fixed in commit 99bda1ecbd56
(&amp;#34;flow_dissector: avoid u16 truncation of skb-&amp;gt;len when computing
thoff&amp;#34;). That fix does not cover the BPF path, because
__skb_flow_dissect() returns early when a BPF flow dissector
handles the packet.&lt;/p&gt;
&lt;p&gt;struct bpf_flow_keys stores nhoff and thoff as u16, so cap hlen
to U16_MAX before clamping.&lt;/p&gt;
&lt;p&gt;Found by sashiko while reviewing the commit above.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98950</guid>
    </item>
    <item>
      <title>GHSA-4jwg-g8h6-9gv7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4jwg-g8h6-9gv7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()&lt;/p&gt;
&lt;p&gt;bpf_flow_dissect() sanitizes the offsets returned by the BPF program
with clamp_t(u16, ..., hlen).&lt;/p&gt;
&lt;p&gt;If hlen is bigger than 65535, the upper bound is truncated before
the comparison. For instance, with hlen == 65536, both nhoff and
thoff are forced to zero, even if the program returned sane values.&lt;/p&gt;
&lt;p&gt;This is the same class of bug as the one fixed in commit 99bda1ecbd56
(&amp;#34;flow_dissector: avoid u16 truncation of skb-&amp;gt;len when computing
thoff&amp;#34;). That fix does not cover the BPF path, because
__skb_flow_dissect() returns early when a BPF flow dissector
handles the packet.&lt;/p&gt;
&lt;p&gt;struct bpf_flow_keys stores nhoff and thoff as u16, so cap hlen
to U16_MAX before clamping.&lt;/p&gt;
&lt;p&gt;Found by sashiko while reviewing the commit above.&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;flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()&lt;/p&gt;
&lt;p&gt;bpf_flow_dissect() sanitizes the offsets returned by the BPF program
with clamp_t(u16, ..., hlen).&lt;/p&gt;
&lt;p&gt;If hlen is bigger than 65535, the upper bound is truncated before
the comparison. For instance, with hlen == 65536, both nhoff and
thoff are forced to zero, even if the program returned sane values.&lt;/p&gt;
&lt;p&gt;This is the same class of bug as the one fixed in commit 99bda1ecbd56
(&amp;#34;flow_dissector: avoid u16 truncation of skb-&amp;gt;len when computing
thoff&amp;#34;). That fix does not cover the BPF path, because
__skb_flow_dissect() returns early when a BPF flow dissector
handles the packet.&lt;/p&gt;
&lt;p&gt;struct bpf_flow_keys stores nhoff and thoff as u16, so cap hlen
to U16_MAX before clamping.&lt;/p&gt;
&lt;p&gt;Found by sashiko while reviewing the commit above.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4jwg-g8h6-9gv7</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98950 — flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98950</link>
      <description>msrc_CVE-2026-98950</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-98950</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98950</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98950</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 229 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect() bpf_flow_dissect() sanitizes the offsets returned by the BPF program with clamp_t(u16, ..., hlen). If hlen is bigger than 65535, the upper bound is truncated before the comparison. For instance, with hlen == 65536, both nhoff and thoff are forced to zero, even if the program returned sane values. This is the same class of bug as the one fixed in commit 99bda1ecbd56 (&amp;#34;flow_dissector: avoid u16 truncation of skb-&amp;gt;len when computing thoff&amp;#34;). That fix does not cover the BPF path, because __skb_flow_dissect() returns early when a BPF flow dissector handles the packet. struct bpf_flow_keys stores nhoff and thoff as u16, so cap hlen to U16_MAX before clamping. Found by sashiko while reviewing the commit above.&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 229 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect() bpf_flow_dissect() sanitizes the offsets returned by the BPF program with clamp_t(u16, ..., hlen). If hlen is bigger than 65535, the upper bound is truncated before the comparison. For instance, with hlen == 65536, both nhoff and thoff are forced to zero, even if the program returned sane values. This is the same class of bug as the one fixed in commit 99bda1ecbd56 (&amp;#34;flow_dissector: avoid u16 truncation of skb-&amp;gt;len when computing thoff&amp;#34;). That fix does not cover the BPF path, because __skb_flow_dissect() returns early when a BPF flow dissector handles the packet. struct bpf_flow_keys stores nhoff and thoff as u16, so cap hlen to U16_MAX before clamping. Found by sashiko while reviewing the commit above.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98950</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</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://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
