{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  md/raid10: fix still_degraded being inverted in raid10_sync_request()  Commit fe6a19d40ceb (\"md/md-bitmap: merge md_bitmap_start_sync() into bitmap_operations\") converted still_degraded from int to bool, but inverted the assignment in the loop that checks whether the array will still be degraded after the current device is recovered: \"still_degraded = 1\" became \"still_degraded = false\".  As a result, recovering a device while another mirror is still missing calls md_bitmap_start_sync() with degraded == false, which clears bitmap bits that the still-missing device needs.  When that device is re-added, its bitmap-based recovery finds the bits already cleared and skips every region written while the array was degraded, so it is marked In_sync while holding stale data: silent corruption.  Reproducer (raid10 near=2, 4 disks, internal bitmap):  - fail and remove one disk of each mirror pair  - write to the degraded array  - re-add both disks and let recovery finish  - \"check\" reports mismatch_cnt=262272 after 256 MiB of degraded    writes and file contents differ; the second disk's \"recovery\"    completes in milliseconds because everything is skipped  The same conversion in raid1 got it right (still_degraded = true). Restore the correct value.",
  "id": "DEBIAN-CVE-2026-89558",
  "modified": "2026-09-14T08:47:33.419996188Z",
  "published": "2026-09-11T20:19:39.540Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-89558"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-89558"
  ]
}