Bug 2420366 (CVE-2023-53833) - CVE-2023-53833 kernel: drm/i915: Fix NULL ptr deref by checking new_crtc_state
Summary: CVE-2023-53833 kernel: drm/i915: Fix NULL ptr deref by checking new_crtc_state
Keywords:
Status: NEW
Alias: CVE-2023-53833
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-12-09 02:05 UTC by OSIDB Bzimport
Modified: 2026-02-12 15:12 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:2490 0 None None None 2026-02-11 00:16:11 UTC
Red Hat Product Errata RHSA-2026:2535 0 None None None 2026-02-11 11:51:05 UTC
Red Hat Product Errata RHSA-2026:2560 0 None None None 2026-02-11 14:34:09 UTC
Red Hat Product Errata RHSA-2026:2573 0 None None None 2026-02-11 16:30:47 UTC
Red Hat Product Errata RHSA-2026:2577 0 None None None 2026-02-11 17:03:59 UTC
Red Hat Product Errata RHSA-2026:2583 0 None None None 2026-02-11 17:45:03 UTC
Red Hat Product Errata RHSA-2026:2664 0 None None None 2026-02-12 15:12:39 UTC

Description OSIDB Bzimport 2025-12-09 02:05:59 UTC 
In the Linux kernel, the following vulnerability has been resolved:

drm/i915: Fix NULL ptr deref by checking new_crtc_state

intel_atomic_get_new_crtc_state can return NULL, unless crtc state wasn't
obtained previously with intel_atomic_get_crtc_state, so we must check it
for NULLness here, just as in many other places, where we can't guarantee
that intel_atomic_get_crtc_state was called.
We are currently getting NULL ptr deref because of that, so this fix was
confirmed to help.

(cherry picked from commit 1d5b09f8daf859247a1ea65b0d732a24d88980d8)
Comment 1 Alexander B 2025-12-09 16:21:30 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025120954-CVE-2023-53833-09d9@gregkh/T
Comment 7 errata-xmlrpc 2026-02-11 00:16:09 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.6 Telecommunications Update Service

Via RHSA-2026:2490 https://access.redhat.com/errata/RHSA-2026:2490
Comment 8 errata-xmlrpc 2026-02-11 11:51:02 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.8 Telecommunications Update Service

Via RHSA-2026:2535 https://access.redhat.com/errata/RHSA-2026:2535
Comment 9 errata-xmlrpc 2026-02-11 14:34:07 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions

Via RHSA-2026:2560 https://access.redhat.com/errata/RHSA-2026:2560
Comment 10 errata-xmlrpc 2026-02-11 16:30:45 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions

Via RHSA-2026:2573 https://access.redhat.com/errata/RHSA-2026:2573
Comment 11 errata-xmlrpc 2026-02-11 17:03:57 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions

Via RHSA-2026:2577 https://access.redhat.com/errata/RHSA-2026:2577
Comment 12 errata-xmlrpc 2026-02-11 17:45:02 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions

Via RHSA-2026:2583 https://access.redhat.com/errata/RHSA-2026:2583
Comment 13 errata-xmlrpc 2026-02-12 15:12:38 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.2 Advanced Update Support

Via RHSA-2026:2664 https://access.redhat.com/errata/RHSA-2026:2664
Note You need to log in before you can comment on or make changes to this bug.