<?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:37:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-43914 — md/raid5: avoid BUG_ON() while continue reshape after reassembling</title>
      <link>https://db.gcve.eu/vuln/cve-2024-43914</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 BUG_ON() while continue reshape after reassembling&lt;/p&gt;
&lt;p&gt;Currently, mdadm support --revert-reshape to abort the reshape while
reassembling, as the test 07revert-grow. However, following BUG_ON()
can be triggerred by the test:&lt;/p&gt;
&lt;p&gt;kernel BUG at drivers/md/raid5.c:6278!
invalid opcode: 0000 [#1] PREEMPT SMP PTI
irq event stamp: 158985
CPU: 6 PID: 891 Comm: md0_reshape Not tainted 6.9.0-03335-g7592a0b0049a #94
RIP: 0010:reshape_request+0x3f1/0xe60
Call Trace:
 &amp;lt;TASK&amp;gt;
 raid5_sync_request+0x43d/0x550
 md_do_sync+0xb7a/0x2110
 md_thread+0x294/0x2b0
 kthread+0x147/0x1c0
 ret_from_fork+0x59/0x70
 ret_from_fork_asm+0x1a/0x30
 &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;Root cause is that --revert-reshape update the raid_disks from 5 to 4,
while reshape position is still set, and after reassembling the array,
reshape position will be read from super block, then during reshape the
checking of &amp;#39;writepos&amp;#39; that is caculated by old reshape position will
fail.&lt;/p&gt;
&lt;p&gt;Fix this panic the easy way first, by converting the BUG_ON() to
WARN_ON(), and stop the reshape if checkings fail.&lt;/p&gt;
&lt;p&gt;Noted that mdadm must fix --revert-shape as well, and probably md/raid
should enhance metadata validation as well, however this means
reassemble will fail and there must be user tools to fix the wrong
metadata.&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 BUG_ON() while continue reshape after reassembling&lt;/p&gt;
&lt;p&gt;Currently, mdadm support --revert-reshape to abort the reshape while
reassembling, as the test 07revert-grow. However, following BUG_ON()
can be triggerred by the test:&lt;/p&gt;
&lt;p&gt;kernel BUG at drivers/md/raid5.c:6278!
invalid opcode: 0000 [#1] PREEMPT SMP PTI
irq event stamp: 158985
CPU: 6 PID: 891 Comm: md0_reshape Not tainted 6.9.0-03335-g7592a0b0049a #94
RIP: 0010:reshape_request+0x3f1/0xe60
Call Trace:
 &amp;lt;TASK&amp;gt;
 raid5_sync_request+0x43d/0x550
 md_do_sync+0xb7a/0x2110
 md_thread+0x294/0x2b0
 kthread+0x147/0x1c0
 ret_from_fork+0x59/0x70
 ret_from_fork_asm+0x1a/0x30
 &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;Root cause is that --revert-reshape update the raid_disks from 5 to 4,
while reshape position is still set, and after reassembling the array,
reshape position will be read from super block, then during reshape the
checking of &amp;#39;writepos&amp;#39; that is caculated by old reshape position will
fail.&lt;/p&gt;
&lt;p&gt;Fix this panic the easy way first, by converting the BUG_ON() to
WARN_ON(), and stop the reshape if checkings fail.&lt;/p&gt;
&lt;p&gt;Noted that mdadm must fix --revert-shape as well, and probably md/raid
should enhance metadata validation as well, however this means
reassemble will fail and there must be user tools to fix the wrong
metadata.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2024-43914</guid>
    </item>
    <item>
      <title>USN-7088-1 — linux, linux-gcp, linux-gcp-5.4, linux-gkeop, linux-hwe-5.4, linux-ibm, linux-ibm-5.4 vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-7088-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: linux-gcp-5.4, Ubuntu:Pro:18.04:LTS: linux-hwe-5.4, Ubuntu:Pro:18.04:LTS: linux-ibm-5.4, Ubuntu:20.04:LTS: linux, Ubuntu:20.04:LTS: linux-gcp, Ubuntu:20.04:LTS: linux-gkeop, Ubuntu:20.04:LTS: linux-ibm&lt;/p&gt;
&lt;p&gt;Ziming Zhang discovered that the VMware Virtual GPU DRM driver in the Linux
kernel contained an integer overflow vulnerability. A local attacker could
use this to cause a denial of service (system crash). (CVE-2022-36402)&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:
  - ARM64 architecture;
  - PowerPC architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Android drivers;
  - Serial ATA and Parallel ATA drivers;
  - ATM drivers;
  - Drivers core;
  - CPU frequency scaling framework;
  - Device frequency scaling framework;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - ISDN/mISDN subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - EEPROM drivers;
  - VMware VMCI Driver;
  - MMC subsystem;
  - Network drivers;
  - Near Field Communication (NFC) drivers;
  - NVME drivers;
  - Device tree and open firmware driver;
  - Parport drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI drivers;
  - QCOM SoC drivers;
  - Direct Digital Synthesis drivers;
  - TTY drivers;
  - Userspace I/O drivers;
  - DesignWare USB3 driver;
  - USB subsystem;
  - BTRFS file system;
  - File sy…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: linux-gcp-5.4, Ubuntu:Pro:18.04:LTS: linux-hwe-5.4, Ubuntu:Pro:18.04:LTS: linux-ibm-5.4, Ubuntu:20.04:LTS: linux, Ubuntu:20.04:LTS: linux-gcp, Ubuntu:20.04:LTS: linux-gkeop, Ubuntu:20.04:LTS: linux-ibm&lt;/p&gt;
&lt;p&gt;Ziming Zhang discovered that the VMware Virtual GPU DRM driver in the Linux
kernel contained an integer overflow vulnerability. A local attacker could
use this to cause a denial of service (system crash). (CVE-2022-36402)&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:
  - ARM64 architecture;
  - PowerPC architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Android drivers;
  - Serial ATA and Parallel ATA drivers;
  - ATM drivers;
  - Drivers core;
  - CPU frequency scaling framework;
  - Device frequency scaling framework;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - ISDN/mISDN subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - EEPROM drivers;
  - VMware VMCI Driver;
  - MMC subsystem;
  - Network drivers;
  - Near Field Communication (NFC) drivers;
  - NVME drivers;
  - Device tree and open firmware driver;
  - Parport drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI drivers;
  - QCOM SoC drivers;
  - Direct Digital Synthesis drivers;
  - TTY drivers;
  - Userspace I/O drivers;
  - DesignWare USB3 driver;
  - USB subsystem;
  - BTRFS file system;
  - File sy…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7088-1</guid>
    </item>
  </channel>
</rss>
