Answer in brief
CVE-2025-38632 records a Medium severity (CVSS 4.7) vulnerability in pinmux: fix race causing mux_owner NULL with active mux_usecount. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d25e45dcf8e32062f7935e4ba154869043812ab6 <8434dec94e73cad527341d6280895191d949a702 || >=2da32aed4a97ca1d70fb8b77926f72f30ce5fb4b <9b2a3e7189028aa7c4d53a84364f2ea9fb209787 || >=c11e2ec9a780f54982a187ee10ffd1b810715c85 <9ea3f6b9a67be3476e331ce51cac316c2614a564 || >=5a3e85c3c397c781393ea5fb2f45b1f60f8a4e6e <b7bd6e3971eb7f0e34d2fdce1b18b08094e0c804 || >=5a3e85c3c397c781393ea5fb2f45b1f60f8a4e6e <22b585cbd67d14df3b91529d1b990661c300faa9 || >=5a3e85c3c397c781393ea5fb2f45b1f60f8a4e6e <0b075c011032f88d1cfde3b45d6dcf08b44140eb || >=6.6.66 <6.6.102 || >=6.12.5 <6.12.42 | 8434dec94e73cad527341d6280895191d949a702, 9b2a3e7189028aa7c4d53a84364f2ea9fb209787, 9ea3f6b9a67be3476e331ce51cac316c2614a564, b7bd6e3971eb7f0e34d2fdce1b18b08094e0c804, 22b585cbd67d14df3b91529d1b990661c300faa9, 0b075c011032f88d1cfde3b45d6dcf08b44140eb, 6.6.102, 6.12.42 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Aug 22, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 30, 2026
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.
Quoted source text, attributed separately from HOL analysis.