GHSA-5MQ8-R2RM-Q3GQ

Vulnerability from github – Published: 2026-05-27 15:33 – Updated: 2026-05-27 15:33
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

md/md-llbitmap: skip reading rdevs that are not in_sync

When reading bitmap pages from member disks, the code iterates through all rdevs and attempts to read from the first available one. However, it only checks for raid_disk assignment and Faulty flag, missing the In_sync flag check.

This can cause bitmap data to be read from spare disks that are still being rebuilt and don't have valid bitmap information yet. Reading stale or uninitialized bitmap data from such disks can lead to incorrect dirty bit tracking, potentially causing data corruption during recovery or normal operation.

Add the In_sync flag check to ensure bitmap pages are only read from fully synchronized member disks that have valid bitmap data.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-46045"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-27T14:17:23Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmd/md-llbitmap: skip reading rdevs that are not in_sync\n\nWhen reading bitmap pages from member disks, the code iterates through\nall rdevs and attempts to read from the first available one. However,\nit only checks for raid_disk assignment and Faulty flag, missing the\nIn_sync flag check.\n\nThis can cause bitmap data to be read from spare disks that are still\nbeing rebuilt and don\u0027t have valid bitmap information yet. Reading\nstale or uninitialized bitmap data from such disks can lead to\nincorrect dirty bit tracking, potentially causing data corruption\nduring recovery or normal operation.\n\nAdd the In_sync flag check to ensure bitmap pages are only read from\nfully synchronized member disks that have valid bitmap data.",
  "id": "GHSA-5mq8-r2rm-q3gq",
  "modified": "2026-05-27T15:33:22Z",
  "published": "2026-05-27T15:33:22Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-46045"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3115fa2f62970d98f2a639145fb8e2767db8bbf9"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7701e68b5072faa03a8f30b4081dc16df9092381"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/98623c7e2a51eab1833c8628d33fa9c6ef3ce325"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…