DEBIAN-CVE-2024-47141
- Source
- https://security-tracker.debian.org/tracker/CVE-2024-47141
- Import Source
- https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2024-47141.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/DEBIAN-CVE-2024-47141
- Upstream
- Published
- 2025-01-11T13:15:21Z
- Modified
- 2025-09-19T06:11:07Z
- Summary
- [none]
- Details
-
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 pinctrlselectstate() for the same functionality, we are seeing NULL pointer issue while accessing desc->muxowner. Let's say two processes A, B executing in pinrequest() for the same pin and process A updates the desc->muxusecount but not yet updated the desc->muxowner while process B see the desc->muxusecount which got updated by A path and further executes strcmp and while accessing desc->muxowner it crashes with NULL pointer. Serialize the access to mux related setting with a mutex lock. cpu0 (process A) cpu1(process B) pinctrlselectstate() { pinctrlselectstate() { pinrequest() { pinrequest() { ... .... } else { desc->muxusecount++; desc->muxusecount && strcmp(desc->muxowner, owner)) { if (desc->muxusecount > 1) return 0; desc->mux_owner = owner; } }
- References
Affected packages
Debian:13 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source
Debian:14 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source