{
  "affected": [
    {
      "ranges": [
        {
          "events": [
            {
              "introduced": "bce761d757452ba5eb77e11fecc37a04b67494e7"
            },
            {
              "fixed": "2dc510957fe8fd098ab3c3147ebdf34d00cd2734"
            },
            {
              "fixed": "53106e9262a310ef2c9a9321168c03705940c678"
            },
            {
              "fixed": "e743527c5bfdceda1095bc0a9e596e2aebb6a9c3"
            }
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "type": "GIT"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Linux",
        "name": "Kernel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "6.8.0"
            },
            {
              "fixed": "6.18.50"
            }
          ],
          "type": "ECOSYSTEM"
        },
        {
          "events": [
            {
              "introduced": "6.19.0"
            },
            {
              "fixed": "7.2.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89503.json"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nring-buffer: Fix subbuf resize race with ring_buffer_alloc_read_page()\n\nring_buffer_alloc_read_page() is racy with ring_buffer_subbuf_order_set,\nit can allocate a reader page with an outdated order. This isn't a big\nissue, the user can still re-allocate a new reader page and try again.\n\nHowever, what is more problematic is if the value of subbuf_order\nchanges in the middle of ring_buffer_alloc_read_page(). In that case,\nbpage-\u003eorder might not match the actual allocated memory.\n\nUse bpage-\u003eorder for the allocation to prevent this race.",
  "id": "CVE-2026-89503",
  "modified": "2026-09-13T03:30:32.671382489Z",
  "published": "2026-09-11T19:43:51.357Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/2dc510957fe8fd098ab3c3147ebdf34d00cd2734"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/53106e9262a310ef2c9a9321168c03705940c678"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e743527c5bfdceda1095bc0a9e596e2aebb6a9c3"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89503.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89503"
    },
    {
      "type": "PACKAGE",
      "url": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
    }
  ],
  "schema_version": "1.9.0",
  "summary": "ring-buffer: Fix subbuf resize race with ring_buffer_alloc_read_page()"
}