ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2023-53571

In the Linux kernel, the following vulnerability has been resolved: drm/i915: Make intel_get_crtc_new_encoder() less oopsy The point of the WARN was to print something, not oops st

Published Oct 4, 2025 · catalog updated May 11, 2026 · Linux Linux

Check this week

CVE-2023-53571 is not in CISA KEV. FIRST estimates a 15.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
None0.0
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
15.00%
Remediation
Version ranges on file
Affected products
vendor Linux Linux 3a47ae201e074945bbde0b088e4c1215c07f4d75 <780f303233c35eeb5132e3ee1cbc8f4cebe86dd2

In the Linux kernel, the following vulnerability has been resolved: drm/i915: Make intel_get_crtc_new_encoder() less oopsy The point of the WARN was to print something, not oops straight up. Currently that is precisely what happens if we can't find the connector for the crtc in the atomic state. Get the dev pointer from the atomic state instead of the potentially NULL encoder to avoid that. (cherry picked from commit 3b6692357f70498f617ea1b31a0378070a0acf1c)

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor Linux Linux 3a47ae201e074945bbde0b088e4c1215c07f4d75 <780f303233c35eeb5132e3ee1cbc8f4cebe86dd23a47ae201e074945bbde0b088e4c1215c07f4d75 <780f303233c35eeb5132e3ee1cbc8f4cebe86dd2

How to fix CVE-2023-53571

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2023-53571 is not in CISA KEV. FIRST estimates a 15.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.

Which versions are affected?

Compare what you have installed with Linux Linux 3a47ae201e074945bbde0b088e4c1215c07f4d75 <780f303233c35eeb5132e3ee1cbc8f4cebe86dd2 3a47ae201e074945bbde0b088e4c1215c07f4d75 <780f303233c35eeb5132e3ee1cbc8f4cebe86dd2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 15.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 4, 2025 · EUVD

    Detected

    In the Linux kernel, the following vulnerability has been resolved: drm/i915: Make intel_get_crtc_new_encoder() less oopsy The point of the WARN was to print something, not oops straight up. Currently that is precisely what happens if we can't find the connector for the crtc in the atomic state. Get the dev pointer from the atomic state instead of the potentially NULL encoder to avoid that. (cherr

  2. May 11, 2026 · EUVD

    Updated

    In the Linux kernel, the following vulnerability has been resolved: drm/i915: Make intel_get_crtc_new_encoder() less oopsy The point of the WARN was to print something, not oops straight up. Currently that is precisely what happens if we can't find the connector for the crtc in the atomic state. Get the dev pointer from the atomic state instead of the potentially NULL encoder to avoid that. (cherr

Sources

  • CVE.orgVulnerability recordCVE-2023-53571

    Official CVE identifier

    cve.org
  • EUVDVulnerability recordEUVD-2025-32288

    In the Linux kernel, the following vulnerability has been resolved: drm/i915: Make intel_get_crtc_new_encoder() less oopsy The point of the WARN was to print something, not oops straight up. Currently that is precisely what happens if we can't find the connector for the crtc in t

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog May 11, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.