drm/i915/dpt: Treat the DPT BO as a framebuffer
Key facts
- Attack vector
- Local
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Partial Red Hat: 2 without a fix
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat.
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/i915/dpt: Treat the DPT BO as a framebuffer Currently i915_gem_object_is_framebuffer() doesn't treat the BO containing the framebuffer's DPT as a framebuffer itself. This means eg. that the shrinker can evict the DPT BO while leaving the actual FB BO bound, when the DPT is allocated from regular shmem. That causes an immediate oops during hibernate as we try to rewrite the PTEs inside the already evicted DPT obj. TODO: presumably this might also be the reason for the DPT related display faults under heavy memory pressure, but I'm still not sure how that would happen as the object should be pinned by intel_dpt_pin() while in active use by the display engine... (cherry picked from commit 779cb5ba64ec7df80675a956c9022929514f517a)
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Linux | Linux | 6.0 and later | 6.1.23, 6.2.10, 6.3 | Patch available | CNA |
- Linux VendorLinux Affected 6.0 and later Fixed in 6.1.23, 6.2.10, 6.3 Patch available CNA
CPE configurations NVD · 5
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 6.0 to before 6.1.23; 6.2 to before 6.2.10 | Vulnerable | Linux |
| cpe:2.3:o:linux:linux_kernel:6.3:rc1:*:*:*:*:*:* | 6.3 rc1 | Vulnerable | Linux |
| cpe:2.3:o:linux:linux_kernel:6.3:rc2:*:*:*:*:*:* | 6.3 rc2 | Vulnerable | Linux |
| cpe:2.3:o:linux:linux_kernel:6.3:rc3:*:*:*:*:*:* | 6.3 rc3 | Vulnerable | Linux |
| cpe:2.3:o:linux:linux_kernel:6.3:rc4:*:*:*:*:*:* | 6.3 rc4 | Vulnerable | Linux |
- cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* Versions 6.0 to before 6.1.23; 6.2 to before 6.2.10 Vulnerable ·Linux
- cpe:2.3:o:linux:linux_kernel:6.3:rc1:*:*:*:*:*:* Versions 6.3 rc1 Vulnerable ·Linux
- cpe:2.3:o:linux:linux_kernel:6.3:rc2:*:*:*:*:*:* Versions 6.3 rc2 Vulnerable ·Linux
- cpe:2.3:o:linux:linux_kernel:6.3:rc3:*:*:*:*:*:* Versions 6.3 rc3 Vulnerable ·Linux
- cpe:2.3:o:linux:linux_kernel:6.3:rc4:*:*:*:*:*:* Versions 6.3 rc4 Vulnerable ·Linux
Remediation
- Fix · CNA Linux (Linux) Fixed in 6.1.23, 6.2.10, 6.3
Vendor assessments
Red Hat
Red Hat rating: Low. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Red Hat Enterprise Linux 8 | Affected | No fix yet: Fix deferred |
| Red Hat Enterprise Linux 9 | Affected | No fix yet: Fix deferred |
Not affected: 3 products
- Red Hat Enterprise Linux 10
- Red Hat Enterprise Linux 6
- Red Hat Enterprise Linux 7
Timeline
- 2026-10-02 Threatist record created from CVE-2023-53378
- 2026-10-03 Alias added: GHSA-53wx-c6fx-gwfp
References
More Linux Kernel vulnerabilities
- TI-2025-26358 tls: fix handling of zero-length records on the rx_list KEVCVSS 3.1CRITICAL 9.8
- TI-2026-38352 netfilter: bridge: make ebt_snat ARP rewrite writable KEVCVSS 3.1HIGH 8.8
- TI-2013-05264 The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the… KEVCVSS 3.1HIGH 8.8
- TI-2022-00125 Integer overflow in kernel KEVCVSS 3.1HIGH 8.4
- TI-2013-01864 The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9… KEVCVSS 3.1HIGH 8.4
- TI-2021-05514 Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACE KEVCVSS 3.1HIGH 8.3
Sources
- CVE-2023-53378 · CVE Program
- CVE-2023-53378 · NVD
- FIRST EPSS
- GHSA-53wx-c6fx-gwfp · GitHub Advisory Database · CC BY 4.0
- CVE-2023-53378 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences