CVE-2025-38522 (GCVE-0-2025-38522)
Vulnerability from cvelistv5
Published
2025-08-16 11:12
Modified
2025-08-16 11:12
Severity ?
VLAI Severity ?
EPSS score ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
sched/ext: Prevent update_locked_rq() calls with NULL rq
Avoid invoking update_locked_rq() when the runqueue (rq) pointer is NULL
in the SCX_CALL_OP and SCX_CALL_OP_RET macros.
Previously, calling update_locked_rq(NULL) with preemption enabled could
trigger the following warning:
BUG: using __this_cpu_write() in preemptible [00000000]
This happens because __this_cpu_write() is unsafe to use in preemptible
context.
rq is NULL when an ops invoked from an unlocked context. In such cases, we
don't need to store any rq, since the value should already be NULL
(unlocked). Ensure that update_locked_rq() is only called when rq is
non-NULL, preventing calling __this_cpu_write() on preemptible context.
References
Impacted products
{ "containers": { "cna": { "affected": [ { "defaultStatus": "unaffected", "product": "Linux", "programFiles": [ "kernel/sched/ext.c" ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [ { "lessThan": "237c43037b336e36a49eb9f2daac1c7719ec7f8b", "status": "affected", "version": "18853ba782bef65fc81ef2b3370382e5b479c5eb", "versionType": "git" }, { "lessThan": "e14fd98c6d66cb76694b12c05768e4f9e8c95664", "status": "affected", "version": "18853ba782bef65fc81ef2b3370382e5b479c5eb", "versionType": "git" } ] }, { "defaultStatus": "affected", "product": "Linux", "programFiles": [ "kernel/sched/ext.c" ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [ { "status": "affected", "version": "6.15" }, { "lessThan": "6.15", "status": "unaffected", "version": "0", "versionType": "semver" }, { "lessThanOrEqual": "6.15.*", "status": "unaffected", "version": "6.15.8", "versionType": "semver" }, { "lessThanOrEqual": "*", "status": "unaffected", "version": "6.16", "versionType": "original_commit_for_fix" } ] } ], "cpeApplicability": [ { "nodes": [ { "cpeMatch": [ { "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionEndExcluding": "6.15.8", "versionStartIncluding": "6.15", "vulnerable": true }, { "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionEndExcluding": "6.16", "versionStartIncluding": "6.15", "vulnerable": true } ], "negate": false, "operator": "OR" } ] } ], "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsched/ext: Prevent update_locked_rq() calls with NULL rq\n\nAvoid invoking update_locked_rq() when the runqueue (rq) pointer is NULL\nin the SCX_CALL_OP and SCX_CALL_OP_RET macros.\n\nPreviously, calling update_locked_rq(NULL) with preemption enabled could\ntrigger the following warning:\n\n BUG: using __this_cpu_write() in preemptible [00000000]\n\nThis happens because __this_cpu_write() is unsafe to use in preemptible\ncontext.\n\nrq is NULL when an ops invoked from an unlocked context. In such cases, we\ndon\u0027t need to store any rq, since the value should already be NULL\n(unlocked). Ensure that update_locked_rq() is only called when rq is\nnon-NULL, preventing calling __this_cpu_write() on preemptible context." } ], "providerMetadata": { "dateUpdated": "2025-08-16T11:12:11.304Z", "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux" }, "references": [ { "url": "https://git.kernel.org/stable/c/237c43037b336e36a49eb9f2daac1c7719ec7f8b" }, { "url": "https://git.kernel.org/stable/c/e14fd98c6d66cb76694b12c05768e4f9e8c95664" } ], "title": "sched/ext: Prevent update_locked_rq() calls with NULL rq", "x_generator": { "engine": "bippy-1.2.0" } } }, "cveMetadata": { "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "assignerShortName": "Linux", "cveId": "CVE-2025-38522", "datePublished": "2025-08-16T11:12:11.304Z", "dateReserved": "2025-04-16T04:51:24.023Z", "dateUpdated": "2025-08-16T11:12:11.304Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "vulnerability-lookup:meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2025-38522\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-08-16T12:15:27.523\",\"lastModified\":\"2025-08-18T20:16:28.750\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nsched/ext: Prevent update_locked_rq() calls with NULL rq\\n\\nAvoid invoking update_locked_rq() when the runqueue (rq) pointer is NULL\\nin the SCX_CALL_OP and SCX_CALL_OP_RET macros.\\n\\nPreviously, calling update_locked_rq(NULL) with preemption enabled could\\ntrigger the following warning:\\n\\n BUG: using __this_cpu_write() in preemptible [00000000]\\n\\nThis happens because __this_cpu_write() is unsafe to use in preemptible\\ncontext.\\n\\nrq is NULL when an ops invoked from an unlocked context. In such cases, we\\ndon\u0027t need to store any rq, since the value should already be NULL\\n(unlocked). Ensure that update_locked_rq() is only called when rq is\\nnon-NULL, preventing calling __this_cpu_write() on preemptible context.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: sched/ext: Evitar llamadas a update_locked_rq() con rq NULL Evite invocar update_locked_rq() cuando el puntero de la cola de ejecuci\u00f3n (rq) sea NULL en las macros SCX_CALL_OP y SCX_CALL_OP_RET. Anteriormente, llamar a update_locked_rq(NULL) con la preempci\u00f3n habilitada podr\u00eda desencadenar la siguiente advertencia: ERROR: usar __this_cpu_write() en un contexto preemptible [00000000] Esto sucede porque __this_cpu_write() no es seguro para usar en un contexto preemptible. rq es NULL cuando se invoca una operaci\u00f3n desde un contexto desbloqueado. En tales casos, no necesitamos almacenar ninguna rq, ya que el valor ya deber\u00eda ser NULL (desbloqueado). Aseg\u00farese de que update_locked_rq() solo se llame cuando rq no sea NULL, lo que evita llamar a __this_cpu_write() en un contexto preemptible.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/237c43037b336e36a49eb9f2daac1c7719ec7f8b\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/e14fd98c6d66cb76694b12c05768e4f9e8c95664\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}" } }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- 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.
Loading…