CVE-2026-46314: drm/v3d: Reject empty multisync extension to prevent infinite loop

Published Jun 8, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

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

v3dgetextensions() 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 insynccount and outsynccount, which bypasses the existing duplicate- extension guard:

if (se->insynccount || se->outsynccount) return -EINVAL;

The guard never fires because v3dgetmultisyncpostdeps() 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 insynccount and outsynccount are zero in v3dgetmultisyncsubmitdeps(). 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.

Affected Software

4 affected components
Linux Linux kernel (drm/v3d)
Linux Linux kernel>=5.16<6.1.176
Linux Linux kernel>=6.2<6.18.33
Linux Linux kernel>=6.19<7.0.9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    In v3d_get_extensions()/multisync extension processing, reject a multisync extension where se->in_sync_count == 0 and se->out_sync_count == 0 by returning -EINVAL (the guard should fail when count is zero to prevent the infinite loop).

    Linux kernel DRM/v3d multisync extension handling reject empty multisync extension when both in_sync_count and out_sync_count are zero = return -EINVAL

Event History

Jun 8, 2026
CVE Published
via MITRE·03:50 PM
Data Sourced
via MITRE·03:50 PM
Description
Data Sourced
via NVD·05:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-46314?

CVE-2026-46314 has a risk score of 18, indicating it poses a significant security threat.

2

How do I fix CVE-2026-46314?

To address CVE-2026-46314, update to the latest version of the Linux kernel that includes the patch for this vulnerability.

3

Who is affected by CVE-2026-46314?

CVE-2026-46314 affects users of the Linux kernel utilizing the drm/v3d driver.

4

What causes the vulnerability in CVE-2026-46314?

CVE-2026-46314 is caused by the drm/v3d driver processing an unbounded, userspace-supplied list of ioctl extensions.

5

Is CVE-2026-46314 exploitable remotely?

CVE-2026-46314 is not remotely exploitable; it requires local user access to exploit the vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203