Medium 5.5Published Jan 14, 2026

CVE-2025-71141drm/tilcdc: Fix removal actions in case of failed probe

Updated under an hour ago (Oct 27, 2026, 10:50 PM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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.

CVSS: 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Modified
Record last updated: Oct 21, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	69f03be1fa08a66735d53d92d3429c052540e3bf builds before 21e52dc7762908c3d499cfb493d1b8281fc1d3ab; from 3c4babae3c4a1ae05f8f3f5f3d50c440ead7ca6a before 28138ea7180c382b449ba9dce12fdec68880dea4; from 3c4babae3c4a1ae05f8f3f5f3d50c440ead7ca6a before 71be8825e83c90c1e020feb77b29e6a99629e642; from 3c4babae3c4a1ae05f8f3f5f3d50c440ead7ca6a before a585c7ef9cabda58088916baedc6573e9a5cd2a7; 84021fa4cf190e257ae8b66d284cdb92e3fabe33; from 6.6.2 before 6.6.120; from 6.5.12 before 6.6	CNA record
linux linux_kernel linux:linux_kernel	from 6.5.12 before 6.6; from 6.6.2 before 6.6.120; from 6.7.1 before 6.18.4; 6.7; 6.19; 6.19; 6.19; 6.19; and 4 more ranges	NVD

References

References

https://git.kernel.org/stable/c/21e52dc7762908c3d499cfb493d1b8281fc1d3ab	patch
https://git.kernel.org/stable/c/28138ea7180c382b449ba9dce12fdec68880dea4
https://git.kernel.org/stable/c/71be8825e83c90c1e020feb77b29e6a99629e642	patch
https://git.kernel.org/stable/c/a585c7ef9cabda58088916baedc6573e9a5cd2a7	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.