CVE-2026-98609: drm/virtio: fix object leak when drm_gem_handle_create() fails
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.17% (FIRST EPSS).
- Fixed version: Linux Linux 13423a058187c2039aa8cb235c916be4477221b7, 264ae8ac8fd625b6c118baf16c111adeee2ec632, 36570ef2244cc4d7563b1f0157bc0f032498638c; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 13423a058187c2039aa8cb235c916be4477221b7, 264ae8ac8fd625b6c118baf16c111adeee2ec632, 36570ef2244cc4d7563b1f0157bc0f032498638c; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.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/virtio: fix object leak when drm_gem_handle_create() fails virtio_gpu_gem_create() owns the reference taken by virtio_gpu_object_create(). On the drm_gem_handle_create() error path it calls drm_gem_object_release() instead of dropping that reference. drm_gem_object_release() is the inverse of drm_gem_object_init() and does not touch the reference count or call obj->funcs->free(), so it is only correct as the last step of a destructor, as in virtio_gpu_cleanup_object(). Using it here leaves the bo at refcount 1 with no remaining reference, so virtio_gpu_free_object() never runs and the shmem pages, sg table and virtio_gpu_object are leaked. Since virtio_gpu_object_create() has already set bo->created, VIRTIO_GPU_CMD_RESOURCE_UNREF is not queued either, leaking the host-side resource and the resource id. drm_gem_handle_create_tail() drops the handle reference on all of its internal error paths, so the caller only has to drop its own. Use drm_gem_object_put(), matching the success path below.
- Published
- Oct 18, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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
- 4.2affected
- dc5698e80cf724770283e10414054662bdf6ccfa and later · before 13423a058187c2039aa8cb235c916be4477221b7affected · git
- dc5698e80cf724770283e10414054662bdf6ccfa and later · before 687be2f8b5e0e0ca9a7028f8f6413d0ed3fbb9dcaffected · git
- dc5698e80cf724770283e10414054662bdf6ccfa and later · before 264ae8ac8fd625b6c118baf16c111adeee2ec632affected · git
- dc5698e80cf724770283e10414054662bdf6ccfa and later · before e2edd2d78d2cf8446de017adec9598feefed3297affected · git
- dc5698e80cf724770283e10414054662bdf6ccfa and later · before 372e9c3d45f664a2c000427ccbf6cdc2f99b3170affected · git
- dc5698e80cf724770283e10414054662bdf6ccfa and later · before a93dce15dfef200c346b050a2acbed516cc62706affected · git
- dc5698e80cf724770283e10414054662bdf6ccfa and later · before f75066c79d1eec453c0d386ef8636873d1e11f2caffected · git
- dc5698e80cf724770283e10414054662bdf6ccfa and later · before 36570ef2244cc4d7563b1f0157bc0f032498638caffected · git
- before 4.2not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.9-1 | 7.2.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98607Oct 18, 2026 · drm/virtio: fix object leaks in virtio_gpu_resource_create_blob_ioctl()0Monitor
- ← EarlierCVE-2026-98608Oct 18, 2026 · drm/virtio: fix object leak in virtio_gpu_resource_create_ioctl()0Monitor
- Later →CVE-2026-98610Oct 18, 2026 · net/sched: sch_hfsc: bound the classify inner-filter walk with a drift budget0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 13423a058187c2039aa8cb235c916be4477221b7 | Vendor (CNA) |
| Linux Linux | 264ae8ac8fd625b6c118baf16c111adeee2ec632 | Vendor (CNA) |
| Linux Linux | 36570ef2244cc4d7563b1f0157bc0f032498638c | Vendor (CNA) |
| Linux Linux | 372e9c3d45f664a2c000427ccbf6cdc2f99b3170 | Vendor (CNA) |
| Linux Linux | 687be2f8b5e0e0ca9a7028f8f6413d0ed3fbb9dc | Vendor (CNA) |
| Linux Linux | a93dce15dfef200c346b050a2acbed516cc62706 | Vendor (CNA) |
| Linux Linux | e2edd2d78d2cf8446de017adec9598feefed3297 | Vendor (CNA) |
| Linux Linux | f75066c79d1eec453c0d386ef8636873d1e11f2c | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package 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.
- Published
- Fix recordedsame day
- TodayNov 7, 2026+20 d
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 researchersFinders, 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1351 · Oct 19, 2026(Linux Kernel Güvenlik Bildirimi)
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
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/264ae8ac8fd625b6c118baf16c111adeee2ec632
- git.kernel.org/stable/c/36570ef2244cc4d7563b1f0157bc0f032498638c
- git.kernel.org/stable/c/372e9c3d45f664a2c000427ccbf6cdc2f99b3170
- git.kernel.org/stable/c/687be2f8b5e0e0ca9a7028f8f6413d0ed3fbb9dc
- git.kernel.org/stable/c/a93dce15dfef200c346b050a2acbed516cc62706
- git.kernel.org/stable/c/e2edd2d78d2cf8446de017adec9598feefed3297
- git.kernel.org/stable/c/f75066c79d1eec453c0d386ef8636873d1e11f2c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.