CVE-2025-38632
pinmux: fix race causing mux_owner NULL with active mux_usecount
Reported by linux · Published August 22, 2025
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | b7bd6e3971eb7f0e34d2fdce1b18b08094e0c804, 9ea3f6b9a67be3476e331ce51cac316c2614a564, 9b2a3e7189028aa7c4d53a84364f2ea9fb209787, 8434dec94e73cad527341d6280895191d949a702, 6.13, 22b585cbd67d14df3b91529d1b990661c300faa9 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | d25e45dcf8e32062f7935e4ba154869043812ab6, 2da32aed4a97ca1d70fb8b77926f72f30ce5fb4b, c11e2ec9a780f54982a187ee10ffd1b810715c85 |
| Linux | Linux | 6.13, 0, 6.6.102 |
| Linux | Linux | 5a3e85c3c397c781393ea5fb2f45b1f60f8a4e6e, *, 2da32aed4a97ca1d70fb8b77926f72f30ce5fb4b |
| amazon:2023 | kernel-livepatch-6.12.46-66.121 | 0 |
| amazon:2023 | kernel6.12-tools | 0 |
| amazon:2023 | kernel6.12-tools-devel | 0 |
| linux | linux_kernel | 6.13, 6.6.66, 6.12.5 |
| amazon:2023 | kernel6.12-libbpf-static | 0 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | bpftool6.12 | 0 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| amazon:2023 | kernel6.12-libbpf-devel | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| amazon:2023 | kernel6.12-modules-extra-common | 0 |
| amazon:2023 | perf6.12 | 0 |
| amazon:2023 | kernel6.12-devel | 0 |
| amazon:2023 | kernel6.12-libbpf | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
Timeline
- Aug 22, 2025 Coalition ESS Score (9 in total, the first dated here)
- Aug 22, 2025 CVE Published
- Aug 23, 2025 EPSS Score (30 in total, the first dated here)
- Oct 12, 2025 PoC Published (10 in total, the first dated here)
- Dec 15, 2025 Security Advisory (223 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (175 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38632
vulnetix vdb fixes CVE-2025-38632
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38632/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart