<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T13:19:16.721434+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-90385</id>
    <title>fkie_cve-2026-90385</title>
    <updated>2026-09-30T13:19:16.775759+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>md/raid1: create serial pool adding rdev to array with serialize_policy=1</p>
<p>The following bug has been observed with kernel 7.1.3 after adding a new
rdev to an existing RAID1 array with serialize_policy enabled:</p>
<p>Oops: 0002 [#1]
  CPU: 0 UID: 0 PID: 19639 Comm: ext4lazyinit Not tainted 7.1.3-1-default
  RIP: _raw_spin_lock_irqsave+0x27/0x50
  CR2: 0000000000004960
  Call Trace:
   wait_for_serialization+0xb9/0x260 [raid1]
   raid1_make_request+0x762/0xaff [raid1]
   md_handle_request+0x1c9/0x2e0 [md_mod]</p>
<p>The raid1.c code calls wait_for_serialization() if the MD_SERIALIZE_POLICY
is set, and wait_for_serialization assumes that rdev-&gt;serial is
initialized. Normally this will be the case for arrays that have
the serialize_policy sysfs attribute set to 1.</p>
<p>But when a new rdev is added to an existing array in bind_rdev_to_array(),
the condition at mddev_create_serial_pool() causes creation of rdev-&gt;serial
to be skipped. Fix it.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-90385"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-6jq9-46p7-p377</id>
    <title>GHSA-6jq9-46p7-p377</title>
    <updated>2026-09-30T13:19:16.775853+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>md/raid1: create serial pool adding rdev to array with serialize_policy=1</p>
<p>The following bug has been observed with kernel 7.1.3 after adding a new
rdev to an existing RAID1 array with serialize_policy enabled:</p>
<p>Oops: 0002 [#1]
  CPU: 0 UID: 0 PID: 19639 Comm: ext4lazyinit Not tainted 7.1.3-1-default
  RIP: _raw_spin_lock_irqsave+0x27/0x50
  CR2: 0000000000004960
  Call Trace:
   wait_for_serialization+0xb9/0x260 [raid1]
   raid1_make_request+0x762/0xaff [raid1]
   md_handle_request+0x1c9/0x2e0 [md_mod]</p>
<p>The raid1.c code calls wait_for_serialization() if the MD_SERIALIZE_POLICY
is set, and wait_for_serialization assumes that rdev-&gt;serial is
initialized. Normally this will be the case for arrays that have
the serialize_policy sysfs attribute set to 1.</p>
<p>But when a new rdev is added to an existing array in bind_rdev_to_array(),
the condition at mddev_create_serial_pool() causes creation of rdev-&gt;serial
to be skipped. Fix it.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-6jq9-46p7-p377"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/opensuse-su-2026:11893-1</id>
    <title>openSUSE-SU-2026:11893-1 — kernel-devel-7.2.8-1.1 on GA media</title>
    <updated>2026-09-30T13:19:16.775886+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kernel-devel-7.2.8-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/opensuse-su-2026:11893-1"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ubuntu-cve-2026-90385</id>
    <title>UBUNTU-CVE-2026-90385</title>
    <updated>2026-09-30T13:19:16.776230+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 193 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: md/raid1: create serial pool adding rdev to array with serialize_policy=1 The following bug has been observed with kernel 7.1.3 after adding a new rdev to an existing RAID1 array with serialize_policy enabled:   Oops: 0002 [#1]   CPU: 0 UID: 0 PID: 19639 Comm: ext4lazyinit Not tainted 7.1.3-1-default   RIP: _raw_spin_lock_irqsave+0x27/0x50   CR2: 0000000000004960   Call Trace:    wait_for_serialization+0xb9/0x260 [raid1]    raid1_make_request+0x762/0xaff [raid1]    md_handle_request+0x1c9/0x2e0 [md_mod] The raid1.c code calls wait_for_serialization() if the MD_SERIALIZE_POLICY is set, and wait_for_serialization assumes that rdev-&gt;serial is initialized. Normally this will be the case for arrays that have the serialize_policy sysfs attribute set to 1. But when a new rdev is added to an existing array in bind_rdev_to_array(), the condition at mddev_create_serial_pool() causes creation of rdev-&gt;serial to be skipped. Fix it.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ubuntu-cve-2026-90385"/>
  </entry>
</feed>
