CVE-2026-64477

published 25 Jul 2026 · updated 14 Nov 2026

x86,fs/resctrl: Prevent out-of-bounds access while offlining CPU when SNC enabled

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6.12.96, Kernel 6.18.39, Kernel 7.1.4 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: x86,fs/resctrl: Prevent out-of-bounds access while offlining CPU when SNC enabled The architecture updates the cpu_mask in a domain's header to track which online CPUs are associated with the domain. When this mask becomes empty the architecture initiates offline of the domain that includes calling on resctrl fs to offline the domain. If it is a monitoring domain in which LLC occupancy is tracked resctrl fs forces the limbo handler to clear all busy RMID state associated with the domain. The limbo handler always reads the current event value associated with a busy RMID irrespective of it being checked as part of regular "is it still busy" check or whether it will be forced released anyway. When reading an RMID on a system with SNC enabled the "logical RMID" is converted to the "physical RMID" and this conversion requires the NUMA node ID of the resctrl monitoring domain that is in turn determined by querying the NUMA node ID of any CPU belonging to the monitoring domain. When the monitoring domain is going offline its cpu_mask is empty causing the NUMA node ID query via cpu_to_node() to be done with "nr_cpu_ids" as argument resulting in an out-of-bounds access. Refactor the limbo handler to skip reading the RMID when the RMID will just be forced to no longer be dirty in the domain anyway. Add a safety check to the architecture's RMID reader to protect against this scenario.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=6.11 <6.12.96, >=6.13 <6.18.39, >=6.19 <7.1.4, =7.2, >=e13db55b5a0d447dea63cde772c1078405bbbf96 <be1567992417dc92133e74126de7a6066c825ac9, >=e13db55b5a0d447dea63cde772c1078405bbbf96 <ebc300b7ee0c669fa76a7a8858298ff32e296103, >=e13db55b5a0d447dea63cde772c1078405bbbf96 <fc16126cc11d9f507130bf84ab137ee0938c900e, =6.11, >=e13db55b5a0d447dea63cde772c1078405bbbf96 <58c5ec23b1a238eb75cb0aba6f69d8f9e68ef0b26.12.96, 6.18.39, 7.1.4, be1567992417dc92133e74126de7a6066c825ac9, ebc300b7ee0c669fa76a7a8858298ff32e296103, fc16126cc11d9f507130bf84ab137ee0938c900e, 58c5ec23b1a238eb75cb0aba6f69d8f9e68ef0b2
linux-kernel: Kernel>=6.11.0 <6.12.96, >=6.13.0 <6.18.39, >=6.19.0 <7.1.46.12.96, 6.18.39, 7.1.4

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-64477 severity on Zeptric[![CVE-2026-64477](https://zeptric.io/badge/cve/CVE-2026-64477.svg)](https://zeptric.io/cve/CVE-2026-64477)