CVE-2025-38049
Last modified
CVE-2025-38049 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.9, < 6.12.23 |
| Linux | Linux Kernel | >= 6.13, < 6.13.11 |
| Linux | Linux Kernel | >= 6.14, < 6.14.2 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-38049?
How severe is CVE-2025-38049?
How do I fix CVE-2025-38049?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-38043In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38044In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38045In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38046Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2025-38047In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38048In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-3805A vulnerability classified as critical was found in sarriona…5.3
- CVE-2025-38050In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38051In the Linux kernel, the following vulnerability has been re…7
- CVE-2025-38052In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38053In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38054In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-38049?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
