CVE-2024-47141pinmux: Use sequential access to access desc->pinmux data
- 5.5MediumCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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; } }
Timeline
ID reserved
By Linux
- 2 days later
· 2 days later
Published
- 22 months later
· 22 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (13 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 42fed7ba44e4e8c1fb27b28ad14490cb1daff3c7 – < d25e45dcf8e32062f7935e4ba154869043812ab6
- affected 42fed7ba44e4e8c1fb27b28ad14490cb1daff3c7 – < 2da32aed4a97ca1d70fb8b77926f72f30ce5fb4b
- affected 42fed7ba44e4e8c1fb27b28ad14490cb1daff3c7 – < c11e2ec9a780f54982a187ee10ffd1b810715c85
- affected 42fed7ba44e4e8c1fb27b28ad14490cb1daff3c7 – < 5a3e85c3c397c781393ea5fb2f45b1f60f8a4e6e
- affected 3.10
- unaffected < 3.10
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.66 – ≤ 6.6.*
- unaffected 6.12.5 – ≤ 6.12.*
- unaffected 6.13 – ≤ *
References
References4
- https://git.kernel.org/stable/c/d25e45dcf8e32062f7935e4ba154869043812ab6 (opens in a new tab)
- https://git.kernel.org/stable/c/2da32aed4a97ca1d70fb8b77926f72f30ce5fb4b (opens in a new tab)
- https://git.kernel.org/stable/c/c11e2ec9a780f54982a187ee10ffd1b810715c85 (opens in a new tab)
- https://git.kernel.org/stable/c/5a3e85c3c397c781393ea5fb2f45b1f60f8a4e6e (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-42874 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-47141)Record last updated .