CVE-2026-46314
Last modified
CVE-2026-46314 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.11% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.16, < 6.1.176 |
| Linux | Linux Kernel | >= 6.2, < 6.18.33 |
| Linux | Linux Kernel | >= 6.19, < 7.0.9 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-46314?
How severe is CVE-2026-46314?
How do I fix CVE-2026-46314?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-46309In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-4631Cockpit's remote login feature passes user-supplied hostname…9.8
- CVE-2026-46310In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46311In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46312In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46313In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46315In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46316In the Linux kernel, the following vulnerability has been re…9.3
- CVE-2026-46317In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-46318In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46319In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-4632A weakness has been identified in itsourcecode Online Enroll…7.3
Are you affected by CVE-2026-46314?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
