vulnerability
Ubuntu: (Multiple Advisories) (CVE-2024-26874): Linux kernel vulnerabilities
Severity | CVSS | Published | Added | Modified |
---|---|---|---|---|
4 | (AV:L/AC:L/Au:M/C:N/I:N/A:C) | 04/17/2024 | 07/01/2024 | 03/06/2025 |
Description
In the Linux kernel, the following vulnerability has been resolved:
drm/mediatek: Fix a null pointer crash in mtk_drm_crtc_finish_page_flip
It's possible that mtk_crtc->event is NULL in
mtk_drm_crtc_finish_page_flip().
pending_needs_vblank value is set by mtk_crtc->event, but in
mtk_drm_crtc_atomic_flush(), it's is not guarded by the same
lock in mtk_drm_finish_page_flip(), thus a race condition happens.
Consider the following case:
CPU1 CPU2
step 1:
mtk_drm_crtc_atomic_begin()
mtk_crtc->event is not null,
step 1:
mtk_drm_crtc_atomic_flush:
mtk_drm_crtc_update_config(
!!mtk_crtc->event)
step 2:
mtk_crtc_ddp_irq ->
mtk_drm_finish_page_flip:
lock
mtk_crtc->event set to null,
pending_needs_vblank set to false
unlock
pending_needs_vblank set to true,
step 2:
mtk_crtc_ddp_irq ->
mtk_drm_finish_page_flip called again,
pending_needs_vblank is still true
//null pointer
Instead of guarding the entire mtk_drm_crtc_atomic_flush(), it's more
efficient to just check if mtk_crtc->event is null before use.
Solution(s)
References
- CVE-2024-26874
- https://attackerkb.com/topics/CVE-2024-26874
- UBUNTU-USN-6816-1
- UBUNTU-USN-6817-1
- UBUNTU-USN-6817-2
- UBUNTU-USN-6817-3
- UBUNTU-USN-6820-1
- UBUNTU-USN-6820-2
- UBUNTU-USN-6821-1
- UBUNTU-USN-6821-2
- UBUNTU-USN-6821-3
- UBUNTU-USN-6821-4
- UBUNTU-USN-6828-1
- UBUNTU-USN-6871-1
- UBUNTU-USN-6878-1
- UBUNTU-USN-6892-1
- UBUNTU-USN-6896-1
- UBUNTU-USN-6896-2
- UBUNTU-USN-6896-3
- UBUNTU-USN-6896-4
- UBUNTU-USN-6896-5
- UBUNTU-USN-6919-1

Explore Exposure Command
Confidently identify and prioritize exposures from endpoint to cloud with full attack surface visibility and threat-aware risk context.