CVE-2025-71141

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-01-14. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

January 14, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 8, 2026
No patch confirmed yet.
generic

drm/tilcdc: Fix removal actions in case of failed probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a585c7ef9cabda58088916baedc6573e9a5cd2a7
generic

drm/tilcdc: Fix removal actions in case of failed probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/71be8825e83c90c1e020feb77b29e6a99629e642
generic

drm/tilcdc: Fix removal actions in case of failed probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21e52dc7762908c3d499cfb493d1b8281fc1d3ab

Patch Availability(17)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-110.110) @ noble2026-05-29ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1049.50~22.04.1) @ jammy2026-05-29ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1054.57+fips1) @ noble2026-05-29ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1047.48) @ noble2026-05-29ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2042.43) @ noble2026-05-29ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1052.56) @ noble2026-05-29ubuntu
ubuntulinux-tools-nvidia-64k-6.8 (6.8.0-1051.54) @ noble2026-05-29ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1054.57~22.04.1) @ jammy2026-05-29ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1051.54.1) @ noble2026-05-29ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-29.29) @ questing2026-05-29ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1022.22) @ noble2026-05-29ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1054.60) @ noble2026-05-29ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1054.60+fips1) @ noble2026-05-29ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-05-29ubuntu
ubuntulinux-tools-oracle-edge (6.17.0-1014.14~24.04.1) @ noble2026-05-29ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1015.15) @ questing2026-05-29ubuntu
linuxKernel @ 6.6.120—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (95 versions)6.18.5-1—

All Vendor Advisories

