# CVE-2026-98319: drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr

> A memory leak in the Linux kernel DRM subsystem allows local attackers to cause denial of service via resource exhaustion.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106398, BELL-CVE-2026-98319, DEBIAN-CVE-2026-98319, GHSA-hr58-jv8x-qqg3, UBUNTU-CVE-2026-98319

## What is CVE-2026-98319?

CVE-2026-98319 is a memory corruption vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-98319?


## How do I fix CVE-2026-98319?

Apply the vendor's patch.

## Is CVE-2026-98319 being exploited?

There is no known exploitation of CVE-2026-98319 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98319 and fix it if it is affected.

What it is: CVE-2026-98319 is a memory corruption vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98319 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98319/ (Markdown: https://insights.sbomify.com/CVE-2026-98319/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98319
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98319
- OSV: https://osv.dev/vulnerability/CVE-2026-98319

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98319/
Summaries are generated and may contain mistakes; the official description above is the record.