CVE-2024-47141: pinmux: Use sequential access to access desc->pinmux data

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2025-01-11 · updated 2026-10-30
Weakness: CWE-667

Description

In the Linux kernel, the following vulnerability has been resolved: pinmux: Use sequential access to access desc->pinmux data When two client of the same gpio call pinctrl_select_state() for the same functionality, we are seeing NULL pointer issue while accessing desc->mux_owner. Let's say two processes A, B executing in pin_request() for the same pin and process A updates the desc->mux_usecount but not yet updated the desc->mux_owner while process B see the desc->mux_usecount which got updated by A path and further executes strcmp and while accessing desc->mux_owner it crashes with NULL pointer. Serialize the access to mux related setting with a mutex lock. cpu0 (process A) cpu1(process B) pinctrl_select_state() { pinctrl_select_state() { pin_request() { pin_request() { ... .... } else { desc->mux_usecount++; desc->mux_usecount && strcmp(desc->mux_owner, owner)) { if (desc->mux_usecount > 1) return 0; desc->mux_owner = owner; } }

Affected products

Linux kernel: before 6.6.66; from 6.7 before 6.12.5 — fixed in 6.6.66, 6.12.5
Linux: 3.10 — fixed in 6.13

How to fix

Upgrade to a fixed version: Linux kernel 6.6.66, 6.12.5; Linux 6.13. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2024-47141 or the next vulnerability affects your stack