<?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:45:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72420 — md/raid5: avoid R5_Overlap races while breaking stripe batches</title>
      <link>https://db.gcve.eu/vuln/cve-2026-72420</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;md/raid5: avoid R5_Overlap races while breaking stripe batches&lt;/p&gt;
&lt;p&gt;KCSAN report a race in break_stripe_batch_list() vs. raid5_make_request()
on sh-&amp;gt;dev[i].flags (plain word write vs. atomic bit op)..&lt;/p&gt;
&lt;p&gt;and .. one possible scenario is:&lt;/p&gt;
&lt;p&gt;CPU1                            CPU2
break_stripe_batch_list(sh1)
-&amp;gt; handle sh2
-&amp;gt; lock(sh2)
-&amp;gt; sh2-&amp;gt;batch_head = NULL
-&amp;gt; unlock(sh2)
-&amp;gt; test_and_clear_bit(R5_Overlap, sh2-&amp;gt;dev[i].flags)
-&amp;gt; wake_up_bit(sh2-&amp;gt;dev[i].flags)
                                raid5_make_request()
                                -&amp;gt; add_all_stripe_bios(sh2)
                                -&amp;gt; lock(sh2)
                                -&amp;gt; stripe_bio_overlaps(sh2) returns true
				   batch_head is NULL, so new bio overlap
				   exist bio on sh2 -&amp;gt; true
                                -&amp;gt; set_bit(R5_Overlap, sh2-&amp;gt;dev[i].flags)
                                -&amp;gt; unlock(sh2)
                                -&amp;gt; wait_on_bit(sh2-&amp;gt;dev[i].flags)
-&amp;gt; sh2-&amp;gt;dev[i].flags = sh1-&amp;gt;dev[i].flags &amp;amp; ~R5_Overlap&lt;/p&gt;
&lt;p&gt;No wait_up_bit(), CPU2 could be wait_on_bit() forever...&lt;/p&gt;
&lt;p&gt;Fix by :
- Expand the protect zone.
- Use batch_head&amp;#39;s device flag&amp;#39;s snaphot when no held head_sh-&amp;gt;stripe_lock.
- Move sh/head_sh-&amp;gt;batch_head = NULL to the end of protected zone , and ,
  any concurrent add_all_stripe_bios() grabs sh-&amp;gt;stripe_lock now either:
	- see batch_head != null, and , is rejected by stripe_bio_overlaps()
	  under the lock (no R5_Overlap wait…&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;md/raid5: avoid R5_Overlap races while breaking stripe batches&lt;/p&gt;
&lt;p&gt;KCSAN report a race in break_stripe_batch_list() vs. raid5_make_request()
on sh-&amp;gt;dev[i].flags (plain word write vs. atomic bit op)..&lt;/p&gt;
&lt;p&gt;and .. one possible scenario is:&lt;/p&gt;
&lt;p&gt;CPU1                            CPU2
break_stripe_batch_list(sh1)
-&amp;gt; handle sh2
-&amp;gt; lock(sh2)
-&amp;gt; sh2-&amp;gt;batch_head = NULL
-&amp;gt; unlock(sh2)
-&amp;gt; test_and_clear_bit(R5_Overlap, sh2-&amp;gt;dev[i].flags)
-&amp;gt; wake_up_bit(sh2-&amp;gt;dev[i].flags)
                                raid5_make_request()
                                -&amp;gt; add_all_stripe_bios(sh2)
                                -&amp;gt; lock(sh2)
                                -&amp;gt; stripe_bio_overlaps(sh2) returns true
				   batch_head is NULL, so new bio overlap
				   exist bio on sh2 -&amp;gt; true
                                -&amp;gt; set_bit(R5_Overlap, sh2-&amp;gt;dev[i].flags)
                                -&amp;gt; unlock(sh2)
                                -&amp;gt; wait_on_bit(sh2-&amp;gt;dev[i].flags)
-&amp;gt; sh2-&amp;gt;dev[i].flags = sh1-&amp;gt;dev[i].flags &amp;amp; ~R5_Overlap&lt;/p&gt;
&lt;p&gt;No wait_up_bit(), CPU2 could be wait_on_bit() forever...&lt;/p&gt;
&lt;p&gt;Fix by :
- Expand the protect zone.
- Use batch_head&amp;#39;s device flag&amp;#39;s snaphot when no held head_sh-&amp;gt;stripe_lock.
- Move sh/head_sh-&amp;gt;batch_head = NULL to the end of protected zone , and ,
  any concurrent add_all_stripe_bios() grabs sh-&amp;gt;stripe_lock now either:
	- see batch_head != null, and , is rejected by stripe_bio_overlaps()
	  under the lock (no R5_Overlap wait…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-72420</guid>
    </item>
    <item>
      <title>USN-8886-1 — linux-nvidia-tegra vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8886-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-nvidia-tegra&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:
  - NVDIMM (Non-Volatile Memory Device) drivers;
  - Handshake API;
  - ARM32 architecture;
  - ARM64 architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Intel NPU Driver;
  - Android drivers;
  - Rados block device (RBD) driver;
  - Bluetooth drivers;
  - Hardware random number generator core;
  - TPM device driver;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - DMA engine subsystem;
  - FireWire subsystem;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - CoreSight HW tracing drivers;
  - I2C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Multifunction device drivers;
  - Fastrpc Driver;
  - Amazon Nitro Secure Module driver;
  - MMC subsystem;
  - MTD block device drivers;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - Texas Instruments network drivers;
  - NTB driver;
  - NVME drivers;
  - NVMEM (Non Volatile Memory) drivers;
  - Parport drivers…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-nvidia-tegra&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:
  - NVDIMM (Non-Volatile Memory Device) drivers;
  - Handshake API;
  - ARM32 architecture;
  - ARM64 architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Intel NPU Driver;
  - Android drivers;
  - Rados block device (RBD) driver;
  - Bluetooth drivers;
  - Hardware random number generator core;
  - TPM device driver;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - DMA engine subsystem;
  - FireWire subsystem;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - CoreSight HW tracing drivers;
  - I2C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Multifunction device drivers;
  - Fastrpc Driver;
  - Amazon Nitro Secure Module driver;
  - MMC subsystem;
  - MTD block device drivers;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - Texas Instruments network drivers;
  - NTB driver;
  - NVME drivers;
  - NVMEM (Non Volatile Memory) drivers;
  - Parport drivers…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8886-1</guid>
    </item>
  </channel>
</rss>
