CVE-2024-47141

Kernel crash via unsynchronized pinmux ownership update

Published Jan 11, 2025 · Updated May 11, 2026

Race condition in Linux kernel pinmux code allows local users to crash the kernel by concurrently requesting the same GPIO pin. The pin_request() path increments desc->mux_usecount before setting desc->mux_owner, allowing a second request to dereference the still-NULL owner in strcmp(). Exploitation requires local low-privileged access and two clients targeting the same GPIO functionality; the documented consequence is a kernel crash.

CVSS severity5.5
Medium
EPSS probability0.17%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Race condition in Linux kernel pinmux code allows local users to crash the kernel by concurrently requesting the same GPIO pin. The pin_request() path increments desc->mux_usecount before setting desc->mux_owner, allowing a second request to dereference the still-NULL owner in strcmp(). Exploitation requires local low-privileged access and two clients targeting the same GPIO functionality; the documented consequence is a kernel crash.

The record

CVE
CVE-2024-47141
Published
Jan 11, 2025
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-667, T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jan 11, 2025CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=3.10
  2. Affected versionversion=42fed7ba44e4e8c1fb27b28ad14490cb1daff3c7 <2da32aed4a97ca1d70fb8b77926f72f30ce5fb4b
  3. Affected versionversion=42fed7ba44e4e8c1fb27b28ad14490cb1daff3c7 <5a3e85c3c397c781393ea5fb2f45b1f60f8a4e6e
  4. Affected versionversion=42fed7ba44e4e8c1fb27b28ad14490cb1daff3c7 <c11e2ec9a780f54982a187ee10ffd1b810715c85

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=3.10; version=42fed7ba44e4e8c1fb27b28ad14490cb1daff3c7 <2da32aed4a97ca1d70fb8b77926f72f30ce5fb4b; version=42fed7ba44e4e8c1fb27b28ad14490cb1daff3c7 <5a3e85c3c397c781393ea5fb2f45b1f60f8a4e6e; version=42fed7ba44e4e8c1fb27b28ad14490cb1daff3c7 <c11e2ec9a780f54982a187ee10ffd1b810715c85

Published CVSS scores

5.5CISA-ADPCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
5.5UbuntuCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
5.7SUSECVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
5.5NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.7SUSECVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-667Improper Locking
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo