CVE-2024-26874 json
drm/mediatek: Fix a null pointer crash in mtk_drm_crtc_finish_page_flip
published 2024-04-17 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-24136
- cvss
- 4.7
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 4.19.311, 5.4.273, 5.10.214, 5.15.153, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 6.9
- linux Debian 12 6.1.85-1
- linux Debian 14, Debian 13 6.7.12-1
debian advisories DEBIAN-CVE-2024-26874
- linux Ubuntu 20.04 LTS 5.4.0-189.209
- linux Ubuntu 22.04 LTS 5.15.0-112.122
- linux Ubuntu 24.04 LTS 6.8.0-35.35
- linux-aws Ubuntu 20.04 LTS 5.4.0-1128.138
- linux-aws Ubuntu 22.04 LTS 5.15.0-1063.69
- linux-aws Ubuntu 24.04 LTS 6.8.0-1009.9
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1132.141
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1062.70
ubuntu advisories UBUNTU-CVE-2024-26874
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- dtb-aarch64 openSUSE Leap 15.5 5.14.21-150500.55.68.1
- kernel-64kb SLE Module for Basesystem 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.68.1
- kernel-syms SLE Module for Development Tools 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.68.1
- kernel-obs-qa openSUSE Leap 15.5 5.14.21-150500.55.68.1
- kernel-source SLE Module for Development Tools 15 SP5, SLE Module for Basesystem 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.68.1
- kernel-default SLE Workstation Extension 15 SP5, SLE Module for Legacy 15 SP5, SLE Module for Basesystem 15 SP5 +4 more 5.14.21-150500.55.68.1
- kernel-kvmsmall openSUSE Leap 15.5 5.14.21-150500.55.68.1
- kernel-zfcpdump SLE Module for Basesystem 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.68.1
suse advisories SUSE-SU-2024:2190-1SUSE-SU-2024:2184-1SUSE-SU-2024:2019-1SUSE-SU-2024:2008-1SUSE-SU-2024:1983-1SUSE-SU-2024:1979-1
- git.kernel.org/stable/c/accdac6b71d5a2b84040c3d2234f53a60edc398e commit
- git.kernel.org/stable/c/dfde84cc6c589f2a9f820f12426d97365670b731 commit
- git.kernel.org/stable/c/4688be96d20ffa49d2186523ee84f475f316fd49 commit
- git.kernel.org/stable/c/9beec711a17245b853d64488fd5b739031612340 commit
- git.kernel.org/stable/c/d2bd30c710475b2e29288827d2c91f9e6e2b91d7 commit
- git.kernel.org/stable/c/a3dd12b64ae8373a41a216a0b621df224210860a commit
- git.kernel.org/stable/c/9acee29a38b4d4b70f1f583e5ef9a245db4db710 commit
- git.kernel.org/stable/c/3fc88b246a2fc16014e374040fc15af1d3752535 commit
- git.kernel.org/stable/c/c958e86e9cc1b48cac004a6e245154dfba8e163b commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-26874 updated cvss 4.4
kernel: drm/mediatek: Fix a null pointer crash in mtk_drm_crtc_finish_page_flip
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
- Technology feeds
References
-
git.kernel.org
/stable/c/accdac6b71d5a2b84040c3d2234f53a60edc398e
mailing-list, patch
-
git.kernel.org
/stable/c/dfde84cc6c589f2a9f820f12426d97365670b731
mailing-list, patch
-
git.kernel.org
/stable/c/4688be96d20ffa49d2186523ee84f475f316fd49
mailing-list, patch
-
git.kernel.org
/stable/c/9beec711a17245b853d64488fd5b739031612340
mailing-list, patch
-
git.kernel.org
/stable/c/d2bd30c710475b2e29288827d2c91f9e6e2b91d7
mailing-list, patch
-
git.kernel.org
/stable/c/a3dd12b64ae8373a41a216a0b621df224210860a
mailing-list, patch
-
git.kernel.org
/stable/c/9acee29a38b4d4b70f1f583e5ef9a245db4db710
mailing-list, patch
-
git.kernel.org
/stable/c/3fc88b246a2fc16014e374040fc15af1d3752535
mailing-list, patch
-
git.kernel.org
/stable/c/c958e86e9cc1b48cac004a6e245154dfba8e163b
mailing-list, patch
-
lists.debian.org
/debian-lts-announce/2024/06/msg00017.html
mailing-list
-
lists.debian.org
/debian-lts-announce/2024/06/msg00020.html
mailing-list
Sources
- CVE List CVE-2024-26874
- NVD CVE-2024-26874
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.