<?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:27:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93241 — memcg: bypass the reclaim and oom killer for dying tasks once oom_reaper is done</title>
      <link>https://db.gcve.eu/vuln/cve-2026-93241</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;memcg: bypass the reclaim and oom killer for dying tasks once oom_reaper is done&lt;/p&gt;
&lt;p&gt;At Meta, we are seeing instances where an OOM killed job is stuck in the
exit path for several hours.  In one particular case, the job was stuck
for more than 8 hours and I had to manually remove the memory.max limits
to allow the process to exit.&lt;/p&gt;
&lt;p&gt;The job was a single process job and had ~55 GiB memory.max and zswap
enabled.  It had almost 0 anon in memory and ~111 GiB in zswap compressed
to ~51 GiB zswap pool (i.e.  almost all of memory.current was zswap). 
Nothing was left on the LRUs to reclaim.&lt;/p&gt;
&lt;p&gt;On further inspection, I observed ~20k threads of that process stuck with
the following stack:&lt;/p&gt;
&lt;p&gt;[&amp;lt;0&amp;gt;] mem_cgroup_out_of_memory+0x4e/0xa0
[&amp;lt;0&amp;gt;] charge_memcg+0x8bf/0x990
[&amp;lt;0&amp;gt;] mem_cgroup_swapin_charge_folio+0x4e/0x80
[&amp;lt;0&amp;gt;] __read_swap_cache_async+0x10c/0x260
[&amp;lt;0&amp;gt;] swapin_readahead+0x116/0x3f0
[&amp;lt;0&amp;gt;] do_swap_page+0x13c/0x1ce0
[&amp;lt;0&amp;gt;] handle_mm_fault+0x61d/0x11f0
[&amp;lt;0&amp;gt;] do_user_addr_fault+0x3e7/0x6d0
[&amp;lt;0&amp;gt;] exc_page_fault+0x8f/0x110
[&amp;lt;0&amp;gt;] asm_exc_page_fault+0x22/0x30
[&amp;lt;0&amp;gt;] __get_user_8+0x14/0x20
[&amp;lt;0&amp;gt;] futex_cleanup+0x27/0x1c0
[&amp;lt;0&amp;gt;] futex_exit_release+0x47/0x60
[&amp;lt;0&amp;gt;] do_exit+0x107/0x940
[&amp;lt;0&amp;gt;] do_group_exit+0x81/0xa0
[&amp;lt;0&amp;gt;] get_signal+0x2b1/0x6e0
[&amp;lt;0&amp;gt;] arch_do_signal_or_restart+0x1a/0x1c0
[&amp;lt;0&amp;gt;] exit_to_user_mode_loop+0xa8/0x1c0
[&amp;lt;0&amp;gt;] do_syscall_64+0x152/0x250
[&amp;lt;0&amp;gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53&lt;/p&gt;
&lt;p&gt;In addition the dmesg was filled wit…&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;memcg: bypass the reclaim and oom killer for dying tasks once oom_reaper is done&lt;/p&gt;
&lt;p&gt;At Meta, we are seeing instances where an OOM killed job is stuck in the
exit path for several hours.  In one particular case, the job was stuck
for more than 8 hours and I had to manually remove the memory.max limits
to allow the process to exit.&lt;/p&gt;
&lt;p&gt;The job was a single process job and had ~55 GiB memory.max and zswap
enabled.  It had almost 0 anon in memory and ~111 GiB in zswap compressed
to ~51 GiB zswap pool (i.e.  almost all of memory.current was zswap). 
Nothing was left on the LRUs to reclaim.&lt;/p&gt;
&lt;p&gt;On further inspection, I observed ~20k threads of that process stuck with
the following stack:&lt;/p&gt;
&lt;p&gt;[&amp;lt;0&amp;gt;] mem_cgroup_out_of_memory+0x4e/0xa0
[&amp;lt;0&amp;gt;] charge_memcg+0x8bf/0x990
[&amp;lt;0&amp;gt;] mem_cgroup_swapin_charge_folio+0x4e/0x80
[&amp;lt;0&amp;gt;] __read_swap_cache_async+0x10c/0x260
[&amp;lt;0&amp;gt;] swapin_readahead+0x116/0x3f0
[&amp;lt;0&amp;gt;] do_swap_page+0x13c/0x1ce0
[&amp;lt;0&amp;gt;] handle_mm_fault+0x61d/0x11f0
[&amp;lt;0&amp;gt;] do_user_addr_fault+0x3e7/0x6d0
[&amp;lt;0&amp;gt;] exc_page_fault+0x8f/0x110
[&amp;lt;0&amp;gt;] asm_exc_page_fault+0x22/0x30
[&amp;lt;0&amp;gt;] __get_user_8+0x14/0x20
[&amp;lt;0&amp;gt;] futex_cleanup+0x27/0x1c0
[&amp;lt;0&amp;gt;] futex_exit_release+0x47/0x60
[&amp;lt;0&amp;gt;] do_exit+0x107/0x940
[&amp;lt;0&amp;gt;] do_group_exit+0x81/0xa0
[&amp;lt;0&amp;gt;] get_signal+0x2b1/0x6e0
[&amp;lt;0&amp;gt;] arch_do_signal_or_restart+0x1a/0x1c0
[&amp;lt;0&amp;gt;] exit_to_user_mode_loop+0xa8/0x1c0
[&amp;lt;0&amp;gt;] do_syscall_64+0x152/0x250
[&amp;lt;0&amp;gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53&lt;/p&gt;
&lt;p&gt;In addition the dmesg was filled wit…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-93241</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>
