<?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>Thu, 19 Nov 2026 17:35:07 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80725 — net: gro: properly validate BIG TCP aggregation criteria</title>
      <link>https://db.gcve.eu/vuln/cve-2026-80725</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: gro: properly validate BIG TCP aggregation criteria&lt;/p&gt;
&lt;p&gt;When GRO attempts to aggregate packets beyond GRO_LEGACY_MAX_SIZE (64KB),
BIG TCP should only be permitted for plain IPv4 TCP and plain IPv6 TCP
(with sufficient MAC header room to insert the temporary HBH jumbo header).&lt;/p&gt;
&lt;p&gt;However, commit b1a78b9b9886 (&amp;#34;net: add support for ipv4 big tcp&amp;#34;)
loosened the check in skb_gro_receive(), leading to several issues:&lt;/p&gt;
&lt;p&gt;1. skb_gro_receive() checked skb_headroom(p) instead of the actual space
   before the MAC header (p-&amp;gt;mac_header). Because skb_headroom(p) includes
   mac_len, crafted frames (e.g. injected via AF_PACKET) can pass the check
   with p-&amp;gt;mac_header &amp;lt; 8 bytes. When ipv6_gro_complete() inserts the
   temporary HBH jumbo header, the memmove() starts before skb-&amp;gt;head,
   causing an out-of-bounds write and wrapping skb-&amp;gt;mac_header.
2. It allowed non-IP protocols such as software VLAN (ETH_P_8021Q /
   ETH_P_8021AD) to aggregate beyond 64KB because
   p-&amp;gt;protocol != ETH_P_IPV6 was true.
3. It checked p-&amp;gt;encapsulation instead of NAPI_GRO_CB(skb)-&amp;gt;encap_mark,
   allowing encapsulated flows (e.g. SIT / IPv6-in-IPv4) to aggregate
   beyond 64KB.&lt;/p&gt;
&lt;p&gt;Fix skb_gro_receive() to strictly enforce:
- NAPI_GRO_CB(skb)-&amp;gt;proto == IPPROTO_TCP
- Not encapsulated (!NAPI_GRO_CB(skb)-&amp;gt;encap_mark &amp;amp;&amp;amp; !p-&amp;gt;encapsulation)
- Protocol must be either ETH_P_IP or ETH_P_IPV6
- If ETH_P_IPV6, p-&amp;gt;mac_header must be at least
  sizeof(struct h…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: gro: properly validate BIG TCP aggregation criteria&lt;/p&gt;
&lt;p&gt;When GRO attempts to aggregate packets beyond GRO_LEGACY_MAX_SIZE (64KB),
BIG TCP should only be permitted for plain IPv4 TCP and plain IPv6 TCP
(with sufficient MAC header room to insert the temporary HBH jumbo header).&lt;/p&gt;
&lt;p&gt;However, commit b1a78b9b9886 (&amp;#34;net: add support for ipv4 big tcp&amp;#34;)
loosened the check in skb_gro_receive(), leading to several issues:&lt;/p&gt;
&lt;p&gt;1. skb_gro_receive() checked skb_headroom(p) instead of the actual space
   before the MAC header (p-&amp;gt;mac_header). Because skb_headroom(p) includes
   mac_len, crafted frames (e.g. injected via AF_PACKET) can pass the check
   with p-&amp;gt;mac_header &amp;lt; 8 bytes. When ipv6_gro_complete() inserts the
   temporary HBH jumbo header, the memmove() starts before skb-&amp;gt;head,
   causing an out-of-bounds write and wrapping skb-&amp;gt;mac_header.
2. It allowed non-IP protocols such as software VLAN (ETH_P_8021Q /
   ETH_P_8021AD) to aggregate beyond 64KB because
   p-&amp;gt;protocol != ETH_P_IPV6 was true.
3. It checked p-&amp;gt;encapsulation instead of NAPI_GRO_CB(skb)-&amp;gt;encap_mark,
   allowing encapsulated flows (e.g. SIT / IPv6-in-IPv4) to aggregate
   beyond 64KB.&lt;/p&gt;
&lt;p&gt;Fix skb_gro_receive() to strictly enforce:
- NAPI_GRO_CB(skb)-&amp;gt;proto == IPPROTO_TCP
- Not encapsulated (!NAPI_GRO_CB(skb)-&amp;gt;encap_mark &amp;amp;&amp;amp; !p-&amp;gt;encapsulation)
- Protocol must be either ETH_P_IP or ETH_P_IPV6
- If ETH_P_IPV6, p-&amp;gt;mac_header must be at least
  sizeof(struct h…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-80725</guid>
    </item>
    <item>
      <title>USN-9002-1 — linux-nvidia-tegra vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-9002-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-nvidia-tegra&lt;/p&gt;
&lt;p&gt;It was discovered that the io_uring subsystem in the Linux kernel did not
properly handle canceled task work when processing certain wait operations,
leading to the operation being performed in the wrong task context. A local
attacker could possibly use this to cause a denial of service (system
crash). (CVE-2026-81010)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - ARM64 architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Intel NPU Driver;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Auxiliary display drivers;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - Character device driver;
  - CPU idle management framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - ARM SCMI message protocol;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - HSI subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - I3C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - On-Chip Interconnect management framework;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Fastrpc Driver;
  - Amazon Nitro Secure Module driver;
  - MMC subsystem;
  - MTD block device drivers;
  - Ethernet bonding…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-nvidia-tegra&lt;/p&gt;
&lt;p&gt;It was discovered that the io_uring subsystem in the Linux kernel did not
properly handle canceled task work when processing certain wait operations,
leading to the operation being performed in the wrong task context. A local
attacker could possibly use this to cause a denial of service (system
crash). (CVE-2026-81010)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - ARM64 architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Intel NPU Driver;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Auxiliary display drivers;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - Character device driver;
  - CPU idle management framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - ARM SCMI message protocol;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - HSI subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - I3C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - On-Chip Interconnect management framework;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Fastrpc Driver;
  - Amazon Nitro Secure Module driver;
  - MMC subsystem;
  - MTD block device drivers;
  - Ethernet bonding…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-9002-1</guid>
    </item>
  </channel>
</rss>
