CVE-2025-38049x86/resctrl: Fix allocation of cleanest CLOSID on platforms with no monitors
- 5.5MediumCVSS base score
- 0.27%Exploitation in 30 daysEPSS · top 81% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 2 days later
· 2 days later
Published
- 13 months later
· 13 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.27% · top 81% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 6eac36bb9eb0349c983313c71692c19d50b56878 – < a8a1bcc27d4607227088d80483164289b5348293
- affected 6eac36bb9eb0349c983313c71692c19d50b56878 – < ed5addb55e403ad6598102bcf546e068ae01fef6
- affected 6eac36bb9eb0349c983313c71692c19d50b56878 – < 93a418fc61da13d1ee4047d4d1327990f7a2816a
- affected 6eac36bb9eb0349c983313c71692c19d50b56878 – < a121798ae669351ec0697c94f71c3a692b2a755b
- affected 6.9
- unaffected < 6.9
- unaffected 6.12.23 – ≤ 6.12.*
- unaffected 6.13.11 – ≤ 6.13.*
- unaffected 6.14.2 – ≤ 6.14.*
- unaffected 6.15 – ≤ *
References
References4
- https://git.kernel.org/stable/c/a8a1bcc27d4607227088d80483164289b5348293 (opens in a new tab)
- https://git.kernel.org/stable/c/ed5addb55e403ad6598102bcf546e068ae01fef6 (opens in a new tab)
- https://git.kernel.org/stable/c/93a418fc61da13d1ee4047d4d1327990f7a2816a (opens in a new tab)
- https://git.kernel.org/stable/c/a121798ae669351ec0697c94f71c3a692b2a755b (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-11827 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-38049)Record last updated .