PT-2026-52238 · Linux · Linux
Publicado
2026-06-25
·
Atualizado
2026-06-25
·
CVE-2026-53142
Nenhuma
Não há classificações de severidade ou métricas disponíveis. Quando houver, atualizaremos as informações correspondentes na página.
In the Linux kernel, the following vulnerability has been resolved:
drm/xe/display: fix oops in suspend/shutdown without display
The xe driver keeps track of whether to probe display, and whether
display hardware is there, using xe->info.probe display. It gets set to
false if there's no display after intel display device probe(). However,
the display may also be disabled via fuses, detected at a later time in
intel display device info runtime init().
In this case, the xe driver does for each intel crtc() on uninitialized
mode config in xe display flush cleanup work(), leading to a NULL
pointer dereference, and generally calls display code with display info
cleared.
Check for intel display device present() after
intel display device info runtime init(), and reset
xe->info.probe display as necessary. Also do unset display features()
for completeness, although display runtime init has already done
that. This will need to be unified across all cases later.
Move intel display device info runtime init() call slightly earlier,
similar to i915, to avoid a bunch of unnecessary setup for no display
cases.
Note #1: The xe driver has no business doing low level display plumbing
like for each intel crtc() to begin with. It all needs to happen in
display code.
Note #2: The actual bug is present already in commit 44e694958b95
("drm/xe/display: Implement display support"), but the oops was likely
introduced later at commit ddf6492e0e50 ("drm/xe/display: Make display
suspend/resume work on discrete").
(cherry picked from commit 7c3eb9f47533220888a67266448185fd0775d4da)
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾
Identificadores relacionados
Produtos afetados
Linux