<?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:32:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23394 — af_unix: Give up GC if MSG_PEEK intervened.</title>
      <link>https://db.gcve.eu/vuln/cve-2026-23394</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;af_unix: Give up GC if MSG_PEEK intervened.&lt;/p&gt;
&lt;p&gt;Igor Ushakov reported that GC purged the receive queue of
an alive socket due to a race with MSG_PEEK with a nice repro.&lt;/p&gt;
&lt;p&gt;This is the exact same issue previously fixed by commit
cbcf01128d0a (&amp;#34;af_unix: fix garbage collect vs MSG_PEEK&amp;#34;).&lt;/p&gt;
&lt;p&gt;After GC was replaced with the current algorithm, the cited
commit removed the locking dance in unix_peek_fds() and
reintroduced the same issue.&lt;/p&gt;
&lt;p&gt;The problem is that MSG_PEEK bumps a file refcount without
interacting with GC.&lt;/p&gt;
&lt;p&gt;Consider an SCC containing sk-A and sk-B, where sk-A is
close()d but can be recv()ed via sk-B.&lt;/p&gt;
&lt;p&gt;The bad thing happens if sk-A is recv()ed with MSG_PEEK from
sk-B and sk-B is close()d while GC is checking unix_vertex_dead()
for sk-A and sk-B.&lt;/p&gt;
&lt;p&gt;GC thread                    User thread
  ---------                    -----------
  unix_vertex_dead(sk-A)
  -&amp;gt; true   &amp;lt;------.
                    \
                     `------   recv(sk-B, MSG_PEEK)
              invalidate !!    -&amp;gt; sk-A&amp;#39;s file refcount : 1 -&amp;gt; 2&lt;/p&gt;
&lt;p&gt;close(sk-B)
                               -&amp;gt; sk-B&amp;#39;s file refcount : 2 -&amp;gt; 1
  unix_vertex_dead(sk-B)
  -&amp;gt; true&lt;/p&gt;
&lt;p&gt;Initially, sk-A&amp;#39;s file refcount is 1 by the inflight fd in sk-B
recvq.  GC thinks sk-A is dead because the file refcount is the
same as the number of its inflight fds.&lt;/p&gt;
&lt;p&gt;However, sk-A&amp;#39;s file refcount is bumped silently by MSG_PEEK,
which invalidates the previous e…&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;af_unix: Give up GC if MSG_PEEK intervened.&lt;/p&gt;
&lt;p&gt;Igor Ushakov reported that GC purged the receive queue of
an alive socket due to a race with MSG_PEEK with a nice repro.&lt;/p&gt;
&lt;p&gt;This is the exact same issue previously fixed by commit
cbcf01128d0a (&amp;#34;af_unix: fix garbage collect vs MSG_PEEK&amp;#34;).&lt;/p&gt;
&lt;p&gt;After GC was replaced with the current algorithm, the cited
commit removed the locking dance in unix_peek_fds() and
reintroduced the same issue.&lt;/p&gt;
&lt;p&gt;The problem is that MSG_PEEK bumps a file refcount without
interacting with GC.&lt;/p&gt;
&lt;p&gt;Consider an SCC containing sk-A and sk-B, where sk-A is
close()d but can be recv()ed via sk-B.&lt;/p&gt;
&lt;p&gt;The bad thing happens if sk-A is recv()ed with MSG_PEEK from
sk-B and sk-B is close()d while GC is checking unix_vertex_dead()
for sk-A and sk-B.&lt;/p&gt;
&lt;p&gt;GC thread                    User thread
  ---------                    -----------
  unix_vertex_dead(sk-A)
  -&amp;gt; true   &amp;lt;------.
                    \
                     `------   recv(sk-B, MSG_PEEK)
              invalidate !!    -&amp;gt; sk-A&amp;#39;s file refcount : 1 -&amp;gt; 2&lt;/p&gt;
&lt;p&gt;close(sk-B)
                               -&amp;gt; sk-B&amp;#39;s file refcount : 2 -&amp;gt; 1
  unix_vertex_dead(sk-B)
  -&amp;gt; true&lt;/p&gt;
&lt;p&gt;Initially, sk-A&amp;#39;s file refcount is 1 by the inflight fd in sk-B
recvq.  GC thinks sk-A is dead because the file refcount is the
same as the number of its inflight fds.&lt;/p&gt;
&lt;p&gt;However, sk-A&amp;#39;s file refcount is bumped silently by MSG_PEEK,
which invalidates the previous e…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-23394</guid>
    </item>
    <item>
      <title>USN-8277-1 — linux, linux-aws, linux-hwe-6.17, linux-oem-6.17, linux-oracle, linux-raspi, linux-realtime, linux-realtime-6.17 vulner…</title>
      <link>https://db.gcve.eu/vuln/usn-8277-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.17, Ubuntu:24.04:LTS: linux-oem-6.17, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime-6.17, Ubuntu:25.10: linux, Ubuntu:25.10: linux-aws, Ubuntu:25.10: linux-oracle, Ubuntu:25.10: linux-raspi, Ubuntu:25.10: linux-realtime&lt;/p&gt;
&lt;p&gt;It was discovered that the Linux kernel algif_aead module did not properly
handle in-place cryptographic operations. This flaw is known as Copy Fail.
A local attacker could use this to escalate privileges, or possibly escape
a container. (CVE-2026-31431)&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:
  - S390 architecture;
  - Cryptographic API;
  - GPU drivers;
  - Ethernet bonding driver;
  - Network file system (NFS) server daemon;
  - Distributed Switch Architecture;
  - Netfilter;
  - Control group (cgroup);
  - Kernel kexec() syscall;
  - Memory management;
  - MAC80211 subsystem;
  - Multipath TCP;
  - Packet sockets;
  - TLS protocol;
  - Unix domain sockets;
(CVE-2025-71088, CVE-2025-71090, CVE-2025-71127, CVE-2025-71134,
CVE-2025-71139, CVE-2025-71141, CVE-2025-71142, CVE-2025-71144,
CVE-2025-71152, CVE-2025-71155, CVE-2026-23274, CVE-2026-23351,
CVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,
CVE-2026-43033, CVE-2026-43077, CVE-2026-43078)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.17, Ubuntu:24.04:LTS: linux-oem-6.17, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime-6.17, Ubuntu:25.10: linux, Ubuntu:25.10: linux-aws, Ubuntu:25.10: linux-oracle, Ubuntu:25.10: linux-raspi, Ubuntu:25.10: linux-realtime&lt;/p&gt;
&lt;p&gt;It was discovered that the Linux kernel algif_aead module did not properly
handle in-place cryptographic operations. This flaw is known as Copy Fail.
A local attacker could use this to escalate privileges, or possibly escape
a container. (CVE-2026-31431)&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:
  - S390 architecture;
  - Cryptographic API;
  - GPU drivers;
  - Ethernet bonding driver;
  - Network file system (NFS) server daemon;
  - Distributed Switch Architecture;
  - Netfilter;
  - Control group (cgroup);
  - Kernel kexec() syscall;
  - Memory management;
  - MAC80211 subsystem;
  - Multipath TCP;
  - Packet sockets;
  - TLS protocol;
  - Unix domain sockets;
(CVE-2025-71088, CVE-2025-71090, CVE-2025-71127, CVE-2025-71134,
CVE-2025-71139, CVE-2025-71141, CVE-2025-71142, CVE-2025-71144,
CVE-2025-71152, CVE-2025-71155, CVE-2026-23274, CVE-2026-23351,
CVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,
CVE-2026-43033, CVE-2026-43077, CVE-2026-43078)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8277-1</guid>
    </item>
  </channel>
</rss>
