CVE-2026-98509: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-f38g-7gw9-c4x5
Share
Published
Advisory Summary

CVE-2026-98509 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-98509 at a Glance

CVE Identifier CVE-2026-98509
GHSA Identifier GHSA-f38g-7gw9-c4x5
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-98509

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-98509, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In the Linux kernel, the following vulnerability has been resolved: drm/virtio: fix memory leak of fence event on execbuffer failure virtio_gpu_execbuffer_ioctl() reserves a DRM event with drm_event_reserve_init() when VIRTGPU_EXECBUF_RING_IDX selects a ring that userspace has enabled polling for. virtio_gpu_init_submit() does this before the BO handles, the command buffer, the syncobj arrays and the in-fence are processed, so every later error path runs with the event already pending, including plain argument validation failures such as an invalid bo_handle or an in-syncobj that carries no fence. On those paths, virtio_gpu_cleanup_submit() drops the out-fence without cancelling the event. The fence is freed without ever having been emitted, taking the only driver-side pointer to the event with it. Closing the DRM file does not help. drm_events_release() unlinks pending events but deliberately leaves the freeing to the driver's later drm_send_event(), which never runs for an orphaned event, so the allocation is leaked permanently. Found when fuzzing the virtio driver with Syzkaller: BUG: memory leak unreferenced object 0xffff88802c176e80 (size 96): comm "syz.1.367", pid 10561, jiffies 4294960122 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ c8 6e 17 2c 80 88 ff ff 00 00 00 00 00 00 00 00 .n.,............ backtrace (crc e1973c6b): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4597 [inline] slab_alloc_node mm/slub.c:4917 [inline] __kmalloc_cache_noprof+0x49d/0x6f0 mm/slub.c:5485 _kmalloc_noprof include/linux/slab.h:988 [inline] _kzalloc_noprof include/linux/slab.h:1309 [inline] virtio_gpu_fence_event_create drivers/gpu/drm/virtio/virtgpu_submit.c:282 [inline] virtio_gpu_init_submit drivers/gpu/drm/virtio/virtgpu_submit.c:398 [inline] virtio_gpu_execbuffer_ioctl+0xbbf/0x1aa0 drivers/gpu/drm/virtio/virtgpu_submit.c:505 drm_ioctl_kernel+0x1f4/0x3e0 drivers/gpu/drm/drm_ioctl.c:817 drm_ioctl+0x5f4/0xc70 drivers/gpu/drm/drm_ioctl.c:914 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x116/0x800 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Fix by cancelling and freeing the DRM event on the execbuffer error path before dropping the fence. Clear the fence's event pointer after cancellation so it does not retain a dangling pointer.

References

NVD — CVE-2026-98509 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98509
git.kernel.org/stable/c/43bfe2b60c... WEB
https://git.kernel.org/stable/c/43bfe2b60c149bf6effda25f245a00509061fa15
git.kernel.org/stable/c/4e333e2336... WEB
https://git.kernel.org/stable/c/4e333e2336138f4659b1d7a0371c499f80428612
git.kernel.org/stable/c/8fa78900fd... WEB
https://git.kernel.org/stable/c/8fa78900fd24247277c03dc7b8a2864cb12d4340
git.kernel.org/stable/c/ae583668f1... WEB
https://git.kernel.org/stable/c/ae583668f16d41fcc1b54f45848c1b6ac1d6669a
git.kernel.org/stable/c/b74aad23d9... WEB
https://git.kernel.org/stable/c/b74aad23d99b279bb34d135795f39a6d8ecdc075

Frequently Asked Questions

What is CVE-2026-98509?
CVE-2026-98509 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-98509?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98509?
CVE-2026-98509 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98509?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-f38g-7gw9-c4x5",
  "modified" : "2026-10-18T18:31:52Z",
  "published" : "2026-10-18T18:31:51Z",
  "aliases" : [ "CVE-2026-98509" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/virtio: fix memory leak of fence event on execbuffer failure\n\nvirtio_gpu_execbuffer_ioctl() reserves a DRM event with\ndrm_event_reserve_init() when VIRTGPU_EXECBUF_RING_IDX selects a ring that\nuserspace has enabled polling for. virtio_gpu_init_submit() does this\nbefore the BO handles, the command buffer, the syncobj arrays and the\nin-fence are processed, so every later error path runs with the event\nalready pending, including plain argument validation failures such as an\ninvalid bo_handle or an in-syncobj that carries no fence.\n\nOn those paths, virtio_gpu_cleanup_submit() drops the out-fence without\ncancelling the event. The fence is freed without ever having been emitted,\ntaking the only driver-side pointer to the event with it. Closing the DRM\nfile does not help. drm_events_release() unlinks pending events but\ndeliberately leaves the freeing to the driver's later drm_send_event(),\nwhich never runs for an orphaned event, so the allocation is leaked\npermanently.\n\nFound when fuzzing the virtio driver with Syzkaller:\n\n\tBUG: memory leak\n\tunreferenced object 0xffff88802c176e80 (size 96):\n\tcomm \"syz.1.367\", pid 10561, jiffies 4294960122\n\thex dump (first 32 bytes):\n\t\t00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n\t\tc8 6e 17 2c 80 88 ff ff 00 00 00 00 00 00 00 00  .n.,............\n\tbacktrace (crc e1973c6b):\n\t\tkmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]\n\t\tslab_post_alloc_hook mm/slub.c:4597 [inline]\n\t\tslab_alloc_node mm/slub.c:4917 [inline]\n\t\t__kmalloc_cache_noprof+0x49d/0x6f0 mm/slub.c:5485\n\t\t_kmalloc_noprof include/linux/slab.h:988 [inline]\n\t\t_kzalloc_noprof include/linux/slab.h:1309 [inline]\n\t\tvirtio_gpu_fence_event_create drivers/gpu/drm/virtio/virtgpu_submit.c:282 [inline]\n\t\tvirtio_gpu_init_submit drivers/gpu/drm/virtio/virtgpu_submit.c:398 [inline]\n\t\tvirtio_gpu_execbuffer_ioctl+0xbbf/0x1aa0 drivers/gpu/drm/virtio/virtgpu_submit.c:505\n\t\tdrm_ioctl_kernel+0x1f4/0x3e0 drivers/gpu/drm/drm_ioctl.c:817\n\t\tdrm_ioctl+0x5f4/0xc70 drivers/gpu/drm/drm_ioctl.c:914\n\t\tvfs_ioctl fs/ioctl.c:51 [inline]\n\t\t__do_sys_ioctl fs/ioctl.c:597 [inline]\n\t\t__se_sys_ioctl fs/ioctl.c:583 [inline]\n\t\t__x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n\t\tdo_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n\t\tdo_syscall_64+0x116/0x800 arch/x86/entry/syscall_64.c:94\n\t\tentry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFix by cancelling and freeing the DRM event on the execbuffer error path\nbefore dropping the fence. Clear the fence's event pointer after\ncancellation so it does not retain a dangling pointer.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98509"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/43bfe2b60c149bf6effda25f245a00509061fa15"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4e333e2336138f4659b1d7a0371c499f80428612"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8fa78900fd24247277c03dc7b8a2864cb12d4340"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ae583668f16d41fcc1b54f45848c1b6ac1d6669a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b74aad23d99b279bb34d135795f39a6d8ecdc075"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:02Z"
  }
}