<?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:53:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74714 — bpf: tcp: Fix use-after-free in bpf_iter_tcp_established_batch()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-74714</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;bpf: tcp: Fix use-after-free in bpf_iter_tcp_established_batch()&lt;/p&gt;
&lt;p&gt;reqsk_queue_hash_req() publishes a TCP_NEW_SYN_RECV request_sock onto
the ehash chain, drops the bucket lock, and only afterwards sets
rsk_refcnt to 3.&lt;/p&gt;
&lt;p&gt;Lockless readers such as __inet_lookup_established() handle this with
refcount_inc_not_zero(), but bpf_iter_tcp_established_batch() uses plain
sock_hold() while holding the bucket lock, on the assumption that the
lock guarantees sk_refcnt &amp;gt; 0. That assumption does not hold for
request_sock:&lt;/p&gt;
&lt;p&gt;CPU 0                                CPU 1
  -----                                -----
  tcp_conn_request()
   reqsk_queue_hash_req()
    inet_ehash_insert(req)
     spin_lock(bucket)
     __sk_nulls_add_node_rcu(req)      // rsk_refcnt == 0
     spin_unlock(bucket)
                                       bpf_iter_tcp_established_batch()
                                        spin_lock(bucket)
                                        sock_hold(req)   &amp;lt;-- addition on 0
                                        spin_unlock(bucket)
    refcount_set(&amp;amp;req-&amp;gt;rsk_refcnt, 3)  // clobbers saturated value&lt;/p&gt;
&lt;p&gt;which surfaces as:&lt;/p&gt;
&lt;p&gt;refcount_t: addition on 0; use-after-free.
  WARNING: lib/refcount.c:25 at refcount_warn_saturate+0x48/0x90, CPU#1
  Call Trace:
   bpf_iter_tcp_established_batch+0x14e/0x170
   bpf_iter_tcp_batch+0x53/0x200
   bpf_iter_tcp_seq_next+0x27/0x70
   bpf_seq_read+0x107/0x410
   vfs_read+0xb9/0x380…&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;bpf: tcp: Fix use-after-free in bpf_iter_tcp_established_batch()&lt;/p&gt;
&lt;p&gt;reqsk_queue_hash_req() publishes a TCP_NEW_SYN_RECV request_sock onto
the ehash chain, drops the bucket lock, and only afterwards sets
rsk_refcnt to 3.&lt;/p&gt;
&lt;p&gt;Lockless readers such as __inet_lookup_established() handle this with
refcount_inc_not_zero(), but bpf_iter_tcp_established_batch() uses plain
sock_hold() while holding the bucket lock, on the assumption that the
lock guarantees sk_refcnt &amp;gt; 0. That assumption does not hold for
request_sock:&lt;/p&gt;
&lt;p&gt;CPU 0                                CPU 1
  -----                                -----
  tcp_conn_request()
   reqsk_queue_hash_req()
    inet_ehash_insert(req)
     spin_lock(bucket)
     __sk_nulls_add_node_rcu(req)      // rsk_refcnt == 0
     spin_unlock(bucket)
                                       bpf_iter_tcp_established_batch()
                                        spin_lock(bucket)
                                        sock_hold(req)   &amp;lt;-- addition on 0
                                        spin_unlock(bucket)
    refcount_set(&amp;amp;req-&amp;gt;rsk_refcnt, 3)  // clobbers saturated value&lt;/p&gt;
&lt;p&gt;which surfaces as:&lt;/p&gt;
&lt;p&gt;refcount_t: addition on 0; use-after-free.
  WARNING: lib/refcount.c:25 at refcount_warn_saturate+0x48/0x90, CPU#1
  Call Trace:
   bpf_iter_tcp_established_batch+0x14e/0x170
   bpf_iter_tcp_batch+0x53/0x200
   bpf_iter_tcp_seq_next+0x27/0x70
   bpf_seq_read+0x107/0x410
   vfs_read+0xb9/0x380…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-74714</guid>
    </item>
    <item>
      <title>USN-8886-1 — linux-nvidia-tegra vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8886-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;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:
  - NVDIMM (Non-Volatile Memory Device) drivers;
  - Handshake API;
  - ARM32 architecture;
  - ARM64 architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Intel NPU Driver;
  - Android drivers;
  - Rados block device (RBD) driver;
  - Bluetooth drivers;
  - Hardware random number generator core;
  - TPM device driver;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - DMA engine subsystem;
  - FireWire subsystem;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - CoreSight HW tracing drivers;
  - I2C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Multifunction device drivers;
  - Fastrpc Driver;
  - Amazon Nitro Secure Module driver;
  - MMC subsystem;
  - MTD block device drivers;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - Texas Instruments network drivers;
  - NTB driver;
  - NVME drivers;
  - NVMEM (Non Volatile Memory) drivers;
  - Parport drivers…&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;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:
  - NVDIMM (Non-Volatile Memory Device) drivers;
  - Handshake API;
  - ARM32 architecture;
  - ARM64 architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Intel NPU Driver;
  - Android drivers;
  - Rados block device (RBD) driver;
  - Bluetooth drivers;
  - Hardware random number generator core;
  - TPM device driver;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - DMA engine subsystem;
  - FireWire subsystem;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - CoreSight HW tracing drivers;
  - I2C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Multifunction device drivers;
  - Fastrpc Driver;
  - Amazon Nitro Secure Module driver;
  - MMC subsystem;
  - MTD block device drivers;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - Texas Instruments network drivers;
  - NTB driver;
  - NVME drivers;
  - NVMEM (Non Volatile Memory) drivers;
  - Parport drivers…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8886-1</guid>
    </item>
  </channel>
</rss>