(19)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 145 total refreshes for this CVE.

  1. 2026-09-20 20:15 UTCEPSS rescore
  2. 2026-09-19 03:36 UTCOSV refresh
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-16 14:07 UTCEPSS rescore
  5. 2026-09-16 05:14 UTCEPSS rescore
  6. 2026-09-15 03:10 UTCEPSS rescore
  7. 2026-09-13 16:46 UTCEPSS rescore
  8. 2026-09-12 15:00 UTCEPSS rescore
  9. 2026-09-11 14:52 UTCEPSS rescore
  10. 2026-09-11 09:36 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:00 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-02 14:11 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-08-31 07:25 UTCOSV refresh
  18. 2026-08-30 01:21 UTCEPSS rescore
  19. 2026-08-28 21:40 UTCEPSS rescore
  20. 2026-08-27 14:24 UTCEPSS rescore
  21. 2026-08-26 14:45 UTCEPSS rescore
  22. 2026-08-25 13:48 UTCEPSS rescore
  23. 2026-08-24 14:16 UTCEPSS rescore
  24. 2026-08-23 00:18 UTCEPSS rescore
  25. 2026-08-21 23:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-19 17:03 UTCEPSS rescore
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-16 14:55 UTCEPSS rescore
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 14:15 UTCEG score recompute
  8. 2026-08-14 14:15 UTCVendor advisory
  9. 2026-08-14 14:15 UTCGHSA enrichment
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-12 13:50 UTCEPSS rescore
  12. 2026-08-11 13:42 UTCEPSS rescore
  13. 2026-08-10 23:59 UTCEPSS rescore
  14. 2026-08-09 19:45 UTCEG score recompute
  15. 2026-08-09 19:45 UTCVendor advisory
  16. 2026-08-09 19:45 UTCGHSA enrichment
  17. 2026-08-08 16:36 UTCEPSS rescore
  18. 2026-08-08 00:35 UTCEG score recompute
  19. 2026-08-08 00:35 UTCVendor advisory
  20. 2026-08-08 00:35 UTCGHSA enrichment
  21. 2026-08-07 16:27 UTCEPSS rescore
  22. 2026-08-06 13:46 UTCEPSS rescore
  23. 2026-08-06 05:45 UTCEG score recompute
  24. 2026-08-06 05:45 UTCVendor advisory
  25. 2026-08-06 05:44 UTCGHSA enrichment
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-04 10:37 UTCEPSS rescore
  28. 2026-08-03 10:35 UTCEPSS rescore
  29. 2026-08-02 23:24 UTCEG score recompute
  30. 2026-08-02 23:24 UTCVendor advisory
  31. 2026-08-02 23:24 UTCGHSA enrichment
  32. 2026-08-02 02:26 UTCEPSS rescore
  33. 2026-08-01 04:15 UTCEPSS rescore
  34. 2026-07-30 01:30 UTCEPSS rescore
  35. 2026-07-27 14:13 UTCEPSS rescore
  36. 2026-07-25 14:17 UTCEPSS rescore
  37. 2026-07-25 14:17 UTCEPSS rescore
  38. 2026-07-24 14:17 UTCEPSS rescore
  39. 2026-07-23 14:18 UTCEPSS rescore
  40. 2026-07-23 14:18 UTCEPSS rescore
  41. 2026-07-23 10:19 UTCOSV refresh
  42. 2026-07-23 03:03 UTCEG score recompute
  43. 2026-07-22 14:08 UTCEPSS rescore
  44. 2026-07-21 15:24 UTCEPSS rescore
  45. 2026-07-20 17:08 UTCEPSS rescore
  46. 2026-07-19 14:30 UTCEPSS rescore
  47. 2026-07-19 14:30 UTCEPSS rescore
  48. 2026-07-18 10:04 UTCEPSS rescore
  49. 2026-07-18 10:04 UTCEPSS rescore
  50. 2026-07-16 17:02 UTCEPSS rescore
  51. 2026-07-16 17:02 UTCEPSS rescore
  52. 2026-07-15 16:57 UTCEPSS rescore
  53. 2026-07-15 16:57 UTCEPSS rescore
  54. 2026-07-13 06:12 UTCEPSS rescore
  55. 2026-07-11 08:27 UTCEPSS rescore
  56. 2026-07-11 08:27 UTCEPSS rescore
  57. 2026-07-09 19:10 UTCEPSS rescore
  58. 2026-07-08 15:15 UTCEPSS rescore
  59. 2026-07-07 13:46 UTCEPSS rescore
  60. 2026-07-06 16:27 UTCEPSS rescore
  61. 2026-07-06 05:32 UTCOSV refresh
  62. 2026-07-06 02:23 UTCEPSS rescore
  63. 2026-07-05 02:30 UTCEPSS rescore
  64. 2026-07-05 02:30 UTCEPSS rescore
  65. 2026-07-04 06:31 UTCEPSS rescore
  66. 2026-07-04 06:31 UTCEPSS rescore
  67. 2026-07-01 15:06 UTCEPSS rescore
  68. 2026-06-30 23:22 UTCEPSS rescore
  69. 2026-06-30 23:22 UTCEPSS rescore
  70. 2026-06-28 14:07 UTCEPSS rescore
  71. 2026-06-28 14:07 UTCEPSS rescore
  72. 2026-06-27 03:08 UTCEPSS rescore
  73. 2026-06-25 13:49 UTCEPSS rescore
  74. 2026-06-25 13:49 UTCEPSS rescore
  75. 2026-06-22 14:25 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2025-71141?
CVE-2025-71141 is a medium vulnerability published on January 14, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/tilcdc: Fix removal actions in case of failed probe The drmkmshelperpollfini() and drmatomichelper_shutdown() helpers should only be called when the device has been successfully registered. Currently, these functions are called…
When was CVE-2025-71141 disclosed?
CVE-2025-71141 was first published in the National Vulnerability Database on January 14, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-71141 actively exploited?
CVE-2025-71141 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.7% of all scored CVEs.
What is the CVSS score of CVE-2025-71141?
CVE-2025-71141 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-71141?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71141, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71141

Explore →

Is Your Infrastructure Affected by CVE-2025-71141?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs