Vulnerability-Lookup

GHSA-6JQ9-46P7-P377

Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32

Details

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->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->serial to be skipped. Fix it.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-90385"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-17T17:17:37Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmd/raid1: create serial pool adding rdev to array with serialize_policy=1\n\nThe following bug has been observed with kernel 7.1.3 after adding a new\nrdev to an existing RAID1 array with serialize_policy enabled:\n\n  Oops: 0002 [#1]\n  CPU: 0 UID: 0 PID: 19639 Comm: ext4lazyinit Not tainted 7.1.3-1-default\n  RIP: _raw_spin_lock_irqsave+0x27/0x50\n  CR2: 0000000000004960\n  Call Trace:\n   wait_for_serialization+0xb9/0x260 [raid1]\n   raid1_make_request+0x762/0xaff [raid1]\n   md_handle_request+0x1c9/0x2e0 [md_mod]\n\nThe raid1.c code calls wait_for_serialization() if the MD_SERIALIZE_POLICY\nis set, and wait_for_serialization assumes that rdev-\u003eserial is\ninitialized. Normally this will be the case for arrays that have\nthe serialize_policy sysfs attribute set to 1.\n\nBut when a new rdev is added to an existing array in bind_rdev_to_array(),\nthe condition at mddev_create_serial_pool() causes creation of rdev-\u003eserial\nto be skipped. Fix it.",
  "id": "GHSA-6jq9-46p7-p377",
  "modified": "2026-09-17T18:32:03Z",
  "published": "2026-09-17T18:32:03Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90385"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/140234b2380ffb8ffb0cfc46fee0e822f43adef7"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/37f11973c3eb72a5eb061082cad529bb6939c24f"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c02d675e81468003e4f2253b616c53729070d712"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/f9e4364449f7ca6917f3599eb32064dba5b7b147"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-90385 (GCVE-0-2026-90385)

Vulnerability from cvelistv5 – Published: 2026-09-17 16:09 – Updated: 2026-09-17 16:09

Title

md/raid1: create serial pool adding rdev to array with serialize_policy=1

Summary

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->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->serial to be skipped. Fix it.

Severity

No CVSS data available.

Assigner

Linux mitre root Scorecard

References

4 references

URL	Tags
https://git.kernel.org/stable/c/f9e4364449f7ca691…
https://git.kernel.org/stable/c/37f11973c3eb72a5e…
https://git.kernel.org/stable/c/c02d675e81468003e…
https://git.kernel.org/stable/c/140234b2380ffb8ff…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 69b00b5bb23552d43e8bbed73ef6624604bb94a2 , < f9e4364449f7ca6917f3599eb32064dba5b7b147 (git) Affected: 69b00b5bb23552d43e8bbed73ef6624604bb94a2 , < 37f11973c3eb72a5eb061082cad529bb6939c24f (git) Affected: 69b00b5bb23552d43e8bbed73ef6624604bb94a2 , < c02d675e81468003e4f2253b616c53729070d712 (git) Affected: 69b00b5bb23552d43e8bbed73ef6624604bb94a2 , < 140234b2380ffb8ffb0cfc46fee0e822f43adef7 (git)
Linux	Linux	Affected: 5.6 Unaffected: 0 , < 5.6 (semver) Unaffected: 6.12.110 , ≤ 6.12.* (semver) Unaffected: 6.18.52 , ≤ 6.18.* (semver) Unaffected: 7.2.6 , ≤ 7.2.* (semver) Unaffected: 7.3-rc1 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/md/md.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "f9e4364449f7ca6917f3599eb32064dba5b7b147",
              "status": "affected",
              "version": "69b00b5bb23552d43e8bbed73ef6624604bb94a2",
              "versionType": "git"
            },
            {
              "lessThan": "37f11973c3eb72a5eb061082cad529bb6939c24f",
              "status": "affected",
              "version": "69b00b5bb23552d43e8bbed73ef6624604bb94a2",
              "versionType": "git"
            },
            {
              "lessThan": "c02d675e81468003e4f2253b616c53729070d712",
              "status": "affected",
              "version": "69b00b5bb23552d43e8bbed73ef6624604bb94a2",
              "versionType": "git"
            },
            {
              "lessThan": "140234b2380ffb8ffb0cfc46fee0e822f43adef7",
              "status": "affected",
              "version": "69b00b5bb23552d43e8bbed73ef6624604bb94a2",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/md/md.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.6"
            },
            {
              "lessThan": "5.6",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.110",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.52",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.110",
                  "versionStartIncluding": "5.6",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.52",
                  "versionStartIncluding": "5.6",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.6",
                  "versionStartIncluding": "5.6",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3-rc1",
                  "versionStartIncluding": "5.6",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmd/raid1: create serial pool adding rdev to array with serialize_policy=1\n\nThe following bug has been observed with kernel 7.1.3 after adding a new\nrdev to an existing RAID1 array with serialize_policy enabled:\n\n  Oops: 0002 [#1]\n  CPU: 0 UID: 0 PID: 19639 Comm: ext4lazyinit Not tainted 7.1.3-1-default\n  RIP: _raw_spin_lock_irqsave+0x27/0x50\n  CR2: 0000000000004960\n  Call Trace:\n   wait_for_serialization+0xb9/0x260 [raid1]\n   raid1_make_request+0x762/0xaff [raid1]\n   md_handle_request+0x1c9/0x2e0 [md_mod]\n\nThe raid1.c code calls wait_for_serialization() if the MD_SERIALIZE_POLICY\nis set, and wait_for_serialization assumes that rdev-\u003eserial is\ninitialized. Normally this will be the case for arrays that have\nthe serialize_policy sysfs attribute set to 1.\n\nBut when a new rdev is added to an existing array in bind_rdev_to_array(),\nthe condition at mddev_create_serial_pool() causes creation of rdev-\u003eserial\nto be skipped. Fix it."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-17T16:09:21.198Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/f9e4364449f7ca6917f3599eb32064dba5b7b147"
        },
        {
          "url": "https://git.kernel.org/stable/c/37f11973c3eb72a5eb061082cad529bb6939c24f"
        },
        {
          "url": "https://git.kernel.org/stable/c/c02d675e81468003e4f2253b616c53729070d712"
        },
        {
          "url": "https://git.kernel.org/stable/c/140234b2380ffb8ffb0cfc46fee0e822f43adef7"
        }
      ],
      "title": "md/raid1: create serial pool adding rdev to array with serialize_policy=1",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-90385",
    "datePublished": "2026-09-17T16:09:21.198Z",
    "dateReserved": "2026-09-11T19:38:34.809Z",
    "dateUpdated": "2026-09-17T16:09:21.198Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

GHSA-6JQ9-46P7-P377

CVE-2026-90385 (GCVE-0-2026-90385)

Tags

Sightings

Nomenclature

Related by attack behaviour