CVE-2026-98319
drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 92c715fca907686f5298220ece53423e38ba3aed, < 3d6576ed3de01e8a378397b7020e33ae3d40aa6cUpgrade to: 3d6576ed3de01e8a378397b7020e33ae3d40aa6cAffected: ≥ 92c715fca907686f5298220ece53423e38ba3aed, < 86c33f740aa27e9cdc1259f0cc59c9c58f545e4bUpgrade to: 86c33f740aa27e9cdc1259f0cc59c9c58f545e4bAffected: ≥ 92c715fca907686f5298220ece53423e38ba3aed, < 88c450e23b8fd4f1dcd329562f5e81ef05f3d941Upgrade to: 88c450e23b8fd4f1dcd329562f5e81ef05f3d941Affected: ≥ 92c715fca907686f5298220ece53423e38ba3aed, < 780716e2e019186fa6e5aad097a44b87b0b5388fUpgrade to: 780716e2e019186fa6e5aad097a44b87b0b5388f + 6 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/3d6576ed3de01e8a378397b7020e33ae3d40aa6c
- git.kernel.org/stable/c/780716e2e019186fa6e5aad097a44b87b0b5388f
- git.kernel.org/stable/c/86c33f740aa27e9cdc1259f0cc59c9c58f545e4b
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI