CVE-2024-56625

can: dev: can_set_termination(): allow sleeping GPIOs

MEDIUM
5.5
CVSS Score
Published: December 27, 2024 at 02:51 PM UTC
Updated: June 17, 2026 at 08:12 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: can: dev: can_set_termination(): allow sleeping GPIOs In commit 6e86a1543c37 ("can: dev: provide optional GPIO based termination support") GPIO based termination support was added. For no particular reason that patch uses gpiod_set_value() to set the GPIO. This leads to the following warning, if the systems uses a sleeping GPIO, i.e. behind an I2C port expander: | WARNING: CPU: 0 PID: 379 at /drivers/gpio/gpiolib.c:3496 gpiod_set_value+0x50/0x6c | CPU: 0 UID: 0 PID: 379 Comm: ip Not tainted 6.11.0-20241016-1 #1 823affae360cc91126e4d316d7a614a8bf86236c Replace gpiod_set_value() by gpiod_set_value_cansleep() to allow the use of sleeping GPIOs.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.15 ≤ v < 5.15.1745.15 ≤ v < 6.1.1205.15 ≤ v < 6.12.55.15 ≤ v < 6.135.15 ≤ v < 6.6.665.16 ≤ v < 6.1.1206.2 ≤ v < 6.6.666.7 ≤ v < 6.12.55.156.13 rc16e86a1543c378f2e8837ad88f361b7bf606c80f7
Vendor states this is fixed in 1ac442f25c19953d2f33b92549628b0aeac83db6 (fixed)
Vendor states this is fixed in 3b0c5bb437d31a9864f633b85cbc42d2f6c51c96 (fixed)
Vendor states this is fixed in 46637a608fb1ee871a0ad8bf70d917d5d95ac251 (fixed)
Vendor states this is fixed in ee1dfbdd8b4b6de85e96ae2059dc9c1bdb6b49b5 (fixed)
Vendor states this is fixed in faa0a1975a6fbce30616775216606eb8d6388ea1 (fixed)
Vendor states this is fixed in 5.15 (unaffected)
Vendor states this is fixed in 5.15.174 (unaffected)
Vendor states this is fixed in 6.1.120 (unaffected)
Vendor states this is fixed in 6.12.5 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Vendor states this is fixed in 6.6.66 (unaffected)

References (6)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/1ac442f25c19953d2f33b92549628b0aeac83db6
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/3b0c5bb437d31a9864f633b85cbc42d2f6c51c96
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/46637a608fb1ee871a0ad8bf70d917d5d95ac251
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/ee1dfbdd8b4b6de85e96ae2059dc9c1bdb6b49b5
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/faa0a1975a6fbce30616775216606eb8d6388ea1
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card