{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.1.4-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  fuse-uring: fix data races on ring-\u003eready  On weakly-ordered architectures, the store to fiq-\u003eops can be reordered past the store to ring-\u003eready, allowing a CPU that sees ring-\u003eready == true via fuse_uring_ready() to dispatch requests through a stale fiq-\u003eops pointer. Upgrade the store to smp_store_release() and the load in fuse_uring_ready() to smp_load_acquire() so that the preceding WRITE_ONCE(fiq-\u003eops, ...) is visible to any CPU that observes ring-\u003eready == true.  Additionally, fuse_uring_do_register() publishes ring-\u003eready with WRITE_ONCE() but the fast-path check reads it with a plain load. This is a marked-vs-unmarked access that KCSAN will flag. Wrap it in READ_ONCE() to mark it without adding unnecessary ordering.  Also wrap the fc-\u003ering load in fuse_uring_ready() in READ_ONCE() to prevent the compiler from reloading it between the NULL check and the dereference.",
  "id": "DEBIAN-CVE-2026-64588",
  "modified": "2026-09-14T16:47:48.953852852Z",
  "published": "2026-08-06T08:16:34.123Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-64588"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-64588"
  ]
}