CVE-2025-71141: drm/tilcdc: Fix removal actions in case of failed probe
In the Linux kernel, the following vulnerability has been resolved:
drm/tilcdc: Fix removal actions in case of failed probe
The drmkmshelperpollfini() and drmatomichelpershutdown() helpers should only be called when the device has been successfully registered. Currently, these functions are called unconditionally in tilcdcfini(), which causes warnings during probe deferral scenarios.
[ 7.972317] WARNING: CPU: 0 PID: 23 at drivers/gpu/drm/drmatomicstatehelper.c:175 drmatomichelpercrtcduplicatestate+0x60/0x68 ... [ 8.005820] drmatomichelpercrtcduplicatestate from drmatomicgetcrtcstate+0x68/0x108 [ 8.005858] drmatomicgetcrtcstate from drmatomichelperdisableall+0x90/0x1c8 [ 8.005885] drmatomichelperdisableall from drmatomichelpershutdown+0x90/0x144 [ 8.005911] drmatomichelpershutdown from tilcdcfini+0x68/0xf8 [tilcdc] [ 8.005957] tilcdcfini [tilcdc] from tilcdcpdevprobe+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 isregistered flag.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-71141?
CVE-2025-71141 has a moderate severity level affecting the Linux kernel.
How do I fix CVE-2025-71141?
To fix CVE-2025-71141, update your Linux kernel to the latest stable version where the vulnerability has been resolved.
What systems are affected by CVE-2025-71141?
CVE-2025-71141 affects systems running the Linux kernel, specifically those using the tilcdc driver.
Is CVE-2025-71141 exploitable remotely?
CVE-2025-71141 is not typically considered remotely exploitable, as it pertains to device management during kernel initialization.
When was CVE-2025-71141 disclosed?
CVE-2025-71141 was disclosed as part of ongoing patches to the Linux kernel.