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

Published Jul 25, 2026
·
Updated

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 cpumask 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 cpumask is empty causing the NUMA node ID query via cputonode() to be done with "nrcpuids" 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 Software

1 affected component
Linux Kernel

Event History

Jul 25, 2026
CVE Published
via MITRE·08:51 AM
Data Sourced
via MITRE·08:51 AM
Description
Data Sourced
via NVD·10:17 AM
Description

Frequently Asked Questions

1

What severity level is CVE-2026-64477?

CVE-2026-64477 is rated with a severity level of 24.

2

What is the primary issue addressed by CVE-2026-64477?

CVE-2026-64477 addresses out-of-bounds access while offlining a CPU when SNC is enabled in the Linux kernel.

3

How do I fix CVE-2026-64477?

To fix CVE-2026-64477, upgrade the Linux kernel to a version that has the vulnerability resolved.

4

Which software is affected by CVE-2026-64477?

CVE-2026-64477 affects the Linux Kernel.

5

What are the potential consequences of not addressing CVE-2026-64477?

Not addressing CVE-2026-64477 could lead to system instability or security vulnerabilities due to out-of-bounds access.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203