CVE-2025-38632 Details
Description
In 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.
A vulnerability in the Linux kernel's pinmux handling can cause a null pointer dereference. This issue arises from a race condition where two clients of the same GPIO can interfere with each other, leading to an inconsistent state. The problem was partially addressed in a previous commit, but the fix was not complete. The vulnerability occurs when one process frees a pin while another is requesting it, causing the pin's ownership data to become corrupted. As a result, the pin appears to be in use but has no assigned owner, which can trigger a null pointer dereference when the pin is requested again.
The vulnerability has been fixed in the Linux kernel. Users should upgrade to the latest version where this issue has been addressed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/0b075c011032f88d1cfde3b45d6dcf08b44140eb | kernel.org | Patch |
| https://git.kernel.org/stable/c/22b585cbd67d14df3b91529d1b990661c300faa9 | kernel.org | Patch |
| https://git.kernel.org/stable/c/8434dec94e73cad527341d6280895191d949a702 | kernel.org | |
| https://git.kernel.org/stable/c/9b2a3e7189028aa7c4d53a84364f2ea9fb209787 | kernel.org | Patch |
| https://git.kernel.org/stable/c/9ea3f6b9a67be3476e331ce51cac316c2614a564 | kernel.org | Patch |
| https://git.kernel.org/stable/c/b7bd6e3971eb7f0e34d2fdce1b18b08094e0c804 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-362 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | [email protected] |
| CWE-476 | NULL Pointer Dereference | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.6.66, < 6.6.102 >= 6.12.5, < 6.12.42 >= 6.13, < 6.15.10 >= 6.16, < 6.16.1 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 5, 2026 | CVE Modified | CISA-ADP |
| Oct 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 26, 2025 | Initial Analysis | [email protected] |
| Aug 22, 2025 | New CVE Received | kernel.org |