Answer in brief
CVE-2024-47141 records a Medium severity (CVSS 5.5) vulnerability in pinmux: Use sequential access to access desc->pinmux data. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=42fed7ba44e4e8c1fb27b28ad14490cb1daff3c7 <d25e45dcf8e32062f7935e4ba154869043812ab6 || >=42fed7ba44e4e8c1fb27b28ad14490cb1daff3c7 <2da32aed4a97ca1d70fb8b77926f72f30ce5fb4b || >=42fed7ba44e4e8c1fb27b28ad14490cb1daff3c7 <c11e2ec9a780f54982a187ee10ffd1b810715c85 || >=42fed7ba44e4e8c1fb27b28ad14490cb1daff3c7 <5a3e85c3c397c781393ea5fb2f45b1f60f8a4e6e | d25e45dcf8e32062f7935e4ba154869043812ab6, 2da32aed4a97ca1d70fb8b77926f72f30ce5fb4b, c11e2ec9a780f54982a187ee10ffd1b810715c85, 5a3e85c3c397c781393ea5fb2f45b1f60f8a4e6e |
| Linux/Linuxgeneric | 3.10 | Not reported |
Published upstream
Jan 11, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 30, 2026
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; } }
Quoted source text, attributed separately from HOL analysis.