<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T17:26:32.764782+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-53260</id>
    <title>CVE-2026-53260 — tcp: Add preempt_{disable,enable}_nested() in reqsk_queue_hash_req().</title>
    <updated>2026-11-19T17:26:32.785699+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>tcp: Add preempt_{disable,enable}_nested() in reqsk_queue_hash_req().</p>
<p>syzbot reported a weird reqsk-&gt;rsk_refcnt underflow in
__inet_csk_reqsk_queue_drop().</p>
<p>The captured reqsk_put() in __inet_csk_reqsk_queue_drop()
is called only when it successfully removes reqsk from ehash.</p>
<p>Moreover, reqsk_timer_handler() calls another reqsk_put()
after that.</p>
<p>This indicates that the reqsk was missing both refcnts for
ehash and the timer itself.</p>
<p>Since all the syzbot reports had PREEMPT_RT enabled, the only
possible scenario is that reqsk_queue_hash_req() is preempted
after mod_timer() and before refcount_set(), and then the timer
triggered after 1s aborts the reqsk due to its listener's close().</p>
<p>Let's wrap mod_timer() and refcount_set() with
preempt_disable_nested() and preempt_enable_nested().</p>
<p>Note that inet_ehash_insert() holds the normal spin_lock()
(mutex in PREEMPT_RT), so it must be called outside of
preempt_disable_nested(), but this is fine.</p>
<p>The lookup path just ignores 0 sk_refcnt entries in ehash
and tries to create another reqsk, but this will fail at
inet_ehash_insert().</p>
<p>[0]:
refcount_t: underflow; use-after-free.
WARNING: lib/refcount.c:28 at refcount_warn_saturate+0xb2/0x110 lib/refcount.c:28, CPU#0: ktimers/0/16
Modules linked in:
CPU: 0 UID: 0 PID: 16 Comm: ktimers/0 Tainted: G             L      syzkaller #0 PREEMPT_{RT,(full)}
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Goo…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-53260"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/usn-8629-1</id>
    <title>USN-8629-1 — linux, linux-aws, linux-azure, linux-azure-fde, linux-ibm, linux-oracle, linux-raspi, linux-realtime vulnerabilities</title>
    <updated>2026-11-19T17:26:32.785812+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-azure, Ubuntu:26.04:LTS: linux-azure-fde, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle, Ubuntu:26.04:LTS: linux-raspi, Ubuntu:26.04:LTS: linux-realtime</p>
<p>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:
  - x86 architecture;
  - InfiniBand drivers;
  - Network drivers;
  - Network traffic control;
  - IPv4 networking;
  - IPv6 networking;
  - Netfilter;
  - RxRPC session sockets;
  - SCTP protocol;
(CVE-2026-46331, CVE-2026-52924, CVE-2026-53131, CVE-2026-53151,
CVE-2026-53175, CVE-2026-53176, CVE-2026-53186, CVE-2026-53212,
CVE-2026-53215, CVE-2026-53216, CVE-2026-53221, CVE-2026-53224,
CVE-2026-53225, CVE-2026-53228, CVE-2026-53246, CVE-2026-53247,
CVE-2026-53260, CVE-2026-53359)</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/usn-8629-1"/>
  </entry>
</feed>
