{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-89503", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2026-09-11T19:38:34.715Z", "datePublished": "2026-09-11T19:43:51.357Z", "dateUpdated": "2026-09-11T19:43:51.357Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-09-11T19:43:51.357Z"}, "descriptions": [{"lang": "en", "value": "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->order might not match the actual allocated memory.\n\nUse bpage->order for the allocation to prevent this race."}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["kernel/trace/ring_buffer.c"], "versions": [{"version": "bce761d757452ba5eb77e11fecc37a04b67494e7", "lessThan": "2dc510957fe8fd098ab3c3147ebdf34d00cd2734", "status": "affected", "versionType": "git"}, {"version": "bce761d757452ba5eb77e11fecc37a04b67494e7", "lessThan": "53106e9262a310ef2c9a9321168c03705940c678", "status": "affected", "versionType": "git"}, {"version": "bce761d757452ba5eb77e11fecc37a04b67494e7", "lessThan": "e743527c5bfdceda1095bc0a9e596e2aebb6a9c3", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["kernel/trace/ring_buffer.c"], "versions": [{"version": "6.8", "status": "affected"}, {"version": "0", "lessThan": "6.8", "status": "unaffected", "versionType": "semver"}, {"version": "6.18.50", "lessThanOrEqual": "6.18.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.2.4", "lessThanOrEqual": "7.2.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.3-rc1", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.8", "versionEndExcluding": "6.18.50"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.8", "versionEndExcluding": "7.2.4"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.8", "versionEndExcluding": "7.3-rc1"}]}]}], "references": [{"url": "https://git.kernel.org/stable/c/2dc510957fe8fd098ab3c3147ebdf34d00cd2734"}, {"url": "https://git.kernel.org/stable/c/53106e9262a310ef2c9a9321168c03705940c678"}, {"url": "https://git.kernel.org/stable/c/e743527c5bfdceda1095bc0a9e596e2aebb6a9c3"}], "title": "ring-buffer: Fix subbuf resize race with ring_buffer_alloc_read_page()", "x_generator": {"engine": "bippy-1.2.0"}}}}

{}

{"affected": [{"affectedData": [{"defaultStatus": "unaffected", "product": "Linux", "programFiles": ["kernel/trace/ring_buffer.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"lessThan": "2dc510957fe8fd098ab3c3147ebdf34d00cd2734", "status": "affected", "version": "bce761d757452ba5eb77e11fecc37a04b67494e7", "versionType": "git"}, {"lessThan": "53106e9262a310ef2c9a9321168c03705940c678", "status": "affected", "version": "bce761d757452ba5eb77e11fecc37a04b67494e7", "versionType": "git"}, {"lessThan": "e743527c5bfdceda1095bc0a9e596e2aebb6a9c3", "status": "affected", "version": "bce761d757452ba5eb77e11fecc37a04b67494e7", "versionType": "git"}]}, {"defaultStatus": "affected", "product": "Linux", "programFiles": ["kernel/trace/ring_buffer.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"status": "affected", "version": "6.8"}, {"lessThan": "6.8", "status": "unaffected", "version": "0", "versionType": "semver"}, {"lessThanOrEqual": "6.18.*", "status": "unaffected", "version": "6.18.50", "versionType": "semver"}, {"lessThanOrEqual": "7.2.*", "status": "unaffected", "version": "7.2.4", "versionType": "semver"}, {"lessThanOrEqual": "*", "status": "unaffected", "version": "7.3-rc1", "versionType": "original_commit_for_fix"}]}], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "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->order might not match the actual allocated memory.\n\nUse bpage->order for the allocation to prevent this race."}], "id": "CVE-2026-89503", "lastModified": "2026-09-11T20:19:32.547", "metrics": {}, "published": "2026-09-11T20:19:32.547", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/2dc510957fe8fd098ab3c3147ebdf34d00cd2734"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/53106e9262a310ef2c9a9321168c03705940c678"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/e743527c5bfdceda1095bc0a9e596e2aebb6a9c3"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Received"}

{"bugzilla": {"description": "kernel: Linux kernel ring-buffer: Denial of Service due to subbuffer resize race condition", "id": "2532017", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2532017"}, "csaw": false, "cvss3": {"cvss3_base_score": "5.5", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "status": "draft"}, "cwe": "CWE-367", "details": ["A flaw was found in the Linux kernel's ring-buffer component. A race condition exists in the `ring_buffer_alloc_read_page()` function when it interacts with `ring_buffer_subbuf_order_set`. This can lead to an incorrect memory allocation where the buffer page's order (`bpage->order`) does not match the actual allocated memory. This mismatch could potentially cause system instability or a denial of service."], "name": "CVE-2026-89503", "package_state": [{"cpe": "cpe:/a:redhat:openshift:4", "fix_state": "Fix deferred", "package_name": "openshift/ose-rhel-coreos-8", "product_name": "Red Hat OpenShift Container Platform 4"}, {"cpe": "cpe:/a:redhat:openshift:4", "fix_state": "Fix deferred", "package_name": "openshift/ose-rhel-coreos-9", "product_name": "Red Hat OpenShift Container Platform 4"}], "public_date": "2026-09-11T19:43:51Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-89503\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-89503\nhttps://git.kernel.org/stable/c/2dc510957fe8fd098ab3c3147ebdf34d00cd2734\nhttps://git.kernel.org/stable/c/53106e9262a310ef2c9a9321168c03705940c678\nhttps://git.kernel.org/stable/c/e743527c5bfdceda1095bc0a9e596e2aebb6a9c3"], "threat_severity": "Moderate"}

{}