CVE-2026-46314

drm/v3d: Reject empty multisync extension to prevent infinite loop

State
Published
Severity
Not scored
Published
Jun 8, 2026
Updated
Jun 19, 2026
Reserved
May 13, 2026

Read the record on cve.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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • e4165ae8304e5ea822fbe5909dd3be5445c058b7 to before 309abbddeca0c12714721928a819ef45e5710998Affected
  • e4165ae8304e5ea822fbe5909dd3be5445c058b7 to before 4fa42a249e8cd6ed17aea04e5695b6e9001f2433Affected
  • e4165ae8304e5ea822fbe5909dd3be5445c058b7 to before 9c5164781cb388d219d8f49fa0f0b04cf86ad544Affected
  • e4165ae8304e5ea822fbe5909dd3be5445c058b7 to before fb44d589bf3148e13452185a6e772a7efbf2d684Affected
LinuxLinux
  • 5.16Affected
  • before 5.16Not affected
  • 6.1.176 through 6.1.*Not affected
  • 6.18.33 through 6.18.*Not affected
  • 7.0.9 through 7.0.*Not affected
  • 7.1 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.