LiveActive security incident?Get immediate response
CVE Record

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 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel graphics driver cleanup bug in drm/tilcdc. During failed device initialization, the driver could run shutdown cleanup for resources that were not successfully registered, causing kernel warnings. The source bundle does not provide CVSS, business impact, or evidence of attacker exploitation.

Executive priority

Treat as low urgency unless your organization operates Linux devices using the tilcdc display driver. There is no cited exploitation evidence, no CVSS, and no described data-loss or remote compromise path, but fixed kernels should still be adopted through normal maintenance.

Technical view

tilcdc_fini() called drm_kms_helper_poll_fini() and drm_atomic_helper_shutdown() unconditionally. In probe deferral or failed probe paths, those helpers should only run after successful device registration. The fix rewrites cleanup using standard goto error handling so only initialized resources are unwound, and removes an is_registered flag.

Likely exposure

Exposure appears limited to Linux systems that include and exercise the drm/tilcdc driver. The affected-version metadata in the bundle is inconsistent and should be validated against the running kernel source, vendor kernel package, or referenced stable commits.

Exploitation context

The source bundle says this CVE is not in KEV and provides no evidence of active exploitation, public exploit code, privilege escalation, or remote attack paths. The described symptom is kernel warning output during probe deferral scenarios.

Researcher notes

The evidence supports a driver cleanup-order flaw, not a demonstrated security boundary bypass. The CVE record lacks CVSS, CWE, exploitability detail, and clear affected-version ranges. Validate impact by reviewing the exact kernel branch, tilcdc configuration, and whether the referenced commits are present.

Mitigation direction

  • Check Linux vendor or distribution advisories for CVE-2025-71141 guidance.
  • Update to a kernel build containing the referenced stable fixes.
  • Validate whether drm/tilcdc is built, loaded, or relevant in your environment.
  • If updates are unavailable, request vendor guidance for supported interim controls.

Validation and detection

  • Inventory kernels and kernel packages across affected device fleets.
  • Confirm whether the tilcdc DRM driver is enabled or present.
  • Compare kernel source or package changelogs against the referenced stable commits.
  • Review boot or kernel logs for tilcdc probe-deferral warnings.
  • Track remediation evidence in vulnerability management records.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-71141 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux69f03be1fa08a66735d53d92d3429c052540e3bf, 3c4babae3c4a1ae05f8f3f5f3d50c440ead7ca6a, 3c4babae3c4a1ae05f8f3f5f3d50c440ead7ca6a, 84021fa4cf190e257ae8b66d284cdb92e3fabe33, 6.6.2, 6.5.12unaffected
LinuxLinux6.7, 0, 6.6.120, 6.18.4, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.