cve.bz

CVE-2026-98999 linux linux

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix stale pinned_link entry when fb-pin performs the final unpin xe_bo_pin_external() and xe_bo_unpin_external() maintain the bo's pinned_link list membership in xe->pinned.late.external, based on whether the current call is the outermost pin or the final unpin. However, the same external bo's pin_count can also be raised and lowered directly by __xe_pin_fb_vma()/__xe_unpin_fb_vma(), which pin the bo as a display scanout buffer without going through xe_bo_pin_external()/xe_bo_unpin_external() at all, and have no notion of, or ownership over, pinned_link. If a bo is pinned both externally (e.g. dma-buf export) and as an fb, and the external unpin happens first, xe_bo_unpin_external() correctly observes pin_count > 1 and leaves the bo on pinned_link. When the fb unpin later performs the true last unpin (pin_count 1 -> 0), it never touches pinned_link, leaving the bo linked on xe->pinned.late.external indefinitely. Once the bo is subsequently freed, this stale list entry points into freed memory, corrupting the list and risking a use-after-free the next time the list is walked or spliced. The backup object pin/unpin sites in xe_bo_notifier_prepare_pinned()/ xe_bo_notifier_unprepare_pinned() have the same bypass characteristic, though they never add their bo to a pinned list, so are not affected by this particular list-corruption issue. Move the pinned_link removal into xe_bo_account_unpin(), which already runs on every unpin path (kernel, external, framebuffer, backup object) right before the true 1 -> 0 pin_count transition. Since list_del_init() only operates on the node itself, this removal is list-agnostic and safe to perform regardless of which list (external or kernel_bo_present) the bo happens to be linked on, or which code path is performing the final unpin. Drop the now-redundant explicit list_del_init() calls in xe_bo_unpin_external() and xe_bo_unpin(). v2: - New patch v3: - Rebased on changes to previous patch. (cherry picked from commit ca58d36a1f93af586ee93b340c9f9fd81312cc01)

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-98999 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-98999?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-98999?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-98999 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-98999

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-98999](https://cve.bz/cve/badge/CVE-2026-98999.svg)](https://cve.bz/cve/CVE-2026-98999)

HTML:

<a href="https://cve.bz/cve/CVE-2026-98999"><img src="https://cve.bz/cve/badge/CVE-2026-98999.svg" alt="CVE-2026-98999"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.8 and later

Fixed in

ProductRelease lineFixed in
Linux6.186.18.57
Linux7.27.2.11
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13linuxno fix listedDEBIAN-CVE-2026-98999
Debian14linux7.2.11-1DEBIAN-CVE-2026-98999
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-98999
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-98999
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-98999
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 40 moreno fix listedUBUNTU-CVE-2026-98999
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 44 moreno fix listedUBUNTU-CVE-2026-98999
Ubuntu24.04:LTSlinux-aws-7.07.0.0-1017.18~24.04.1UBUNTU-CVE-2026-98999 USN-9020-1
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1019.19~24.04.1UBUNTU-CVE-2026-98999 USN-9020-1
Ubuntu24.04:LTSlinux-gcp-7.07.0.0-1017.19~24.04.1UBUNTU-CVE-2026-98999 USN-9020-1
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-43.43~24.04.1UBUNTU-CVE-2026-98999 USN-9018-2
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1016.18~24.04.1UBUNTU-CVE-2026-98999 USN-9020-1
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-43.43.1~24.04.2UBUNTU-CVE-2026-98999
Ubuntu26.04:LTSlinux7.0.0-43.43UBUNTU-CVE-2026-98999 USN-9018-1
18 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquita25linux-ltsno fix listedBELL-CVE-2026-98999
Alpaquitastreamlinux-lts6.18.58-r0BELL-CVE-2026-98999

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A framebuffer final unpin can leave xe_bo pinned_link attached to a pinned object list when the same buffer was also externally pinned. After the buffer is freed, a later list walk or splice can access freed memory and corrupt list pointers, creating a concrete use after free candidate with possible kernel crash and potential local privilege escalation. For the CVSS the PR:L value reflects that local DRM access plus control of a framebuffer, DRM lease, display service, or equivalent graphics context is required. AC:H reflects the required mixed external and framebuffer pin lifecycle, final unpin ordering, object release, and later list processing. The issue is not directly network reachable. Base impact is CIA:LLH, while the paranoid CIA:HHH score covers the still defensible possibility that allocator reuse turns the stale list node into stronger kernel memory corruption.

Red Hat's mitigation

--- CME Mitigation Guidance (2026-11-02) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to relocate buffer object tracking list detachment into common unpin accounting within the Intel Xe graphics driver to guarantee node removal on final unpin: upgrade to Linux kernel 6.18.57, 7.2.11, 7.3 (or the fixed Kernel/Kernel Ivos Qualcomm/Openshift/Ose Rhel Coreos/Kpatch builds), which move pinned_link removal via list_del_init into xe_bo_account_unpin so it unlinks the node during any 1-to-0 pin count transition, closing all 2 injection vectors (interleaved buffer object pinning via external dma-buf export and display framebuffer creation, triggering final unpin via framebuffer release to leave a stale list entry prior to buffer deallocation). Until patched, this is only a concern on Linux systems with Intel Xe graphics hardware and driver (drm/xe) where local users have access to DRM graphics rendering device nodes — Systems without Intel Xe graphics hardware or where DRM device nodes are restricted from untrusted users are unaffected — so restrict local user access to DRM graphics rendering device nodes, confine rendering privileges, and prevent untrusted users from accessing Intel Xe device interfaces. As a compensating measure, deploy KASAN or HWASan to detect use-after-free conditions and corrupted list pointer dereferences when the tracking list is traversed or spliced, enable SLAB freelist randomization and integrity checks to mitigate heap exploitation when manipulating freed buffer objects, enforce SELinux in enforcing mode to restrict local user access to Intel DRM device nodes and confine process domains, enable KASLR to randomize kernel code and data layouts to hinder locating kernel structures during exploitation, enable SMEP to prevent kernel-mode execution of userspace code if list corruption hijacks control flow, and enable SMAP to prevent kernel-mode access to userspace memory during use-after-free exploitation. These controls limit blast radius and contain exploitation, but they do not fix the underlying use-after-free list-corruption defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-98999.

References

Check your stackJSON