<?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://cve.radiocsirt.org</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, 15 Oct 2026 08:04:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-42234 — mm: fix crashes from deferred split racing folio migration</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-42234</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;mm: fix crashes from deferred split racing folio migration&lt;/p&gt;
&lt;p&gt;Even on 6.10-rc6, I&amp;#39;ve been seeing elusive &amp;#34;Bad page state&amp;#34;s (often on
flags when freeing, yet the flags shown are not bad: PG_locked had been
set and cleared??), and VM_BUG_ON_PAGE(page_ref_count(page) == 0)s from
deferred_split_scan()&amp;#39;s folio_put(), and a variety of other BUG and WARN
symptoms implying double free by deferred split and large folio migration.&lt;/p&gt;
&lt;p&gt;6.7 commit 9bcef5973e31 (&amp;#34;mm: memcg: fix split queue list crash when large
folio migration&amp;#34;) was right to fix the memcg-dependent locking broken in
85ce2c517ade (&amp;#34;memcontrol: only transfer the memcg data for migration&amp;#34;),
but missed a subtlety of deferred_split_scan(): it moves folios to its own
local list to work on them without split_queue_lock, during which time
folio-&amp;gt;_deferred_list is not empty, but even the &amp;#34;right&amp;#34; lock does nothing
to secure the folio and the list it is on.&lt;/p&gt;
&lt;p&gt;Fortunately, deferred_split_scan() is careful to use folio_try_get(): so
folio_migrate_mapping() can avoid the race by folio_undo_large_rmappable()
while the old folio&amp;#39;s reference count is temporarily frozen to 0 - adding
such a freeze in the !mapping case too (originally, folio lock and
unmapping and no swap cache left an anon folio unreachable, so no freezing
was needed there: but the deferred split queue offers a way to reach it).&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;mm: fix crashes from deferred split racing folio migration&lt;/p&gt;
&lt;p&gt;Even on 6.10-rc6, I&amp;#39;ve been seeing elusive &amp;#34;Bad page state&amp;#34;s (often on
flags when freeing, yet the flags shown are not bad: PG_locked had been
set and cleared??), and VM_BUG_ON_PAGE(page_ref_count(page) == 0)s from
deferred_split_scan()&amp;#39;s folio_put(), and a variety of other BUG and WARN
symptoms implying double free by deferred split and large folio migration.&lt;/p&gt;
&lt;p&gt;6.7 commit 9bcef5973e31 (&amp;#34;mm: memcg: fix split queue list crash when large
folio migration&amp;#34;) was right to fix the memcg-dependent locking broken in
85ce2c517ade (&amp;#34;memcontrol: only transfer the memcg data for migration&amp;#34;),
but missed a subtlety of deferred_split_scan(): it moves folios to its own
local list to work on them without split_queue_lock, during which time
folio-&amp;gt;_deferred_list is not empty, but even the &amp;#34;right&amp;#34; lock does nothing
to secure the folio and the list it is on.&lt;/p&gt;
&lt;p&gt;Fortunately, deferred_split_scan() is careful to use folio_try_get(): so
folio_migrate_mapping() can avoid the race by folio_undo_large_rmappable()
while the old folio&amp;#39;s reference count is temporarily frozen to 0 - adding
such a freeze in the !mapping case too (originally, folio lock and
unmapping and no swap cache left an anon folio unreachable, so no freezing
was needed there: but the deferred split queue offers a way to reach it).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-42234</guid>
    </item>
    <item>
      <title>USN-7089-1 — linux, linux-gcp-6.8, linux-hwe-6.8 vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7089-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-gcp-6.8, Ubuntu:22.04:LTS: linux-hwe-6.8, Ubuntu:24.04:LTS: linux&lt;/p&gt;
&lt;p&gt;Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel
did not properly check for the device to be enabled before writing. A local
attacker could possibly use this to cause a denial of service. (CVE-2024-25741)&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:
  - ARM32 architecture;
  - MIPS architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Cryptographic API;
  - Serial ATA and Parallel ATA drivers;
  - Null block device driver;
  - Bluetooth drivers;
  - Cdrom driver;
  - Clock framework and drivers;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - Cirrus firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - I2C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - ISDN/mISDN subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Fastrpc Driver;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - Near Field Communication (NFC) drivers;
  - NVME drivers;
  - NVMEM (Non Volatile Memory) drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - S/390 drivers;
  - SCSI drivers;
  - Thermal drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB DSL drivers;
  - USB core drivers;
  - DesignWare USB3 driver;
  - USB Gadget dr…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-gcp-6.8, Ubuntu:22.04:LTS: linux-hwe-6.8, Ubuntu:24.04:LTS: linux&lt;/p&gt;
&lt;p&gt;Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel
did not properly check for the device to be enabled before writing. A local
attacker could possibly use this to cause a denial of service. (CVE-2024-25741)&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:
  - ARM32 architecture;
  - MIPS architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Cryptographic API;
  - Serial ATA and Parallel ATA drivers;
  - Null block device driver;
  - Bluetooth drivers;
  - Cdrom driver;
  - Clock framework and drivers;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - Cirrus firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - I2C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - ISDN/mISDN subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Fastrpc Driver;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - Near Field Communication (NFC) drivers;
  - NVME drivers;
  - NVMEM (Non Volatile Memory) drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - S/390 drivers;
  - SCSI drivers;
  - Thermal drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB DSL drivers;
  - USB core drivers;
  - DesignWare USB3 driver;
  - USB Gadget dr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7089-1</guid>
    </item>
  </channel>
</rss>
