<?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://vulnerability.circl.lu</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, 06 Oct 2026 05:01:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68136 — net: gro: fix double aggregation of flush-marked skbs</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68136</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: fix double aggregation of flush-marked skbs&lt;/p&gt;
&lt;p&gt;Commit 0ab03f353d36 (&amp;#34;net-gro: Fix GRO flush when receiving a GSO
packet.&amp;#34;) added a flush check to skb_gro_receive(), but
skb_gro_receive_list() lacks the same validation.&lt;/p&gt;
&lt;p&gt;As a result, packets marked with NAPI_GRO_CB(skb)-&amp;gt;flush may still be
re-aggregated.&lt;/p&gt;
&lt;p&gt;This allows already-GRO&amp;#39;d packets with existing frag_list to be
re-aggregated into a new GRO session, corrupting the frag_list chain
structure. When skb_segment() attempts to unpack these malformed packets,
it encounters invalid state and triggers a kernel panic.&lt;/p&gt;
&lt;p&gt;Scenario (Tethering/Device forwarding):
  1. Driver: Generated aggregated packet P1 via LRO with frag_list
  2. Dev A: Receives aggregated fraglist packet and flush flag set
  3. Dev A: Re-enters GRO, skb_gro_receive_list() is called
  4. Missing flush check allows re-aggregation despite flush flag
  5. Frag_list chain becomes corrupted (loops or dangling refs)
  6. Dev B: TX path calls skb_segment(), crashes on corrupted frag_list&lt;/p&gt;
&lt;p&gt;Root cause in skb_segment():
  The check at line ~4891:
    if (hsize &amp;lt;= 0 &amp;amp;&amp;amp; i &amp;gt;= nfrags &amp;amp;&amp;amp; skb_headlen(list_skb) &amp;amp;&amp;amp;
        (skb_headlen(list_skb) == len || sg)) {&lt;/p&gt;
&lt;p&gt;When frag_list is corrupted by double aggregation, when list_skb is
  a NULL pointer from skb-&amp;gt;next, skb_headlen(list_skb) dereference
  NULL/corrupted pointers occurs.&lt;/p&gt;
&lt;p&gt;Call Trace:
 skb_headlen(NULL skb)
 skb_segment
 tcp_gso_segment
 tcp4_gso_…&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: fix double aggregation of flush-marked skbs&lt;/p&gt;
&lt;p&gt;Commit 0ab03f353d36 (&amp;#34;net-gro: Fix GRO flush when receiving a GSO
packet.&amp;#34;) added a flush check to skb_gro_receive(), but
skb_gro_receive_list() lacks the same validation.&lt;/p&gt;
&lt;p&gt;As a result, packets marked with NAPI_GRO_CB(skb)-&amp;gt;flush may still be
re-aggregated.&lt;/p&gt;
&lt;p&gt;This allows already-GRO&amp;#39;d packets with existing frag_list to be
re-aggregated into a new GRO session, corrupting the frag_list chain
structure. When skb_segment() attempts to unpack these malformed packets,
it encounters invalid state and triggers a kernel panic.&lt;/p&gt;
&lt;p&gt;Scenario (Tethering/Device forwarding):
  1. Driver: Generated aggregated packet P1 via LRO with frag_list
  2. Dev A: Receives aggregated fraglist packet and flush flag set
  3. Dev A: Re-enters GRO, skb_gro_receive_list() is called
  4. Missing flush check allows re-aggregation despite flush flag
  5. Frag_list chain becomes corrupted (loops or dangling refs)
  6. Dev B: TX path calls skb_segment(), crashes on corrupted frag_list&lt;/p&gt;
&lt;p&gt;Root cause in skb_segment():
  The check at line ~4891:
    if (hsize &amp;lt;= 0 &amp;amp;&amp;amp; i &amp;gt;= nfrags &amp;amp;&amp;amp; skb_headlen(list_skb) &amp;amp;&amp;amp;
        (skb_headlen(list_skb) == len || sg)) {&lt;/p&gt;
&lt;p&gt;When frag_list is corrupted by double aggregation, when list_skb is
  a NULL pointer from skb-&amp;gt;next, skb_headlen(list_skb) dereference
  NULL/corrupted pointers occurs.&lt;/p&gt;
&lt;p&gt;Call Trace:
 skb_headlen(NULL skb)
 skb_segment
 tcp_gso_segment
 tcp4_gso_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68136</guid>
    </item>
    <item>
      <title>USN-8781-1 — linux-nvidia-tegra vulnerabilities</title>
      <link>https://vulnerability.circl.lu/vuln/usn-8781-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 some Arm processors could complete a broadcast
translation lookaside buffer (TLB) invalidation before memory writes made
through the invalidated translation were globally observed. A local
attacker could possibly use this to write to memory after permission to do
so had been revoked, bypassing memory protections or escalating privileges.
(CVE-2025-10263)&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:
  - ARM64 architecture;
  - User-space API (UAPI);
  - Kernel build system;
  - ARM32 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Cryptographic API;
  - Intel NPU Driver;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - DRBD Distributed Replicated Block Device drivers;
  - Rados block device (RBD) driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - EFI core;
  - FPGA Framework;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - I3C subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media…&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 some Arm processors could complete a broadcast
translation lookaside buffer (TLB) invalidation before memory writes made
through the invalidated translation were globally observed. A local
attacker could possibly use this to write to memory after permission to do
so had been revoked, bypassing memory protections or escalating privileges.
(CVE-2025-10263)&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:
  - ARM64 architecture;
  - User-space API (UAPI);
  - Kernel build system;
  - ARM32 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Cryptographic API;
  - Intel NPU Driver;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - DRBD Distributed Replicated Block Device drivers;
  - Rados block device (RBD) driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - EFI core;
  - FPGA Framework;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - I3C subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/usn-8781-1</guid>
    </item>
  </channel>
</rss>
