5.5

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

Analyzed
AliasesUBUNTU-CVE-2026-46314DEBIAN-CVE-2026-46314CGA-3vjp-8593-hppj
Published 08-06-2026Last modified 19-06-2026

Vulnerability summary

CVE-2026-46314 is a medium (CVSS 5.5) Loop with Unreachable Exit Condition vulnerability in linux. EPSS estimates a 0.11% chance of exploitation in the next 30 days, higher than 1.5% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 5.5, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
5.5/10
010
Medium · v3.1 (NVD)
EPSS score
0.11%
0%100%
Low · -0.05 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 37 · Related 37

Timeline

  1. 08-06-2026
    PublishedVulnerability first disclosed.
  2. 19-06-2026
    Last modifiedVulnerability information updated.

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 metrics

4 scores · 3 sources · 2 versions

EPSS trend

Probability

0.11%

Chance of exploitation in the next 30 days

Percentile

2%

Versus all other CVEs

30-day change

Decrease -0.05 pp

From 0.16% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu139 products
  • linux< 6.8.0-136.136 | All versions (No fix recorded) | < 7.0.0-28.28
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-aws< 6.8.0-1061.64 | All versions (No fix recorded) | < 7.0.0-1009.9
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Chainguard5 products
  • linux-aws-6.12All versions (No fix recorded)
  • linux-azure-6.12All versions (No fix recorded)
  • linux-gcp-6.12All versions (No fix recorded)
  • linux-qemu-6.12All versions (No fix recorded)
  • linux-vmware-6.12All versions (No fix recorded)
Linux2 products
  • linux≥ e4165ae8304e5ea822fbe5909dd3be5445c058b7, < 309abbddeca0c12714721928a819ef45e5710998 | ≥ e4165ae8304e5ea822fbe5909dd3be5445c058b7, < 4fa42a249e8cd6ed17aea04e5695b6e9001f2433 | ≥ e4165ae8304e5ea822fbe5909dd3be5445c058b7, < 9c5164781cb388d219d8f49fa0f0b04cf86ad544 | ≥ e4165ae8304e5ea822fbe5909dd3be5445c058b7, < fb44d589bf3148e13452185a6e772a7efbf2d684 | 5.16
  • linux_kernel≥ 5.16, < 6.1.176 | ≥ 6.2, < 6.18.33 | ≥ 6.19, < 7.0.9
Debian1 product
  • linux< 6.1.176-1 | All versions (No fix recorded) | < 7.0.9-1

4 vendors · 147 products

References

33 links
Show all 33 references