Skip to content
Fencer Vulns
high 7.8

CVE-2024-26939 json

drm/i915/vma: Fix UAF on destroy against retire race

published 2024-05-01 2 y ago modified 2026-08-05 3 mo ago also EUVD-2024-24201

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 16%
public exploits
0
none known

Summary

In the Linux kernel, the following vulnerability has been resolved:

drm/i915/vma: Fix UAF on destroy against retire race

Object debugging tools were sporadically reporting illegal attempts to free a still active i915 VMA object when parking a GT believed to be idle.

[161.359441] ODEBUG: free active (active state 0) object: ffff88811643b958 object type: i915_active hint: __i915_vma_active+0x0/0x50 [i915] [161.360082] WARNING: CPU: 5 PID: 276 at lib/debugobjects.c:514 debug_print_object+0x80/0xb0 ... [161.360304] CPU: 5 PID: 276 Comm: kworker/5:2 Not tainted 6.5.0-rc1-CI_DRM_13375-g003f860e5577+ #1 [161.360314] Hardware name: Intel Corporation Rocket Lake Client Platform/RocketLake S UDIMM 6L RVP, BIOS RKLSFWI1.R00.3173.A03.2204210138 04/21/2022 [161.360322] Workqueue: i915-unordered __intel_wakeref_put_work [i915] [161.360592] RIP: 0010:debug_print_object+0x80/0xb0 ... [161.361347] debug_object_free+0xeb/0x110 [161.361362] i915_active_fini+0x14/0x130 [i915] [161.361866] release_references+0xfe/0x1f0 [i915] [161.362543] i915_vma_parked+0x1db/0x380 [i915] [161.363129] __gt_park+0x121/0x230 [i915] [161.363515] ____intel_wakeref_put_last+0x1f/0x70 [i915]

That has been tracked down to be happening when another thread is deactivating the VMA inside __active_retire() helper, after the VMA's active counter has been already decremented to 0, but before deactivation of the VMA's object is reported to the object debugging tool.

We could prevent from that race by serializing i915_active_fini() with __active_retire() via ref->tree_lock, but that wouldn't stop the VMA from being used, e.g. from __i915_vma_retire() called at the end of __active_retire(), after that VMA has been already freed by a concurrent i915_vma_destroy() on return from the i915_active_fini(). Then, we should rather fix the issue at the VMA level, not in i915_active.

Since __i915_vma_parked() is called from __gt_park() on last put of the GT's wakeref, the issue could be addressed by holding the GT wakeref long enough for __active_retire() to complete before that wakeref is released and the GT parked.

I believe the issue was introduced by commit d93939730347 ("drm/i915: Remove the vma refcount") which moved a call to i915_active_fini() from a dropped i915_vma_release(), called on last put of the removed VMA kref, to i915_vma_parked() processing path called on last put of a GT wakeref. However, its visibility to the object debugging tool was suppressed by a bug in i915_active that was fixed two weeks later with commit e92eb246feb9 ("drm/i915/active: Fix missing debug object activation").

A VMA associated with a request doesn't acquire a GT wakeref by itself. Instead, it depends on a wakeref held directly by the request's active intel_context for a GT associated with its VM, and indirectly on that intel_context's engine wakeref if the engine belongs to the same GT as the VMA's VM. Those wakerefs are released asynchronously to VMA deactivation.

Fix the issue by getting a wakeref for the VMA's GT when activating it, and putting that wakeref only after the VMA is deactivated. However, exclude global GTT from that processing path, otherwise the GPU never goes idle. Since __i915_vma_retire() may be called from atomic contexts, use async variant of wakeref put. Also, to avoid circular locking dependency, take care of acquiring the wakeref before VM mutex when both are needed.

v7: Add inline comments with justifications for: - using untracked variants of intel_gt_pm_get/put() (Nirmoy), - using async variant of _put(), - not getting the wakeref in case of a global GTT, - always getting the first wakeref outside vm->mutex. v6: Since __i915_vma_active/retire() callbacks are not serialized, storing a wakeref tracking handle inside struct i915_vma is not safe, and there is no other good place for that. Use untracked variants of intel_gt_pm_get/put_async(). v5: Replace "tile" with "GT" across commit description (Rodrigo), - ---truncated---

Patch / fix

  • Linux Linux 6.1.88, 6.6.29, 6.8.3, 6.9
  • linux Debian 12 6.1.90-1
  • linux Debian 14, Debian 13 6.8.9-1

debian advisories DEBIAN-CVE-2024-26939

  • linux Ubuntu 24.04 LTS 6.8.0-35.35
  • linux-aws Ubuntu 24.04 LTS 6.8.0-1009.9
  • linux-gcp Ubuntu 24.04 LTS 6.8.0-1008.9
  • linux-gke Ubuntu 24.04 LTS 6.8.0-1004.7
  • linux-ibm Ubuntu 24.04 LTS 6.8.0-1006.6
  • linux-azure Ubuntu 24.04 LTS 6.8.0-1008.8
  • linux-raspi Ubuntu 24.04 LTS 6.8.0-1005.5
  • linux-riscv Ubuntu 24.04 LTS 6.8.0-35.35.1

ubuntu advisories UBUNTU-CVE-2024-26939

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

  • kernel RHEL 9 5.14.0-503.11.1.el9_5
  • rv RHEL 9 5.14.0-503.11.1.el9_5
  • perf RHEL 9 5.14.0-503.11.1.el9_5
  • rtla RHEL 9 5.14.0-503.11.1.el9_5
  • bpftool RHEL 9 7.4.0-503.11.1.el9_5
  • libperf RHEL 9 5.14.0-503.11.1.el9_5
  • kernel-rt RHEL 9 5.14.0-503.11.1.el9_5
  • kernel-64k RHEL 9 5.14.0-503.11.1.el9_5

red hat advisories RHSA-2025:9584RHSA-2024:9315RHSA-2024:7000RHSA-2024:7001

  • kernel-rt Linux Micro 6.0 6.4.0-9.1
  • kernel-source-rt Linux Micro 6.0 6.4.0-9.1
  • kernel-source Linux Micro 6.0 6.4.0-18.1
  • kernel-default Linux Micro 6.0 6.4.0-18.1
  • kernel-kvmsmall Linux Micro 6.0 6.4.0-18.1
  • kernel-default-base Linux Micro 6.0 6.4.0-17.1.1.51
  • 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

suse advisories SUSE-SU-2025:20028-1SUSE-SU-2025:20008-1SUSE-SU-2024:2190-1SUSE-SU-2024:2008-1SUSE-SU-2024:1644-1

  • kernel AlmaLinux 8 4.18.0-553.22.1.el8_10
  • perf AlmaLinux 8 4.18.0-553.22.1.el8_10
  • bpftool AlmaLinux 8 4.18.0-553.22.1.el8_10
  • kernel-core AlmaLinux 8 4.18.0-553.22.1.el8_10
  • kernel-tools AlmaLinux 8 4.18.0-553.22.1.el8_10
  • python3-perf AlmaLinux 8 4.18.0-553.22.1.el8_10
  • kernel-modules AlmaLinux 8 4.18.0-553.22.1.el8_10
  • kernel-zfcpdump AlmaLinux 8 4.18.0-553.22.1.el8_10

almalinux advisories ALSA-2024:7000ALSA-2024:7001

  • kernel Rocky Linux 8 4.18.0-553.22.1.el8_10
  • kernel-rt Rocky Linux 8 4.18.0-553.22.1.rt7.363.el8_10

rocky linux advisories RLSA-2024:7000RLSA-2024:7001

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-26939 updated cvss 5.5

