cve-2025-38049
Vulnerability from cvelistv5
Published
2025-04-18 07:01
Modified
2025-04-18 07:01
Severity ?
EPSS score ?
Summary
x86/resctrl: Fix allocation of cleanest CLOSID on platforms with no monitors
References
{ "containers": { "cna": { "affected": [ { "defaultStatus": "unaffected", "product": "Linux", "programFiles": [ "arch/x86/kernel/cpu/resctrl/rdtgroup.c" ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [ { "lessThan": "a8a1bcc27d4607227088d80483164289b5348293", "status": "affected", "version": "6eac36bb9eb0349c983313c71692c19d50b56878", "versionType": "git" }, { "lessThan": "ed5addb55e403ad6598102bcf546e068ae01fef6", "status": "affected", "version": "6eac36bb9eb0349c983313c71692c19d50b56878", "versionType": "git" }, { "lessThan": "93a418fc61da13d1ee4047d4d1327990f7a2816a", "status": "affected", "version": "6eac36bb9eb0349c983313c71692c19d50b56878", "versionType": "git" }, { "lessThan": "a121798ae669351ec0697c94f71c3a692b2a755b", "status": "affected", "version": "6eac36bb9eb0349c983313c71692c19d50b56878", "versionType": "git" } ] }, { "defaultStatus": "affected", "product": "Linux", "programFiles": [ "arch/x86/kernel/cpu/resctrl/rdtgroup.c" ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [ { "status": "affected", "version": "6.9" }, { "lessThan": "6.9", "status": "unaffected", "version": "0", "versionType": "semver" }, { "lessThanOrEqual": "6.12.*", "status": "unaffected", "version": "6.12.23", "versionType": "semver" }, { "lessThanOrEqual": "6.13.*", "status": "unaffected", "version": "6.13.11", "versionType": "semver" }, { "lessThanOrEqual": "6.14.*", "status": "unaffected", "version": "6.14.2", "versionType": "semver" }, { "lessThanOrEqual": "*", "status": "unaffected", "version": "6.15-rc1", "versionType": "original_commit_for_fix" } ] } ], "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nx86/resctrl: Fix allocation of cleanest CLOSID on platforms with no monitors\n\nCommit\n\n 6eac36bb9eb0 (\"x86/resctrl: Allocate the cleanest CLOSID by searching closid_num_dirty_rmid\")\n\nadded logic that causes resctrl to search for the CLOSID with the fewest dirty\ncache lines when creating a new control group, if requested by the arch code.\nThis depends on the values read from the llc_occupancy counters. The logic is\napplicable to architectures where the CLOSID effectively forms part of the\nmonitoring identifier and so do not allow complete freedom to choose an unused\nmonitoring identifier for a given CLOSID.\n\nThis support missed that some platforms may not have these counters. This\ncauses a NULL pointer dereference when creating a new control group as the\narray was not allocated by dom_data_init().\n\nAs this feature isn\u0027t necessary on platforms that don\u0027t have cache occupancy\nmonitors, add this to the check that occurs when a new control group is\nallocated." } ], "providerMetadata": { "dateUpdated": "2025-04-18T07:01:30.421Z", "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux" }, "references": [ { "url": "https://git.kernel.org/stable/c/a8a1bcc27d4607227088d80483164289b5348293" }, { "url": "https://git.kernel.org/stable/c/ed5addb55e403ad6598102bcf546e068ae01fef6" }, { "url": "https://git.kernel.org/stable/c/93a418fc61da13d1ee4047d4d1327990f7a2816a" }, { "url": "https://git.kernel.org/stable/c/a121798ae669351ec0697c94f71c3a692b2a755b" } ], "title": "x86/resctrl: Fix allocation of cleanest CLOSID on platforms with no monitors", "x_generator": { "engine": "bippy-1.0.0" } } }, "cveMetadata": { "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "assignerShortName": "Linux", "cveId": "CVE-2025-38049", "datePublished": "2025-04-18T07:01:30.421Z", "dateReserved": "2025-04-16T04:51:23.979Z", "dateUpdated": "2025-04-18T07:01:30.421Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2025-38049\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-04-18T07:15:43.187\",\"lastModified\":\"2025-04-29T14:39:34.517\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nx86/resctrl: Fix allocation of cleanest CLOSID on platforms with no monitors\\n\\nCommit\\n\\n 6eac36bb9eb0 (\\\"x86/resctrl: Allocate the cleanest CLOSID by searching closid_num_dirty_rmid\\\")\\n\\nadded logic that causes resctrl to search for the CLOSID with the fewest dirty\\ncache lines when creating a new control group, if requested by the arch code.\\nThis depends on the values read from the llc_occupancy counters. The logic is\\napplicable to architectures where the CLOSID effectively forms part of the\\nmonitoring identifier and so do not allow complete freedom to choose an unused\\nmonitoring identifier for a given CLOSID.\\n\\nThis support missed that some platforms may not have these counters. This\\ncauses a NULL pointer dereference when creating a new control group as the\\narray was not allocated by dom_data_init().\\n\\nAs this feature isn\u0027t necessary on platforms that don\u0027t have cache occupancy\\nmonitors, add this to the check that occurs when a new control group is\\nallocated.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: x86/resctrl: Se corrige la asignaci\u00f3n del CLOSID m\u00e1s limpio en plataformas sin monitores. El commit 6eac36bb9eb0 (\\\"x86/resctrl: Asignar el CLOSID m\u00e1s limpio buscando closid_num_dirty_rmid\\\") a\u00f1adi\u00f3 l\u00f3gica que hace que resctrl busque el CLOSID con la menor cantidad de l\u00edneas de cach\u00e9 sucias al crear un nuevo grupo de control, si as\u00ed lo solicita el c\u00f3digo de la arquitectura. Esto depende de los valores le\u00eddos de los contadores llc_occupancy. Esta l\u00f3gica es aplicable a arquitecturas donde el CLOSID forma parte del identificador de monitorizaci\u00f3n y, por lo tanto, no permite total libertad para elegir un identificador de monitorizaci\u00f3n sin usar para un CLOSID determinado. Esta compatibilidad no tuvo en cuenta que algunas plataformas podr\u00edan no tener estos contadores. Esto provoca una desreferencia de puntero nulo al crear un nuevo grupo de control, ya que la matriz no fue asignada por dom_data_init(). Como esta funci\u00f3n no es necesaria en plataformas que no tienen monitores de ocupaci\u00f3n de cach\u00e9, agregue esto a la verificaci\u00f3n que se realiza cuando se asigna un nuevo grupo de control.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-476\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.9\",\"versionEndExcluding\":\"6.12.23\",\"matchCriteriaId\":\"10F3EB18-ACA3-4775-AC8D-C1CC227D2763\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.13\",\"versionEndExcluding\":\"6.13.11\",\"matchCriteriaId\":\"E7E864B0-8C00-4679-BA55-659B4C9C3AD3\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.14\",\"versionEndExcluding\":\"6.14.2\",\"matchCriteriaId\":\"FADAE5D8-4808-442C-B218-77B2CE8780A0\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/93a418fc61da13d1ee4047d4d1327990f7a2816a\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/a121798ae669351ec0697c94f71c3a692b2a755b\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/a8a1bcc27d4607227088d80483164289b5348293\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/ed5addb55e403ad6598102bcf546e068ae01fef6\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}" } }
Loading...
Loading...
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.