Vulnerabilities · 2024 · Linux
CVE-2024-47141
Linux Kernel vulnerability
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. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Linux Kernel runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/2da32aed4a97ca1d70fb8b77926f72f30ce5fb4b · Patch
- git.kernel.org/stable/c/5a3e85c3c397c781393ea5fb2f45b1f60f8a4e6e · Patch
- git.kernel.org/stable/c/c11e2ec9a780f54982a187ee10ffd1b810715c85 · Patch
- git.kernel.org/stable/c/d25e45dcf8e32062f7935e4ba154869043812ab6
- nvd.nist.gov/vuln/detail/CVE-2024-47141
- cve.org/CVERecord?id=CVE-2024-47141
More vulnerabilities in Linux products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.