<?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:40:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74506 — afs: Fix UAF when sending a message</title>
      <link>https://db.gcve.eu/vuln/cve-2026-74506</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;afs: Fix UAF when sending a message&lt;/p&gt;
&lt;p&gt;In afs_make_call(), there&amp;#39;s a race with async call reception and
destruction.  If a call is dispatched that doesn&amp;#39;t have call-&amp;gt;write_iter
set (used to specify the data content for FS.StoreData), then the first
rxrpc_kernel_send_data() will not set MSG_MORE in the msghdr.&lt;/p&gt;
&lt;p&gt;Once rxrpc_send_data() queues the last request packet, the response could
come in at any time and cause the call to be completed and put.  However,
afs_make_call() will look at the call again to see it -&amp;gt;write_iter should
be handled - something it&amp;#39;s only allowed to do if it has its own ref on the
call.  Whilst this is the case for synchronous calls, it isn&amp;#39;t true for
async calls such as FS.FetchData.&lt;/p&gt;
&lt;p&gt;There&amp;#39;s also a potential UAF in afs_make_call() in the event that an
asynchronous call is being sent, but the call fails in some way (e.g. it
gets aborted from the server).  The problem there is that afs_make_call()
tries to abort a call if the rxrpc send fails, but the asynchronous
notification from rxrpc may have caused the afs_call to be torn down.&lt;/p&gt;
&lt;p&gt;generic/650 plays games with randomly taking CPUs offline, and can
interject a significant delay such that the call is deallocated before
afs_make_call() gets to check call-&amp;gt;write_iter - and a UAF ensues (caught
by KASAN).&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in afs_make_call+0x1c90/0x2210 [kafs]
   Read of size 8 at addr ffff888035e050e8 by task fsstress/140…&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;afs: Fix UAF when sending a message&lt;/p&gt;
&lt;p&gt;In afs_make_call(), there&amp;#39;s a race with async call reception and
destruction.  If a call is dispatched that doesn&amp;#39;t have call-&amp;gt;write_iter
set (used to specify the data content for FS.StoreData), then the first
rxrpc_kernel_send_data() will not set MSG_MORE in the msghdr.&lt;/p&gt;
&lt;p&gt;Once rxrpc_send_data() queues the last request packet, the response could
come in at any time and cause the call to be completed and put.  However,
afs_make_call() will look at the call again to see it -&amp;gt;write_iter should
be handled - something it&amp;#39;s only allowed to do if it has its own ref on the
call.  Whilst this is the case for synchronous calls, it isn&amp;#39;t true for
async calls such as FS.FetchData.&lt;/p&gt;
&lt;p&gt;There&amp;#39;s also a potential UAF in afs_make_call() in the event that an
asynchronous call is being sent, but the call fails in some way (e.g. it
gets aborted from the server).  The problem there is that afs_make_call()
tries to abort a call if the rxrpc send fails, but the asynchronous
notification from rxrpc may have caused the afs_call to be torn down.&lt;/p&gt;
&lt;p&gt;generic/650 plays games with randomly taking CPUs offline, and can
interject a significant delay such that the call is deallocated before
afs_make_call() gets to check call-&amp;gt;write_iter - and a UAF ensues (caught
by KASAN).&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in afs_make_call+0x1c90/0x2210 [kafs]
   Read of size 8 at addr ffff888035e050e8 by task fsstress/140…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-74506</guid>
    </item>
    <item>
      <title>USN-8959-1 — linux, linux-aws, linux-gcp, linux-hwe-7.0, linux-ibm, linux-oracle vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8959-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle&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:
  - USB Gadget drivers;
  - Memory management;
  - Multiple devices driver;
  - ARM64 architecture;
  - EROFS file system;
  - Networking core;
  - eXpress Data Path;
  - ARM32 architecture;
  - M68K architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - Speakup Console Speech Driver;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Auxiliary display drivers;
  - Drivers core;
  - Micron PCIe SSD driver;
  - Null block device driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - AMD CDX bus driver;
  - Hardware random number generator core;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Clocksource drivers;
  - CPU frequency scaling framework;
  - CPU idle management framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - DIBS (Direct Internal Buffer Sharing) drivers;
  - Buffer Sharing and Synchronization framework;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle&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:
  - USB Gadget drivers;
  - Memory management;
  - Multiple devices driver;
  - ARM64 architecture;
  - EROFS file system;
  - Networking core;
  - eXpress Data Path;
  - ARM32 architecture;
  - M68K architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - Speakup Console Speech Driver;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Auxiliary display drivers;
  - Drivers core;
  - Micron PCIe SSD driver;
  - Null block device driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - AMD CDX bus driver;
  - Hardware random number generator core;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Clocksource drivers;
  - CPU frequency scaling framework;
  - CPU idle management framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - DIBS (Direct Internal Buffer Sharing) drivers;
  - Buffer Sharing and Synchronization framework;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8959-1</guid>
    </item>
  </channel>
</rss>
