Answer in brief
CVE-2025-71141 records a Unknown severity vulnerability in drm/tilcdc: Fix removal actions in case of failed probe. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 6.7 | Not reported |
| Linux/Linuxgeneric | >=69f03be1fa08a66735d53d92d3429c052540e3bf <21e52dc7762908c3d499cfb493d1b8281fc1d3ab || >=3c4babae3c4a1ae05f8f3f5f3d50c440ead7ca6a <28138ea7180c382b449ba9dce12fdec68880dea4 || >=3c4babae3c4a1ae05f8f3f5f3d50c440ead7ca6a <71be8825e83c90c1e020feb77b29e6a99629e642 || >=3c4babae3c4a1ae05f8f3f5f3d50c440ead7ca6a <a585c7ef9cabda58088916baedc6573e9a5cd2a7 || 84021fa4cf190e257ae8b66d284cdb92e3fabe33 || >=6.6.2 <6.6.120 || >=6.5.12 <6.6 | 21e52dc7762908c3d499cfb493d1b8281fc1d3ab, 28138ea7180c382b449ba9dce12fdec68880dea4, 71be8825e83c90c1e020feb77b29e6a99629e642, a585c7ef9cabda58088916baedc6573e9a5cd2a7, 6.6.120, 6.6 |
Published upstream
Jan 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
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.
Quoted source text, attributed separately from HOL analysis.