CVE-2026-98319

Kernel memory exhaustion via leaked DRM events

Published Oct 6, 2026 · Updated Oct 6, 2026

A memory leak in Linux kernel DRM atomic commits from 4.9.10 allows local users with display-control access to deplete kernel memory. In prepare_signaling(), an out_fence_ptr without DRM_MODE_PAGE_FLIP_EVENT allocates a drm_pending_vblank_event, but a later allocation or setup_out_fence() failure leaves it without base.fence, so complete_signaling() does not free it. Reaching the path requires access to a DRM modesetting device and a failing commit; the documented defect is unreleased kernel memory, not arbitrary code execution.

CVSS severityUnavailable
Unscored
EPSS probability0.18%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

A memory leak in Linux kernel DRM atomic commits from 4.9.10 allows local users with display-control access to deplete kernel memory. In prepare_signaling(), an out_fence_ptr without DRM_MODE_PAGE_FLIP_EVENT allocates a drm_pending_vblank_event, but a later allocation or setup_out_fence() failure leaves it without base.fence, so complete_signaling() does not free it. Reaching the path requires access to a DRM modesetting device and a failing commit; the documented defect is unreleased kernel memory, not arbitrary code execution.

The record

CVE
CVE-2026-98319
Published
Oct 6, 2026
Updated
Oct 6, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499.004
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Oct 6, 2026CVE publishedPublication date reported by the CVE source.
  2. Oct 6, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.10
  2. Affected versionversion=4.9.10 <4.10
  3. Affected versionversion=4cd462c7f2b6fcc208aebf44f2c831681feaa925
  4. Affected versionversion=92c715fca907686f5298220ece53423e38ba3aed <3d6576ed3de01e8a378397b7020e33ae3d40aa6c
  5. Affected versionversion=92c715fca907686f5298220ece53423e38ba3aed <780716e2e019186fa6e5aad097a44b87b0b5388f
  6. Affected versionversion=92c715fca907686f5298220ece53423e38ba3aed <86c33f740aa27e9cdc1259f0cc59c9c58f545e4b
  7. Affected versionversion=92c715fca907686f5298220ece53423e38ba3aed <88c450e23b8fd4f1dcd329562f5e81ef05f3d941
  8. Affected versionversion=92c715fca907686f5298220ece53423e38ba3aed <9eb1a393c89a79c4210230d23e7d88d239c61d7b
  9. Affected versionversion=92c715fca907686f5298220ece53423e38ba3aed <b9a68a9ccaada15d8dd0102c188cc6b868ff800b
  10. Affected versionversion=92c715fca907686f5298220ece53423e38ba3aed <d0be0516b5224eb5b6f42f8564a8deadb20ae16b
  11. Affected versionversion=92c715fca907686f5298220ece53423e38ba3aed <daefd7ff159b0d1fb8c9e64430dcbe2aca1bdd09

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=4.10; version=4.9.10 <4.10; version=4cd462c7f2b6fcc208aebf44f2c831681feaa925; version=92c715fca907686f5298220ece53423e38ba3aed <3d6576ed3de01e8a378397b7020e33ae3d40aa6c; version=92c715fca907686f5298220ece53423e38ba3aed <780716e2e019186fa6e5aad097a44b87b0b5388f; version=92c715fca907686f5298220ece53423e38ba3aed <86c33f740aa27e9cdc1259f0cc59c9c58f545e4b; version=92c715fca907686f5298220ece53423e38ba3aed <88c450e23b8fd4f1dcd329562f5e81ef05f3d941; version=92c715fca907686f5298220ece53423e38ba3aed <9eb1a393c89a79c4210230d23e7d88d239c61d7b; version=92c715fca907686f5298220ece53423e38ba3aed <b9a68a9ccaada15d8dd0102c188cc6b868ff800b; version=92c715fca907686f5298220ece53423e38ba3aed <d0be0516b5224eb5b6f42f8564a8deadb20ae16b; version=92c715fca907686f5298220ece53423e38ba3aed <daefd7ff159b0d1fb8c9e64430dcbe2aca1bdd09

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499.004Endpoint Denial of Service: Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started