Strix
69K

CVE-2026-98319

Unknown

Last modified

CVE-2026-98319 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr When an out_fence_ptr is provided but DRM_MODE_PAGE_FLIP_EVENT is not set, a drm_pending_vblank_event will be allocated. If later, there is an allocation failure or another failure at setup_out_fence(), that event will not have base.fence set and it will not be released at complete_signaling(). Release the event and set crtc_state->event to NULL just like in the DRM_MODE_PAGE_FLIP_EVENT case when there is a failure at drm_event_reserve_init().

Description

In the Linux kernel, the following vulnerability has been resolved: drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr When an out_fence_ptr is provided but DRM_MODE_PAGE_FLIP_EVENT is not set, a drm_pending_vblank_event will be allocated. If later, there is an allocation failure or another failure at setup_out_fence(), that event will not have base.fence set and it will not be released at complete_signaling(). Release the event and set crtc_state->event to NULL just like in the DRM_MODE_PAGE_FLIP_EVENT case when there is a failure at drm_event_reserve_init(). That is, prepare_signaling() releases the event and there is nothing to be done at complete_signaling(). Use drm_event_cancel_free() as that will also undo drm_event_reserve_init() in case it has been called.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 92c715fca907686f5298220ece53423e38ba3aed, < 3d6576ed3de01e8a378397b7020e33ae3d40aa6c; >= 92c715fca907686f5298220ece53423e38ba3aed, < 86c33f740aa27e9cdc1259f0cc59c9c58f545e4b; >= 92c715fca907686f5298220ece53423e38ba3aed, < 88c450e23b8fd4f1dcd329562f5e81ef05f3d941; >= 92c715fca907686f5298220ece53423e38ba3aed, < 780716e2e019186fa6e5aad097a44b87b0b5388f; >= 92c715fca907686f5298220ece53423e38ba3aed, < d0be0516b5224eb5b6f42f8564a8deadb20ae16b; >= 92c715fca907686f5298220ece53423e38ba3aed, < daefd7ff159b0d1fb8c9e64430dcbe2aca1bdd09; >= 92c715fca907686f5298220ece53423e38ba3aed, < b9a68a9ccaada15d8dd0102c188cc6b868ff800b; >= 92c715fca907686f5298220ece53423e38ba3aed, < 9eb1a393c89a79c4210230d23e7d88d239c61d7b; 4cd462c7f2b6fcc208aebf44f2c831681feaa925; >= 4.9.10, < 4.10
LinuxLinux4.10

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98319?
In the Linux kernel, the following vulnerability has been resolved: drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr When an out_fence_ptr is provided but DRM_MODE_PAGE_FLIP_EVENT is not set, a drm_pending_vblank_event will be allocated. If later, there is an allocation failure or another failure at setup_out_fence(), that event will not have base.fence set and it will not be released at complete_signaling(). Release the event and set crtc_state->event to NULL just like in the DRM_MODE_PAGE_FLIP_EVENT case when there is a failure at drm_event_reserve_init(). That is, prepare_signaling() releases the event and there is nothing to be done at complete_signaling(). Use drm_event_cancel_free() as that will also undo drm_event_reserve_init() in case it has been called.
How severe is CVE-2026-98319?
Severity scoring for CVE-2026-98319 is pending analysis.
How do I fix CVE-2026-98319?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-98319?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST