CVE-2026-98319 — drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 92c715fca907686f5298220ece53423e38ba3aed and < 3d6576ed3de01e8a378397b7020e33ae3d40aa6c≥ 92c715fca907686f5298220ece53423e38ba3aed and < 86c33f740aa27e9cdc1259f0cc59c9c58f545e4b≥ 92c715fca907686f5298220ece53423e38ba3aed and < 88c450e23b8fd4f1dcd329562f5e81ef05f3d941≥ 92c715fca907686f5298220ece53423e38ba3aed and < 780716e2e019186fa6e5aad097a44b87b0b5388f≥ 92c715fca907686f5298220ece53423e38ba3aed and < d0be0516b5224eb5b6f42f8564a8deadb20ae16b≥ 92c715fca907686f5298220ece53423e38ba3aed and < daefd7ff159b0d1fb8c9e64430dcbe2aca1bdd09≥ 92c715fca907686f5298220ece53423e38ba3aed and < b9a68a9ccaada15d8dd0102c188cc6b868ff800b≥ 92c715fca907686f5298220ece53423e38ba3aed and < 9eb1a393c89a79c4210230d23e7d88d239c61d7b and 3 moreversion 4cd462c7f2b6fcc208aebf44f2c831681feaa925≥ 4.9.10 and < 4.10version 4.10 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.18%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- git.kernel.org/stable/c/d0be0516b5224eb5b6f42f8564a8deadb20ae16b
- git.kernel.org/stable/c/daefd7ff159b0d1fb8c9e64430dcbe2aca1bdd09
- git.kernel.org/stable/c/780716e2e019186fa6e5aad097a44b87b0b5388f
- git.kernel.org/stable/c/88c450e23b8fd4f1dcd329562f5e81ef05f3d941
- git.kernel.org/stable/c/3d6576ed3de01e8a378397b7020e33ae3d40aa6c
- git.kernel.org/stable/c/b9a68a9ccaada15d8dd0102c188cc6b868ff800b
- git.kernel.org/stable/c/9eb1a393c89a79c4210230d23e7d88d239c61d7b
- git.kernel.org/stable/c/86c33f740aa27e9cdc1259f0cc59c9c58f545e4b
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 8h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 8h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-98319 is "drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.