BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-46314High confidence

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

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 19 Jun 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.16% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 21 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.9-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.9-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-46314 · CSAF 2.0 · revision 15 · interimSUSE Product Security TeamCVE-2026-46314
105 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
Summary
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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-35124

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

A malformed condition prevents a loop from making progress or terminating, allowing resource exhaustion.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

A malformed condition prevents a loop from making progress or terminating, allowing resource exhaustion.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Loop with Unreachable Exit Condition ('Infinite Loop') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-835 ↗

CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop'). The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-835
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-1827Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht bekannte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260610Security Bulletin 10 Jun 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 10 Jun 2026, published on 10 June 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46305 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46308 https://www.cve.org/CVERecord?id=CVE-2026-46308 Référence CVE CVE-2026-46309 https://www.cve.org/CVERecord?id=CVE-2026-46309 Référence CVE CVE-2026-46310 https://www.cve.org/CVERecord?id=CVE-2026-46310 Référence CVE CVE-2026-46311 https://www.cve.org/CVERecord?id=CVE-2026-46311 Référence CVE CVE-2026-46312 https://www.cve.org/CVERecord?id=CVE-2026-46312 Référence CVE CVE-2026-46313 https://www.cve.org/CVERecord?id=CVE-2026-46313 Référence CVE CVE-2026-46314 https://www.cve.org/CVERecord?id=CVE-2026-46314 Référence CVE CVE-2026-46315 https://www.cve.org/CVERecord?id=CVE-2026-46315 Référence CVE CVE-2026-46316 https://www.cve.org/CVERecord?id=CVE-2026-46316 Référence CVE CVE-2026-46317 https://www.cve.org/CVERecord?id=CVE-2026-46317 Référence CVE CVE-2026-46318 https://www.cve.org/CVERecord?id=CVE-2026-46318 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46321 https://www.cve.org/CVERecord?id=CVE-2026-46321 Référence CVE CVE-2026-46322 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46305 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46308 https://www.cve.org/CVERecord?id=CVE-2026-46308 Référence CVE CVE-2026-46309 https://www.cve.org/CVERecord?id=CVE-2026-46309 Référence CVE CVE-2026-46310 https://www.cve.org/CVERecord?id=CVE-2026-46310 Référence CVE CVE-2026-46311 https://www.cve.org/CVERecord?id=CVE-2026-46311 Référence CVE CVE-2026-46312 https://www.cve.org/CVERecord?id=CVE-2026-46312 Référence CVE CVE-2026-46313 https://www.cve.org/CVERecord?id=CVE-2026-46313 Référence CVE CVE-2026-46314 https://www.cve.org/CVERecord?id=CVE-2026-46314 Référence CVE CVE-2026-46315 https://www.cve.org/CVERecord?id=CVE-2026-46315 Référence CVE CVE-2026-46316 https://www.cve.org/CVERecord?id=CVE-2026-46316 Référence CVE CVE-2026-46317 https://www.cve.org/CVERecord?id=CVE-2026-46317 Référence CVE CVE-2026-46318 https://www.cve.org/CVERecord?id=CVE-2026-46318 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46321 https://www.cve.org/CVERecord?id=CVE-2026-46321 Référence CVE CVE-2026-46322 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46305 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46308 https://www.cve.org/CVERecord?id=CVE-2026-46308 Référence CVE CVE-2026-46309 https://www.cve.org/CVERecord?id=CVE-2026-46309 Référence CVE CVE-2026-46310 https://www.cve.org/CVERecord?id=CVE-2026-46310 Référence CVE CVE-2026-46311 https://www.cve.org/CVERecord?id=CVE-2026-46311 Référence CVE CVE-2026-46312 https://www.cve.org/CVERecord?id=CVE-2026-46312 Référence CVE CVE-2026-46313 https://www.cve.org/CVERecord?id=CVE-2026-46313 Référence CVE CVE-2026-46314 https://www.cve.org/CVERecord?id=CVE-2026-46314 Référence CVE CVE-2026-46315 https://www.cve.org/CVERecord?id=CVE-2026-46315 Référence CVE CVE-2026-46316 https://www.cve.org/CVERecord?id=CVE-2026-46316 Référence CVE CVE-2026-46317 https://www.cve.org/CVERecord?id=CVE-2026-46317 Référence CVE CVE-2026-46318 https://www.cve.org/CVERecord?id=CVE-2026-46318 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46321 https://www.cve.org/CVERecord?id=CVE-2026-46321 Référence CVE CVE-2026-46322 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46305 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46308 https://www.cve.org/CVERecord?id=CVE-2026-46308 Référence CVE CVE-2026-46309 https://www.cve.org/CVERecord?id=CVE-2026-46309 Référence CVE CVE-2026-46310 https://www.cve.org/CVERecord?id=CVE-2026-46310 Référence CVE CVE-2026-46311 https://www.cve.org/CVERecord?id=CVE-2026-46311 Référence CVE CVE-2026-46312 https://www.cve.org/CVERecord?id=CVE-2026-46312 Référence CVE CVE-2026-46313 https://www.cve.org/CVERecord?id=CVE-2026-46313 Référence CVE CVE-2026-46314 https://www.cve.org/CVERecord?id=CVE-2026-46314 Référence CVE CVE-2026-46315 https://www.cve.org/CVERecord?id=CVE-2026-46315 Référence CVE CVE-2026-46317 https://www.cve.org/CVERecord?id=CVE-2026-46317 Référence CVE CVE-2026-46318 https://www.cve.org/CVERecord?id=CVE-2026-46318 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46321 https://www.cve.org/CVERecord?id=CVE-2026-46321 Référence CVE CVE-2026-46322 https://www.cve.org/CVERecord?id=CVE-2026-46322 Référence CVE CVE-2026-46324 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0956Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-46242 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46244 https://www.cve.org/CVERecord?id=CVE-2026-46244 Référence CVE CVE-2026-46253 https://www.cve.org/CVERecord?id=CVE-2026-46253 Référence CVE CVE-2026-46254 https://www.cve.org/CVERecord?id=CVE-2026-46254 Référence CVE CVE-2026-46259 https://www.cve.org/CVERecord?id=CVE-2026-46259 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46289 https://www.cve.org/CVERecord?id=CVE-2026-46289 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46314 https://www.cve.org/CVERecord?id=CVE-2026-46314 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46322 https://www.cve.org/CVERecord?id=CVE-2026-46322 Référence CVE CVE-2026-46328 https://www.cve.org/CVERecord?id=CVE-2026-46328 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-52908 https://www.cve.org/CVERecord?id=CVE-2026-52908 Référence CVE CVE-2026-52909 https://www.cve.org/CVERecord?id=CVE-2026-52909 Référence CVE CVE-2026-52919 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46305 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46308 https://www.cve.org/CVERecord?id=CVE-2026-46308 Référence CVE CVE-2026-46309 https://www.cve.org/CVERecord?id=CVE-2026-46309 Référence CVE CVE-2026-46310 https://www.cve.org/CVERecord?id=CVE-2026-46310 Référence CVE CVE-2026-46311 https://www.cve.org/CVERecord?id=CVE-2026-46311 Référence CVE CVE-2026-46312 https://www.cve.org/CVERecord?id=CVE-2026-46312 Référence CVE CVE-2026-46313 https://www.cve.org/CVERecord?id=CVE-2026-46313 Référence CVE CVE-2026-46314 https://www.cve.org/CVERecord?id=CVE-2026-46314 Référence CVE CVE-2026-46315 https://www.cve.org/CVERecord?id=CVE-2026-46315 Référence CVE CVE-2026-46316 https://www.cve.org/CVERecord?id=CVE-2026-46316 Référence CVE CVE-2026-46317 https://www.cve.org/CVERecord?id=CVE-2026-46317 Référence CVE CVE-2026-46318 https://www.cve.org/CVERecord?id=CVE-2026-46318 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46321 https://www.cve.org/CVERecord?id=CVE-2026-46321 Référence CVE CVE-2026-46322 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0927Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-46276 Référence CVE CVE-2026-46285 https://www.cve.org/CVERecord?id=CVE-2026-46285 Référence CVE CVE-2026-46286 https://www.cve.org/CVERecord?id=CVE-2026-46286 Référence CVE CVE-2026-46289 https://www.cve.org/CVERecord?id=CVE-2026-46289 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46312 https://www.cve.org/CVERecord?id=CVE-2026-46312 Référence CVE CVE-2026-46313 https://www.cve.org/CVERecord?id=CVE-2026-46313 Référence CVE CVE-2026-46314 https://www.cve.org/CVERecord?id=CVE-2026-46314 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46321 https://www.cve.org/CVERecord?id=CVE-2026-46321 Référence CVE CVE-2026-46322 https://www.cve.org/CVERecord?id=CVE-2026-46322 Référence CVE CVE-2026-46328 https://www.cve.org/CVERecord?id=CVE-2026-46328 Référence CVE CVE-2026-46330 https://www.cve.org/CVERecord?id=CVE-2026-46330 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-52904 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46305 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46308 https://www.cve.org/CVERecord?id=CVE-2026-46308 Référence CVE CVE-2026-46309 https://www.cve.org/CVERecord?id=CVE-2026-46309 Référence CVE CVE-2026-46310 https://www.cve.org/CVERecord?id=CVE-2026-46310 Référence CVE CVE-2026-46311 https://www.cve.org/CVERecord?id=CVE-2026-46311 Référence CVE CVE-2026-46312 https://www.cve.org/CVERecord?id=CVE-2026-46312 Référence CVE CVE-2026-46313 https://www.cve.org/CVERecord?id=CVE-2026-46313 Référence CVE CVE-2026-46314 https://www.cve.org/CVERecord?id=CVE-2026-46314 Référence CVE CVE-2026-46315 https://www.cve.org/CVERecord?id=CVE-2026-46315 Référence CVE CVE-2026-46316 https://www.cve.org/CVERecord?id=CVE-2026-46316 Référence CVE CVE-2026-46317 https://www.cve.org/CVERecord?id=CVE-2026-46317 Référence CVE CVE-2026-46318 https://www.cve.org/CVERecord?id=CVE-2026-46318 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46321 https://www.cve.org/CVERecord?id=CVE-2026-46321 Référence CVE CVE-2026-46322 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0862Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-46292 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46296 https://www.cve.org/CVERecord?id=CVE-2026-46296 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=CVE-2026-46299 Référence CVE CVE-2026-46301 https://www.cve.org/CVERecord?id=CVE-2026-46301 Référence CVE CVE-2026-46303 https://www.cve.org/CVERecord?id=CVE-2026-46303 Référence CVE CVE-2026-46304 https://www.cve.org/CVERecord?id=CVE-2026-46304 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46314 https://www.cve.org/CVERecord?id=CVE-2026-46314 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46321 https://www.cve.org/CVERecord?id=CVE-2026-46321 Référence CVE CVE-2026-46322 https://www.cve.org/CVERecord?id=CVE-2026-46322 Référence CVE CVE-2026-46323 https://www.cve.org/CVERecord?id=CVE-2026-46323 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-52909 https://www.cve.org/CVERecord?id=CVE-2026-52909 Référence CVE CVE-2026-52910 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-023161LinuxのLinux Kernelにおける無限ループに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました:drm/v3dにおける無限ループを防止するための空のマルチシンク拡張の拒否問題です。v3d_get_extensions()は、ユーザースペースから提供される単方向連結リストのioctl拡張を、チェーンの長さに制限なく辿ります。ローカルユーザは、in_sync_countとout_sync_countがゼロの自己参照的拡張(ext->next == &ext)を作成でき、既存の重複拡張ガードを回避します。具体的には、以下のガード文があります: if (se->in_sync_count || se->out_sync_count) return -EINVAL;しかしこのガードは、v3d_get_multisync_post_deps()がカウントがゼロの場合に即時に戻るため発動せず、その結果、各イテレーションで両フィールドがゼロのまま維持されます。その結果、カーネルコンテキスト内で無限ループが発生し、呼び出しスレッドがブロックされ、CPUコアが無期限に占有されてしまいます。この問題は、v3d_get_multisync_submit_deps()内でin_sync_countおよびout_sync_countの両方がゼロのマルチシンク拡張を拒否することで修正されました。空のマルチシンクは同期情報を持たず、有用な目的を果たさないため、この種の拡張に対して-EINVALを返すことが、この攻撃ベクターに対する適切な防御策となります。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.16, 6.1.176 ≤ 6.1.*, 6.18.33 ≤ 6.18.*, 7.0.9 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 8 Jun 2026 · Last source change 19 Jun 2026, 12:00 UTC · CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-35124
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-46314 · cve.blacktree.nl