CVE-2026-98999

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)

• https://git.kernel.org/stable/c/3a11adcfd9a2de74d405bd3e8c4d7a1b328e4684
• https://git.kernel.org/stable/c/b3eaff982839e5c22912d604cd8e7748cece8d63
• https://git.kernel.org/stable/c/cf238c067eaae1cbfb00738e29219b9568d2313e

Published

Oct 23, 2026

Last Modified

Oct 24, 2026

Status

Received

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-98993In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-98994In the Linux kernel, the following vulnerability has been re…
• CVE-2026-98995In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-98996In the Linux kernel, the following vulnerability has been re…
• CVE-2026-98997In the Linux kernel, the following vulnerability has been re…
• CVE-2026-98998In the Linux kernel, the following vulnerability has been re…
• CVE-2026-9900Out of bounds write in ANGLE in Google Chrome prior to 148.0…8.3
• CVE-2026-99000In the Linux kernel, the following vulnerability has been re…
• CVE-2026-99001In the Linux kernel, the following vulnerability has been re…
• CVE-2026-99002In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-99003In the Linux kernel, the following vulnerability has been re…
• CVE-2026-99004In the Linux kernel, the following vulnerability has been re…