<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 08:51:24 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98955</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-98955</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://127.0.0.1:10001/vuln/bell-cve-2026-98955</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://127.0.0.1:10001/vuln/certfr-2026-avi-1537</link>
      <description>certfr-2026-avi-1537</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1537</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98955</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-98955</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 256 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: flow_dissector: avoid u16 truncation of skb-&amp;gt;len when computing thoff __skb_flow_dissect() computes key_control-&amp;gt;thoff using:   key_control-&amp;gt;thoff = min_t(u16, nhoff, skb ? skb-&amp;gt;len : hlen); min_t(u16, ...) casts both arguments to u16 before comparing them. Whenever skb-&amp;gt;len (or hlen) modulo 65536 is smaller than nhoff, the truncated length wins and thoff is set to a bogus small value, even when the dissection succeeded. For example, an IPv4/TCP frame with skb-&amp;gt;len == 65540 and nhoff == 34 gets thoff == 4, so callers such as skb_probe_transport_header() point the transport header inside the Ethernet header. Such skbs are not exotic: - At the time of commit d0c081b49137 (&amp;#34;flow_dissector: properly cap   thoff field&amp;#34;), AF_PACKET with PACKET_VNET_HDR could already build GSO   skbs larger than 64KB (MTU checks are skipped for GSO, and   alloc_skb_with_frags() accepted up to MAX_SKB_FRAGS (17) order-0   pages on top of the linear part). - BIG TCP now makes skbs larger than 64KB common. - The following patch makes tun_get_user() dissect IFF_TAP frames   before eth_type_trans() pulls the Ethernet header, so a GSO frame   carrying a 65522..65535 byte L3 packet will be dissected with   skb-&amp;gt;len in [65536, 65549]. Compare as u32 instead. If the resulting offset cannot be represented in the u16 key_control-&amp;gt;thoff, cap it to U16_MAX and report the dissection as failed rather than silently returning a wrong transport offs…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 256 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: flow_dissector: avoid u16 truncation of skb-&amp;gt;len when computing thoff __skb_flow_dissect() computes key_control-&amp;gt;thoff using:   key_control-&amp;gt;thoff = min_t(u16, nhoff, skb ? skb-&amp;gt;len : hlen); min_t(u16, ...) casts both arguments to u16 before comparing them. Whenever skb-&amp;gt;len (or hlen) modulo 65536 is smaller than nhoff, the truncated length wins and thoff is set to a bogus small value, even when the dissection succeeded. For example, an IPv4/TCP frame with skb-&amp;gt;len == 65540 and nhoff == 34 gets thoff == 4, so callers such as skb_probe_transport_header() point the transport header inside the Ethernet header. Such skbs are not exotic: - At the time of commit d0c081b49137 (&amp;#34;flow_dissector: properly cap   thoff field&amp;#34;), AF_PACKET with PACKET_VNET_HDR could already build GSO   skbs larger than 64KB (MTU checks are skipped for GSO, and   alloc_skb_with_frags() accepted up to MAX_SKB_FRAGS (17) order-0   pages on top of the linear part). - BIG TCP now makes skbs larger than 64KB common. - The following patch makes tun_get_user() dissect IFF_TAP frames   before eth_type_trans() pulls the Ethernet header, so a GSO frame   carrying a 65522..65535 byte L3 packet will be dissected with   skb-&amp;gt;len in [65536, 65549]. Compare as u32 instead. If the resulting offset cannot be represented in the u16 key_control-&amp;gt;thoff, cap it to U16_MAX and report the dissection as failed rather than silently returning a wrong transport offs…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-98955</guid>
    </item>
  </channel>
</rss>
