CVE-2024-47141

What the bug is

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; } }

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/pinctrl/core.c
drivers/pinctrl/core.h
drivers/pinctrl/pinmux.c

What this is

PIN CONTROL SUBSYSTEMMAINTAINERS section matched on drivers/pinctrl/ · linux-gpio@vger.kernel.org · Maintained

Check it on the machine

grep -w CONFIG_PINCTRL /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.

• bookwormYnot built on amd64/cloud-amd64, ppc64el/powerpc64le
• trixieYnot built on amd64/cloud-amd64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, s390x/s390x
• forky, sidYnot built on amd64/cloud-amd64, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, s390x/s390x

Y

built in where it is built at all; some flavours do not build it

Build switch

CONFIG_PINCTRL

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published

2025-01-11 (21 months ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.17%, higher than 6.5% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

not yet assignedsource

Subsystem

drivers/pinctrl

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

Introduced	Fixed in	Commit
3.10	6.6.66	2da32aed4a97
3.10	6.12.5	c11e2ec9a780
3.10	6.13	5a3e85c3c397