First published: Fri Apr 18 2025(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-38049 is classified as a moderate severity vulnerability in the Linux kernel.
To fix CVE-2025-38049, update your Linux kernel to the latest patched version provided by your distribution.
CVE-2025-38049 affects systems running vulnerable versions of the Linux kernel that utilize the x86 architecture.
The impact of CVE-2025-38049 can lead to improper allocation of resources impacting performance on systems with no monitors.
CVE-2025-38049 does not allow for remote exploitation, but it can affect system resource management under specific conditions.