kernel: drm/i915/vma: Fix UAF on destroy against retire race

  • 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
    affected: no fix planned “Out of support scope”
  • Red Hat CodeReady Linux Builder (v. 9) libperf 5.14.0-503.11.1.el9_5, kernel-debuginfo-common-s390x 5.14.0-503.11.1.el9_5, kernel-debuginfo-common-x86_64 5.14.0-503.11.1.el9_5, kernel-debuginfo-common-aarch64 5.14.0-503.11.1.el9_5, kernel-debuginfo-common-ppc64le 5.14.0-503.11.1.el9_5
    fixed: vendor fix RHSA-2024:9315
  • Red Hat CodeReady Linux Builder EUS (v.9.4) libperf 5.14.0-427.74.1.el9_4, kernel-debuginfo-common-s390x 5.14.0-427.74.1.el9_4, kernel-debuginfo-common-x86_64 5.14.0-427.74.1.el9_4, kernel-debuginfo-common-aarch64 5.14.0-427.74.1.el9_4, kernel-debuginfo-common-ppc64le 5.14.0-427.74.1.el9_4
    fixed: vendor fix RHSA-2025:9584
  • Red Hat Enterprise Linux AppStream (v. 9) rv 5.14.0-503.11.1.el9_5, perf 5.14.0-503.11.1.el9_5, rtla 5.14.0-503.11.1.el9_5, kernel-devel-matched 5.14.0-503.11.1.el9_5, kernel-64k-devel-matched 5.14.0-503.11.1.el9_5, kernel-debug-devel-matched 5.14.0-503.11.1.el9_5, +6 more
    fixed: vendor fix RHSA-2024:9315
  • Red Hat Enterprise Linux AppStream EUS (v.9.4) rv 5.14.0-427.74.1.el9_4, perf 5.14.0-427.74.1.el9_4, rtla 5.14.0-427.74.1.el9_4, kernel-devel-matched 5.14.0-427.74.1.el9_4, kernel-64k-devel-matched 5.14.0-427.74.1.el9_4, kernel-debug-devel-matched 5.14.0-427.74.1.el9_4, +6 more
    fixed: vendor fix RHSA-2025:9584
  • Red Hat Enterprise Linux BaseOS (v. 8) perf 4.18.0-553.22.1.el8_10, kernel 4.18.0-553.22.1.el8_10, bpftool 4.18.0-553.22.1.el8_10, kernel-core 4.18.0-553.22.1.el8_10, kernel-tools 4.18.0-553.22.1.el8_10, python3-perf 4.18.0-553.22.1.el8_10, +15 more
    fixed: vendor fix RHSA-2024:7000
  • Red Hat Enterprise Linux BaseOS (v. 9) bpftool 7.4.0-503.11.1.el9_5, kernel 5.14.0-503.11.1.el9_5, kernel-64k 5.14.0-503.11.1.el9_5, kernel-core 5.14.0-503.11.1.el9_5, kernel-tools 5.14.0-503.11.1.el9_5, python3-perf 5.14.0-503.11.1.el9_5, +29 more
    fixed: vendor fix RHSA-2024:9315
  • Red Hat Enterprise Linux BaseOS EUS (v.9.4) bpftool 7.3.0-427.74.1.el9_4, kernel 5.14.0-427.74.1.el9_4, kernel-64k 5.14.0-427.74.1.el9_4, kernel-core 5.14.0-427.74.1.el9_4, kernel-tools 5.14.0-427.74.1.el9_4, python3-perf 5.14.0-427.74.1.el9_4, +28 more
    fixed: vendor fix RHSA-2025:9584
show 9 more
  • Red Hat Enterprise Linux CRB (v. 8) kernel-debuginfo-common-x86_64 4.18.0-553.22.1.el8_10, kernel-debuginfo-common-aarch64 4.18.0-553.22.1.el8_10, kernel-debuginfo-common-ppc64le 4.18.0-553.22.1.el8_10
    fixed: vendor fix RHSA-2024:7000
  • Red Hat Enterprise Linux NFV (v. 8) kernel-rt 4.18.0-553.22.1.rt7.363.el8_10, kernel-rt-kvm 4.18.0-553.22.1.rt7.363.el8_10, kernel-rt-core 4.18.0-553.22.1.rt7.363.el8_10, kernel-rt-modules 4.18.0-553.22.1.rt7.363.el8_10, kernel-rt-debug-kvm 4.18.0-553.22.1.rt7.363.el8_10, kernel-rt-debug-core 4.18.0-553.22.1.rt7.363.el8_10, +4 more
    fixed: vendor fix RHSA-2024:7001
  • Red Hat Enterprise Linux Real Time (v. 9) kernel-rt 5.14.0-503.11.1.el9_5, kernel-rt-core 5.14.0-503.11.1.el9_5, kernel-rt-modules 5.14.0-503.11.1.el9_5, kernel-rt-debug-core 5.14.0-503.11.1.el9_5, kernel-rt-modules-core 5.14.0-503.11.1.el9_5, kernel-rt-debug-modules 5.14.0-503.11.1.el9_5, +4 more
    fixed: vendor fix RHSA-2024:9315
  • Red Hat Enterprise Linux Real Time EUS (v.9.4) kernel-rt 5.14.0-427.74.1.el9_4, kernel-rt-core 5.14.0-427.74.1.el9_4, kernel-rt-modules 5.14.0-427.74.1.el9_4, kernel-rt-debug-core 5.14.0-427.74.1.el9_4, kernel-rt-modules-core 5.14.0-427.74.1.el9_4, kernel-rt-debug-modules 5.14.0-427.74.1.el9_4, +4 more
    fixed: vendor fix RHSA-2025:9584
  • Red Hat Enterprise Linux Real Time for NFV (v. 9) kernel-rt 5.14.0-503.11.1.el9_5, kernel-rt-kvm 5.14.0-503.11.1.el9_5, kernel-rt-core 5.14.0-503.11.1.el9_5, kernel-rt-modules 5.14.0-503.11.1.el9_5, kernel-rt-debug-kvm 5.14.0-503.11.1.el9_5, kernel-rt-debug-core 5.14.0-503.11.1.el9_5, +6 more
    fixed: vendor fix RHSA-2024:9315
  • Red Hat Enterprise Linux Real Time for NFV EUS (v.9.4) kernel-rt 5.14.0-427.74.1.el9_4, kernel-rt-kvm 5.14.0-427.74.1.el9_4, kernel-rt-core 5.14.0-427.74.1.el9_4, kernel-rt-modules 5.14.0-427.74.1.el9_4, kernel-rt-debug-kvm 5.14.0-427.74.1.el9_4, kernel-rt-debug-core 5.14.0-427.74.1.el9_4, +6 more
    fixed: vendor fix RHSA-2025:9584
  • Red Hat Enterprise Linux RT (v. 8) kernel-rt 4.18.0-553.22.1.rt7.363.el8_10, kernel-rt-core 4.18.0-553.22.1.rt7.363.el8_10, kernel-rt-modules 4.18.0-553.22.1.rt7.363.el8_10, kernel-rt-debug-core 4.18.0-553.22.1.rt7.363.el8_10, kernel-rt-debug-modules 4.18.0-553.22.1.rt7.363.el8_10, kernel-rt-modules-extra 4.18.0-553.22.1.rt7.363.el8_10, +2 more
    fixed: vendor fix RHSA-2024:7001
  • Red Hat OpenShift AI 8 rhoai/odh-rhel8-operator v2.13.1-2, rhoai/odh-dashboard-rhel8 v2.13.1-1, rhoai/odh-modelmesh-rhel8 v2.13.1-1, rhoai/odh-operator-bundle v2.13.1-2, rhoai/odh-rhel8-operator v2.14.0-24, rhoai/odh-dashboard-rhel8 v2.14.0-11, +56 more
    fixed: vendor fix RHBA-2024:8413
  • Red Hat CodeReady Linux Builder (v. 9) kernel-cross-headers 5.14.0-503.11.1.el9_5 Red Hat Enterprise Linux AppStream (v. 9) kernel-headers 5.14.0-503.11.1.el9_5
    not 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
total
Assessed
2 y ago

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Linux Linux

Classification

Weakness
Technology feeds

References

Sources

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.