CVE-2026-46314
Received Received - Intake
Infinite Loop in Linux Kernel V3D Driver

Publication date: 2026-06-08

Last updated on: 2026-06-08

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Reject empty multisync extension to prevent infinite loop v3d_get_extensions() walks a userspace-provided singly-linked list of ioctl extensions without any bound on the chain length. A local user can craft a self-referential extension (ext->next == &ext) with zero in_sync_count and out_sync_count, which bypasses the existing duplicate- extension guard: if (se->in_sync_count || se->out_sync_count) return -EINVAL; The guard never fires because v3d_get_multisync_post_deps() returns immediately when count is zero, leaving both fields at zero on every iteration. The result is an infinite loop in kernel context, blocking the calling thread and pegging a CPU core indefinitely. Fix this by rejecting a multisync extension where both in_sync_count and out_sync_count are zero in v3d_get_multisync_submit_deps(). An empty multisync carries no synchronization information and serves no useful purpose, so returning -EINVAL for such an extension is the correct defense against this attack vector.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-08
Last Modified
2026-06-08
Generated
2026-06-09
AI Q&A
2026-06-08
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in the Linux kernel's drm/v3d component, where a function called v3d_get_extensions() processes a userspace-provided singly-linked list of ioctl extensions without limiting the length of the chain.

A local user can exploit this by crafting a self-referential extension (where the extension's next pointer points to itself) with both in_sync_count and out_sync_count set to zero. This bypasses the existing guard that prevents duplicate extensions because the guard only triggers if either count is non-zero.

Since the function v3d_get_multisync_post_deps() returns immediately when these counts are zero, the loop never terminates, causing an infinite loop in kernel context. This infinite loop blocks the calling thread and causes a CPU core to be fully utilized indefinitely.

The fix involves rejecting any multisync extension where both in_sync_count and out_sync_count are zero, as such an extension carries no synchronization information and serves no useful purpose.

Impact Analysis

This vulnerability can cause a denial of service condition on the affected system.

By exploiting the infinite loop in kernel context, a local user can block the calling thread and cause a CPU core to be fully consumed indefinitely, potentially degrading system performance or causing system instability.

Mitigation Strategies

The vulnerability is fixed by rejecting multisync extensions where both in_sync_count and out_sync_count are zero in the Linux kernel's v3d driver. To mitigate this vulnerability, you should update your Linux kernel to a version that includes this fix.

This prevents the infinite loop caused by a crafted self-referential extension that leads to CPU core pegging and blocking of the calling thread.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-46314. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart