Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
  • Fixed version: Linux Linux 3d6576ed3de01e8a378397b7020e33ae3d40aa6c, 4.10, 780716e2e019186fa6e5aad097a44b87b0b5388f; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.

Low priority for now. Upgrade to Linux Linux 3d6576ed3de01e8a378397b7020e33ae3d40aa6c, 4.10, 780716e2e019186fa6e5aad097a44b87b0b5388f; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Oct 6, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 8th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-98319

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4cd462c7f2b6fcc208aebf44f2c831681feaa925, 4.10affected
    • 92c715fca907686f5298220ece53423e38ba3aed and later · before 3d6576ed3de01e8a378397b7020e33ae3d40aa6caffected · git
    • 92c715fca907686f5298220ece53423e38ba3aed and later · before 86c33f740aa27e9cdc1259f0cc59c9c58f545e4baffected · git
    • 92c715fca907686f5298220ece53423e38ba3aed and later · before 88c450e23b8fd4f1dcd329562f5e81ef05f3d941affected · git
    • 92c715fca907686f5298220ece53423e38ba3aed and later · before 780716e2e019186fa6e5aad097a44b87b0b5388faffected · git
    • 92c715fca907686f5298220ece53423e38ba3aed and later · before d0be0516b5224eb5b6f42f8564a8deadb20ae16baffected · git
    • 92c715fca907686f5298220ece53423e38ba3aed and later · before daefd7ff159b0d1fb8c9e64430dcbe2aca1bdd09affected · git
    • 92c715fca907686f5298220ece53423e38ba3aed and later · before b9a68a9ccaada15d8dd0102c188cc6b868ff800baffected · git
    • 92c715fca907686f5298220ece53423e38ba3aed and later · before 9eb1a393c89a79c4210230d23e7d88d239c61d7baffected · git
    • 4.9.10 and later · before 4.10affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.113-1~deb12u16.12.113-1~deb12u1
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.8-17.2.8-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-98317Oct 6, 2026 · neighbour: Enforce min/max to NDTPA_INTERVAL_PROBE_TIME_MS.
    0Monitor
  • ← EarlierCVE-2026-98318Oct 6, 2026 · smb: client: validate absolute native symlink targets before NT fixups
    31Monitor
  • Later →CVE-2026-98320Oct 6, 2026 · netfilter: flowtable: hold reference on ct until flow is released
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3d6576ed3de01e8a378397b7020e33ae3d40aa6cVendor (CNA)
Linux Linux4.10Vendor (CNA)
Linux Linux780716e2e019186fa6e5aad097a44b87b0b5388fVendor (CNA)
Linux Linux86c33f740aa27e9cdc1259f0cc59c9c58f545e4bVendor (CNA)
Linux Linux88c450e23b8fd4f1dcd329562f5e81ef05f3d941Vendor (CNA)
Linux Linux9eb1a393c89a79c4210230d23e7d88d239c61d7bVendor (CNA)
Linux Linuxb9a68a9ccaada15d8dd0102c188cc6b868ff800bVendor (CNA)
Linux Linuxd0be0516b5224eb5b6f42f8564a8deadb20ae16bVendor (CNA)
Linux Linuxdaefd7ff159b0d1fb8c9e64430dcbe2aca1bdd09Vendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.06.6.158.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)
debian:linux7.2.8-1 · Debian:14Package registry (OSV)
debian:linux-6.126.12.113-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 8, 2026+34 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Exploit maturity— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records