CVE-2026-89500

In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Make cpu_buffer::free_page a buffer_data_read_page Discarding a cached reader page after a concurrent ring buffer resize uses the new global subbuf_order for the free_pages() call. This mismatched order may crashes the kernel or leaks memory because the cached page was allocated under the old size. Save the actual free_page order alongside the page address to ensure we always refer to the correct value and do not rely on the potentially stalled cpu_buffer->subbuf_order value. The simplest is to make free_page a buffer_data_read_page which already covers exactly what we need: a page address and a page order.

CVSS v3 7.8 HIGH

7.8^/10

CVSS v3 : HIGH

Vector :

Exploitability : 1.8 / Impact : 5.9

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact HIGH

Scope UNCHANGED

References

Link	Resource
https://git.kernel.org/stable/c/7a1fb95de5404134f8758c1295ce88986bdf117c
https://git.kernel.org/stable/c/a1dabe68fb53730bc0be60c5dbfd3f4c560084e7
https://git.kernel.org/stable/c/d787d509bdf6c88c85e095247daf7456cb7fb772

Configurations

No configuration.

History

No history.

Information

Published : 2026-09-11 20:19

Updated : 2026-09-13 07:17

NVD link : CVE-2026-89500

Mitre link : CVE-2026-89500

CVE.ORG link : CVE-2026-89500

JSON object : View

Products Affected

No product.

CWE

No CWE.

{"id": "CVE-2026-89500", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.8, "attackVector": "LOCAL", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 1.8}]}, "affected": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "affectedData": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "8e7b58c27b3c567316a51079b375b846f9223bba", "lessThan": "a1dabe68fb53730bc0be60c5dbfd3f4c560084e7", "versionType": "git"}, {"status": "affected", "version": "8e7b58c27b3c567316a51079b375b846f9223bba", "lessThan": "d787d509bdf6c88c85e095247daf7456cb7fb772", "versionType": "git"}, {"status": "affected", "version": "8e7b58c27b3c567316a51079b375b846f9223bba", "lessThan": "7a1fb95de5404134f8758c1295ce88986bdf117c", "versionType": "git"}], "programFiles": ["kernel/trace/ring_buffer.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "6.8"}, {"status": "unaffected", "version": "0", "lessThan": "6.8", "versionType": "semver"}, {"status": "unaffected", "version": "6.18.51", "versionType": "semver", "lessThanOrEqual": "6.18.*"}, {"status": "unaffected", "version": "7.2.4", "versionType": "semver", "lessThanOrEqual": "7.2.*"}, {"status": "unaffected", "version": "7.3-rc1", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["kernel/trace/ring_buffer.c"], "defaultStatus": "affected"}]}], "published": "2026-09-11T20:19:32.180", "references": [{"url": "https://git.kernel.org/stable/c/7a1fb95de5404134f8758c1295ce88986bdf117c", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/a1dabe68fb53730bc0be60c5dbfd3f4c560084e7", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/d787d509bdf6c88c85e095247daf7456cb7fb772", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Received", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nring-buffer: Make cpu_buffer::free_page a buffer_data_read_page\n\nDiscarding a cached reader page after a concurrent ring buffer resize\nuses the new global subbuf_order for the free_pages() call. This\nmismatched order may crashes the kernel or leaks memory because the cached\npage was allocated under the old size.\n\nSave the actual free_page order alongside the page address to ensure we\nalways refer to the correct value and do not rely on the potentially\nstalled cpu_buffer->subbuf_order value. The simplest is to make\nfree_page a buffer_data_read_page which already covers exactly what we\nneed: a page address and a page order."}], "lastModified": "2026-09-13T07:17:13.210", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}