CVE-2025-38632
MediumIn the Linux kernel, the following vulnerability has been resolved: pinmux: fix race causing mux_owner NULL with active mux_usecount commit 5a3e85c3c397 ("pinmux: Use sequential access to access desc->pinmux data") tried to address the issue when two client of the same gpio calls pinctrl_select_state() for the same functionality, was resulting in NULL pointer issue while accessing desc->mux_owner. However, issue was not completely fixed due to the way it was handled and it can still result in the same NULL pointer. The issue occurs due to the following interleaving: cpu0 (process A) cpu1 (process B) pin_request() { pin_free() { mutex_lock() desc->mux_usecount--; //becomes 0 .. mutex_unlock() mutex_lock(desc->mux) desc->mux_usecount++; // becomes 1 desc->mux_owner = owner; mutex_unlock(desc->mux) mutex_lock(desc->mux) desc->mux_owner = NULL; mutex_unlock(desc->mux) This sequence leads to a state where the pin appears to be in use (`mux_usecount == 1`) but has no owner (`mux_owner == NULL`), which can cause NULL pointer on next pin_request on the same pin. Ensure that updates to mux_usecount and mux_owner are performed atomically under the same lock. Only clear mux_owner when mux_usecount reaches zero and no new owner has been assigned.
CVSS 3.1 score
4.7
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness type
CWE-362CVE-2025-38632 is a Race Condition vulnerability
What is Race Condition?
The product contains a code sequence that can run concurrently with other code, creating unexpected states. Learn more on MITRE CWE
Affected versions
Linux kernel versions
6.6.66,
6.12.5,
6.13
and later are affected. Fixed in
6.6.102,
6.12.42,
6.15.10,
6.16.1,
6.17
and their respective stable series.
References
The following references provide additional information about CVE-2025-38632 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
PatchKernel patch commithttps://git.kernel.org/stable/c/0b075c011032f88d1cfde3b45d6dcf08b44140eb
-
PatchKernel patch commithttps://git.kernel.org/stable/c/22b585cbd67d14df3b91529d1b990661c300faa9
-
PatchKernel patch commithttps://git.kernel.org/stable/c/9b2a3e7189028aa7c4d53a84364f2ea9fb209787
Frequently asked questions
-
What is CVE-2025-38632?
CVE-2025-38632 is a Medium severity Linux kernel vulnerability with a CVSS score of 4.7 out of 10 , classified as a Race Condition flaw (CWE-362) . It affects Linux kernel versions from 6.6.66 onward and has been patched in 6.6.102, 6.12.42, 6.15.10 and others. CVE-2025-38632 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2025-38632?
CVE-2025-38632 has a CVSS score of 4.7 out of 10, rated Medium severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H. -
Is there a patch available for CVE-2025-38632?
Yes — CVE-2025-38632 has been patched. Fixed versions include 6.6.102, 6.12.42, 6.15.10 and others. If you are running Linux kernel 6.6.66 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2025-38632 actively exploited?
No — CVE-2025-38632 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
-
What is Race Condition (CWE-362)?
The product contains a code sequence that can run concurrently with other code, creating unexpected states. View CWE-362 on MITRE CWE →