CVE-2025-38049

x86/resctrl: Fix allocation of cleanest CLOSID on platforms with no monitors

State
Published
Severity
5.5 Medium
Published
Apr 18, 2025
Updated
May 11, 2026
Reserved
Apr 16, 2025

Read the record on cve.org

Description

In the Linux kernel, the following vulnerability has been resolved:

x86/resctrl: Fix allocation of cleanest CLOSID on platforms with no monitors

Commit

6eac36bb9eb0 ("x86/resctrl: Allocate the cleanest CLOSID by searching closid_num_dirty_rmid")

added logic that causes resctrl to search for the CLOSID with the fewest dirty cache lines when creating a new control group, if requested by the arch code. This depends on the values read from the llc_occupancy counters. The logic is applicable to architectures where the CLOSID effectively forms part of the monitoring identifier and so do not allow complete freedom to choose an unused monitoring identifier for a given CLOSID.

This support missed that some platforms may not have these counters. This causes a NULL pointer dereference when creating a new control group as the array was not allocated by dom_data_init().

As this feature isn't necessary on platforms that don't have cache occupancy monitors, add this to the check that occurs when a new control group is allocated.

Scores

CVSSScoreVectorSource
3.15.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HCISA-ADP

Weaknesses

Affected Products

ProductVersions
LinuxLinux
  • 6eac36bb9eb0349c983313c71692c19d50b56878 to before a8a1bcc27d4607227088d80483164289b5348293Affected
  • 6eac36bb9eb0349c983313c71692c19d50b56878 to before ed5addb55e403ad6598102bcf546e068ae01fef6Affected
  • 6eac36bb9eb0349c983313c71692c19d50b56878 to before 93a418fc61da13d1ee4047d4d1327990f7a2816aAffected
  • 6eac36bb9eb0349c983313c71692c19d50b56878 to before a121798ae669351ec0697c94f71c3a692b2a755bAffected
LinuxLinux
  • 6.9Affected
  • before 6.9Not affected
  • 6.12.23 through 6.12.*Not affected
  • 6.13.11 through 6.13.*Not affected
  • 6.14.2 through 6.14.*Not affected
  • 6.15 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.