Kernel crash via unchecked fence allocation
Published Oct 18, 2026 · Updated Oct 18, 2026
NULL dereference in the Linux kernel's virtio GPU driver allows local users to crash the kernel through graphics submission. In drivers/gpu/drm/virtio/virtgpu_submit.c, virtio_gpu_init_submit() forwards an unchecked NULL result from virtio_gpu_fence_alloc() to virtio_gpu_fence_event_create(), which dereferences it. The path requires access to the virtio GPU graphics ioctl and an allocation failure under memory pressure; the documented consequence is a kernel fault, not privilege escalation.
Summary
What happened
NULL dereference in the Linux kernel's virtio GPU driver allows local users to crash the kernel through graphics submission. In drivers/gpu/drm/virtio/virtgpu_submit.c, virtio_gpu_init_submit() forwards an unchecked NULL result from virtio_gpu_fence_alloc() to virtio_gpu_fence_event_create(), which dereferences it. The path requires access to the virtio GPU graphics ioctl and an allocation failure under memory pressure; the documented consequence is a kernel fault, not privilege escalation.
The record
- CVE
- CVE-2026-98508
- Published
- Oct 18, 2026
- Updated
- Oct 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 18, 2026CVE publishedPublication date reported by the CVE source.
- Oct 18, 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.
- Affected versionversion=4037dcd70c3335600a2a95ec6229d70859bd37a1
- Affected versionversion=6.1.54 <6.2
- Affected versionversion=6.5.4 <6.6
- Affected versionversion=6.6
- Affected versionversion=70d1ace56db6c79d39dbe9c0d5244452b67e2fde <846b3c64fe3e77d9db20a7e3e62dbbb637c773e1
- Affected versionversion=70d1ace56db6c79d39dbe9c0d5244452b67e2fde <9571ab7493561afb4624d69572a7ebb67d76d10f
- Affected versionversion=70d1ace56db6c79d39dbe9c0d5244452b67e2fde <a8b83ed4a4b1d04c756f53e375e86d3881f66e72
- Affected versionversion=70d1ace56db6c79d39dbe9c0d5244452b67e2fde <ecced0076b700b5896e52af10d0776be8be36b0d
- Affected versionversion=70d1ace56db6c79d39dbe9c0d5244452b67e2fde <f2f1683955b95c9b958069da3050f7e8e129ff88
- Affected versionversion=98d3e7c5f757577394f036e0301db9e570342566
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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