pinmux: Use sequential access to access desc->pinmux data

Summary

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; } }

Timeline

1. Jan 11, 2025, 12:25 PM UTCCVE published
2. Oct 1, 2025, 7:55 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Oct 30, 2026, 12:19 PM UTCRecord last updated

Affected versions

• Linux Linux

  Version range not reported

• Linux Linux

  3.10

• KernelLinux

  From 3.10.0 · fixed in 6.6.66; From 6.7.0 · fixed in 6.12.5

References 4