CVE-2025-71141

drm/tilcdc: Fix removal actions in case of failed probe

MEDIUM
5.5
CVSS Score
Published: January 14, 2026 at 03:07 PM UTC
Updated: October 21, 2026 at 01:18 PM 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: drm/tilcdc: Fix removal actions in case of failed probe The drm_kms_helper_poll_fini() and drm_atomic_helper_shutdown() helpers should only be called when the device has been successfully registered. Currently, these functions are called unconditionally in tilcdc_fini(), which causes warnings during probe deferral scenarios. [ 7.972317] WARNING: CPU: 0 PID: 23 at drivers/gpu/drm/drm_atomic_state_helper.c:175 drm_atomic_helper_crtc_duplicate_state+0x60/0x68 ... [ 8.005820] drm_atomic_helper_crtc_duplicate_state from drm_atomic_get_crtc_state+0x68/0x108 [ 8.005858] drm_atomic_get_crtc_state from drm_atomic_helper_disable_all+0x90/0x1c8 [ 8.005885] drm_atomic_helper_disable_all from drm_atomic_helper_shutdown+0x90/0x144 [ 8.005911] drm_atomic_helper_shutdown from tilcdc_fini+0x68/0xf8 [tilcdc] [ 8.005957] tilcdc_fini [tilcdc] from tilcdc_pdev_probe+0xb0/0x6d4 [tilcdc] Fix this by rewriting the failed probe cleanup path using the standard goto error handling pattern, which ensures that cleanup functions are only called on successfully initialized resources. Additionally, remove the now-unnecessary is_registered flag.

Affected

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

6.5.12 ≤ v < 6.66.6.2 ≤ v < 6.6.1206.7.1 ≤ v < 6.18.43c4babae3c4a1ae05f8f3f5f3d50c440ead7ca6a6.196.19 rc16.19 rc26.19 rc36.19 rc46.19 rc56.19 rc66.19 rc76.19 rc86.5.126.6.26.769f03be1fa08a66735d53d92d3429c052540e3bf84021fa4cf190e257ae8b66d284cdb92e3fabe33
Vendor states this is fixed in 21e52dc7762908c3d499cfb493d1b8281fc1d3ab (fixed)
Vendor states this is fixed in 71be8825e83c90c1e020feb77b29e6a99629e642 (fixed)
Vendor states this is fixed in a585c7ef9cabda58088916baedc6573e9a5cd2a7 (fixed)
Vendor states this is fixed in 6.12.114 (unaffected)
Vendor states this is fixed in 6.18.4 (unaffected)
Vendor states this is fixed in 6.19 (unaffected)
Affected range stops below 6.6, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.120 (unaffected)
Vendor states this is fixed in 6.7 (unaffected)

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