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

drm/ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout failure

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 43 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 24 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 43 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.

17 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 13 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 · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, 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-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-azure-fde-6.14Affected, 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-nvidia-6.14Affected, 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-gcp-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-hwe-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-lowlatency-hwe-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-nvidia-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-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-oracle-6.14Affected, 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
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-52965 · CSAF 2.0 · revision 5 · interimSUSE Product Security TeamCVE-2026-52965
30 known affected

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

  • cluster-md-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • dlm-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • gfs2-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-devel as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-macros as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-source as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • ocfs2-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • cluster-md-kmp-default as component of SUSE Linux Enterprise Server 15 SP6
  • dlm-kmp-default as component of SUSE Linux Enterprise Server 15 SP6
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout failure When ttm_tt_swapout() fails, the current code calls ttm_resource_add_bulk_move() followed by ttm_resource_move_to_lru_tail() to restore the resource's bulk_move membership. However, ttm_resource_move_to_lru_tail() places the resource at the tail of the LRU list which, relative to the walk cursor's hitch node (placed immediately after the resource when it was yielded), puts the resource *in front of the* the hitch. The next list_for_each_entry_continue() from the hitch finds the same resource again, causing an infinite loop. Fix by deferring del_bulk_move to the success path only. On the success path, TTM_TT_FLAG_SWAPPED has just been set by ttm_tt_swapout() but the resource is still tracked in the bulk_move range, so ttm_resource_del_bulk_move()'s !ttm_resource_unevictable() guard would incorrectly skip the removal. Introduce ttm_resource_del_bulk_move_unevictable() which bypasses that guard.
Remediation
No remediation text is recorded.
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-38833

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 43 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/ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout failure When ttm_tt_swapout() fails, the current code calls ttm_resource_add_bulk_move() followed by ttm_resource_move_to_lru_tail() to restore the resource's bulk_move membership. However, ttm_resource_move_to_lru_tail() places the resource at the tail of the LRU list which, relative to the walk cursor's hitch node (placed immediately after the resource when it was yielded), puts the resource *in front of the* the hitch. The next list_for_each_entry_continue() from the hitch finds the same resource again, causing an infinite loop. Fix by deferring del_bulk_move to the success path only. On the success path, TTM_TT_FLAG_SWAPPED has just been set by ttm_tt_swapout() but the resource is still tracked in the bulk_move range, so ttm_resource_del_bulk_move()'s !ttm_resource_unevictable() guard would incorrectly skip the removal. Introduce ttm_resource_del_bulk_move_unevictable() which bypasses that guard.

What

In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout failure When ttm_tt_swapout() fails, the current code calls ttm_resource_add_bulk_move() followed by ttm_resource_move_to_lru_tail() to restore the resource's bulk_move membership. However, ttm_resource_move_to_lru_tail() places the resource at the tail of the LRU list which, relative to the walk cursor's hitch node (placed immediately after the resource when it was yielded), puts the resource *in front of the* the hitch. The next list_for_each_entry_continue() from the hitch finds the same resource again, causing an infinite loop. Fix by deferring del_bulk_move to the success path only. On the success path, TTM_TT_FLAG_SWAPPED has just been set by ttm_tt_swapout() but the resource is still tracked in the bulk_move range, so ttm_resource_del_bulk_move()'s !ttm_resource_unevictable() guard would incorrectly skip the removal. Introduce ttm_resource_del_bulk_move_unevictable() which bypasses that guard.

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/ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout failure When ttm_tt_swapout() fails, the current code calls ttm_resource_add_bulk_move() followed by ttm_resource_move_to_lru_tail() to restore the resource's bulk_move membership. However, ttm_resource_move_to_lru_tail() places the resource at the tail of the LRU list which, relative to the walk cursor's hitch node (placed immediately after the resource when it was yielded), puts the resource *in front of the* the hitch. The next list_for_each_entry_continue() from the hitch finds the same resource again, causing an infinite loop. Fix by deferring del_bulk_move to the success path only. On the success path, TTM_TT_FLAG_SWAPPED has just been set by ttm_tt_swapout() but the resource is still tracked in the bulk_move range, so ttm_resource_del_bulk_move()'s !ttm_resource_unevictable() guard would incorrectly skip the removal. Introduce ttm_resource_del_bulk_move_unevictable() which bypasses that guard.

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-2077Linux Kernel: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260701Security Bulletin 1 July 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 1 July 2026, published on 1 July 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-52956 Référence CVE CVE-2026-52957 https://www.cve.org/CVERecord?id=CVE-2026-52957 Référence CVE CVE-2026-52958 https://www.cve.org/CVERecord?id=CVE-2026-52958 Référence CVE CVE-2026-52959 https://www.cve.org/CVERecord?id=CVE-2026-52959 Référence CVE CVE-2026-52960 https://www.cve.org/CVERecord?id=CVE-2026-52960 Référence CVE CVE-2026-52961 https://www.cve.org/CVERecord?id=CVE-2026-52961 Référence CVE CVE-2026-52962 https://www.cve.org/CVERecord?id=CVE-2026-52962 Référence CVE CVE-2026-52963 https://www.cve.org/CVERecord?id=CVE-2026-52963 Référence CVE CVE-2026-52964 https://www.cve.org/CVERecord?id=CVE-2026-52964 Référence CVE CVE-2026-52965 https://www.cve.org/CVERecord?id=CVE-2026-52965 Référence CVE CVE-2026-52967 https://www.cve.org/CVERecord?id=CVE-2026-52967 Référence CVE CVE-2026-52968 https://www.cve.org/CVERecord?id=CVE-2026-52968 Référence CVE CVE-2026-52969 https://www.cve.org/CVERecord?id=CVE-2026-52969 Référence CVE CVE-2026-52970 https://www.cve.org/CVERecord?id=CVE-2026-52970 Référence CVE CVE-2026-52971 https://www.cve.org/CVERecord?id=CVE-2026-52971 Référence CVE CVE-2026-52973 https://www.cve.org/CVERecord?id=CVE-2026-52973 Référence CVE CVE-2026-52974 https://www.cve.org/CVERecord?id=CVE-2026-52974 Référence CVE CVE-2026-52975 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-52956 Référence CVE CVE-2026-52957 https://www.cve.org/CVERecord?id=CVE-2026-52957 Référence CVE CVE-2026-52958 https://www.cve.org/CVERecord?id=CVE-2026-52958 Référence CVE CVE-2026-52959 https://www.cve.org/CVERecord?id=CVE-2026-52959 Référence CVE CVE-2026-52960 https://www.cve.org/CVERecord?id=CVE-2026-52960 Référence CVE CVE-2026-52961 https://www.cve.org/CVERecord?id=CVE-2026-52961 Référence CVE CVE-2026-52962 https://www.cve.org/CVERecord?id=CVE-2026-52962 Référence CVE CVE-2026-52963 https://www.cve.org/CVERecord?id=CVE-2026-52963 Référence CVE CVE-2026-52964 https://www.cve.org/CVERecord?id=CVE-2026-52964 Référence CVE CVE-2026-52965 https://www.cve.org/CVERecord?id=CVE-2026-52965 Référence CVE CVE-2026-52967 https://www.cve.org/CVERecord?id=CVE-2026-52967 Référence CVE CVE-2026-52968 https://www.cve.org/CVERecord?id=CVE-2026-52968 Référence CVE CVE-2026-52969 https://www.cve.org/CVERecord?id=CVE-2026-52969 Référence CVE CVE-2026-52970 https://www.cve.org/CVERecord?id=CVE-2026-52970 Référence CVE CVE-2026-52971 https://www.cve.org/CVERecord?id=CVE-2026-52971 Référence CVE CVE-2026-52973 https://www.cve.org/CVERecord?id=CVE-2026-52973 Référence CVE CVE-2026-52974 https://www.cve.org/CVERecord?id=CVE-2026-52974 Référence CVE CVE-2026-52975 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-52956 Référence CVE CVE-2026-52957 https://www.cve.org/CVERecord?id=CVE-2026-52957 Référence CVE CVE-2026-52958 https://www.cve.org/CVERecord?id=CVE-2026-52958 Référence CVE CVE-2026-52959 https://www.cve.org/CVERecord?id=CVE-2026-52959 Référence CVE CVE-2026-52960 https://www.cve.org/CVERecord?id=CVE-2026-52960 Référence CVE CVE-2026-52961 https://www.cve.org/CVERecord?id=CVE-2026-52961 Référence CVE CVE-2026-52962 https://www.cve.org/CVERecord?id=CVE-2026-52962 Référence CVE CVE-2026-52963 https://www.cve.org/CVERecord?id=CVE-2026-52963 Référence CVE CVE-2026-52964 https://www.cve.org/CVERecord?id=CVE-2026-52964 Référence CVE CVE-2026-52965 https://www.cve.org/CVERecord?id=CVE-2026-52965 Référence CVE CVE-2026-52967 https://www.cve.org/CVERecord?id=CVE-2026-52967 Référence CVE CVE-2026-52968 https://www.cve.org/CVERecord?id=CVE-2026-52968 Référence CVE CVE-2026-52969 https://www.cve.org/CVERecord?id=CVE-2026-52969 Référence CVE CVE-2026-52970 https://www.cve.org/CVERecord?id=CVE-2026-52970 Référence CVE CVE-2026-52971 https://www.cve.org/CVERecord?id=CVE-2026-52971 Référence CVE CVE-2026-52973 https://www.cve.org/CVERecord?id=CVE-2026-52973 Référence CVE CVE-2026-52974 https://www.cve.org/CVERecord?id=CVE-2026-52974 Référence CVE CVE-2026-52975 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-52956 Référence CVE CVE-2026-52957 https://www.cve.org/CVERecord?id=CVE-2026-52957 Référence CVE CVE-2026-52958 https://www.cve.org/CVERecord?id=CVE-2026-52958 Référence CVE CVE-2026-52959 https://www.cve.org/CVERecord?id=CVE-2026-52959 Référence CVE CVE-2026-52960 https://www.cve.org/CVERecord?id=CVE-2026-52960 Référence CVE CVE-2026-52961 https://www.cve.org/CVERecord?id=CVE-2026-52961 Référence CVE CVE-2026-52962 https://www.cve.org/CVERecord?id=CVE-2026-52962 Référence CVE CVE-2026-52963 https://www.cve.org/CVERecord?id=CVE-2026-52963 Référence CVE CVE-2026-52964 https://www.cve.org/CVERecord?id=CVE-2026-52964 Référence CVE CVE-2026-52965 https://www.cve.org/CVERecord?id=CVE-2026-52965 Référence CVE CVE-2026-52967 https://www.cve.org/CVERecord?id=CVE-2026-52967 Référence CVE CVE-2026-52968 https://www.cve.org/CVERecord?id=CVE-2026-52968 Référence CVE CVE-2026-52969 https://www.cve.org/CVERecord?id=CVE-2026-52969 Référence CVE CVE-2026-52970 https://www.cve.org/CVERecord?id=CVE-2026-52970 Référence CVE CVE-2026-52971 https://www.cve.org/CVERecord?id=CVE-2026-52971 Référence CVE CVE-2026-52973 https://www.cve.org/CVERecord?id=CVE-2026-52973 Référence CVE CVE-2026-52974 https://www.cve.org/CVERecord?id=CVE-2026-52974 Référence CVE CVE-2026-52975 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-52956 Référence CVE CVE-2026-52957 https://www.cve.org/CVERecord?id=CVE-2026-52957 Référence CVE CVE-2026-52958 https://www.cve.org/CVERecord?id=CVE-2026-52958 Référence CVE CVE-2026-52959 https://www.cve.org/CVERecord?id=CVE-2026-52959 Référence CVE CVE-2026-52960 https://www.cve.org/CVERecord?id=CVE-2026-52960 Référence CVE CVE-2026-52961 https://www.cve.org/CVERecord?id=CVE-2026-52961 Référence CVE CVE-2026-52962 https://www.cve.org/CVERecord?id=CVE-2026-52962 Référence CVE CVE-2026-52963 https://www.cve.org/CVERecord?id=CVE-2026-52963 Référence CVE CVE-2026-52964 https://www.cve.org/CVERecord?id=CVE-2026-52964 Référence CVE CVE-2026-52965 https://www.cve.org/CVERecord?id=CVE-2026-52965 Référence CVE CVE-2026-52967 https://www.cve.org/CVERecord?id=CVE-2026-52967 Référence CVE CVE-2026-52968 https://www.cve.org/CVERecord?id=CVE-2026-52968 Référence CVE CVE-2026-52969 https://www.cve.org/CVERecord?id=CVE-2026-52969 Référence CVE CVE-2026-52970 https://www.cve.org/CVERecord?id=CVE-2026-52970 Référence CVE CVE-2026-52971 https://www.cve.org/CVERecord?id=CVE-2026-52971 Référence CVE CVE-2026-52973 https://www.cve.org/CVERecord?id=CVE-2026-52973 Référence CVE CVE-2026-52974 https://www.cve.org/CVERecord?id=CVE-2026-52974 Référence CVE CVE-2026-52975 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-52956 Référence CVE CVE-2026-52957 https://www.cve.org/CVERecord?id=CVE-2026-52957 Référence CVE CVE-2026-52958 https://www.cve.org/CVERecord?id=CVE-2026-52958 Référence CVE CVE-2026-52959 https://www.cve.org/CVERecord?id=CVE-2026-52959 Référence CVE CVE-2026-52960 https://www.cve.org/CVERecord?id=CVE-2026-52960 Référence CVE CVE-2026-52961 https://www.cve.org/CVERecord?id=CVE-2026-52961 Référence CVE CVE-2026-52962 https://www.cve.org/CVERecord?id=CVE-2026-52962 Référence CVE CVE-2026-52963 https://www.cve.org/CVERecord?id=CVE-2026-52963 Référence CVE CVE-2026-52964 https://www.cve.org/CVERecord?id=CVE-2026-52964 Référence CVE CVE-2026-52965 https://www.cve.org/CVERecord?id=CVE-2026-52965 Référence CVE CVE-2026-52967 https://www.cve.org/CVERecord?id=CVE-2026-52967 Référence CVE CVE-2026-52968 https://www.cve.org/CVERecord?id=CVE-2026-52968 Référence CVE CVE-2026-52969 https://www.cve.org/CVERecord?id=CVE-2026-52969 Référence CVE CVE-2026-52970 https://www.cve.org/CVERecord?id=CVE-2026-52970 Référence CVE CVE-2026-52971 https://www.cve.org/CVERecord?id=CVE-2026-52971 Référence CVE CVE-2026-52973 https://www.cve.org/CVERecord?id=CVE-2026-52973 Référence CVE CVE-2026-52974 https://www.cve.org/CVERecord?id=CVE-2026-52974 Référence CVE CVE-2026-52975 https://www.cve.org/CVERecord?id=

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。drm/ttm: ttm_tt_swapout()が失敗した場合に、ttm_bo_swapout()で無限LRU走査が発生する問題の修正です。ttm_tt_swapout()が失敗すると、現在のコードはttm_resource_add_bulk_move()を呼び出し、その後ttm_resource_move_to_lru_tail()を呼び出してリソースのbulk_moveメンバーシップを復元しようとします。しかし、ttm_resource_move_to_lru_tail()はリソースをLRUリストの末尾に配置しますが、これはwalkカーソルのヒッチノード（リソースが譲渡された直後に配置されている）の相対位置から見るとリソースをヒッチの前に置くことになり、list_for_each_entry_continue()がヒッチからの次の要素として同じリソースを再び見つけてしまって無限ループが発生します。修正は、del_bulk_moveの呼び出しを成功パスのみに遅延させることで行われました。成功パスでは、ttm_tt_swapout()によってTTM_TT_FLAG_SWAPPEDが設定された直後であるものの、リソースはまだbulk_move範囲で管理されています。そのため、ttm_resource_del_bulk_move()の!ttm_resource_unevictable()ガードによって誤って削除がスキップされる可能性があります。これを回避するために、ttm_resource_del_bulk_move_unevictable()を導入し、該当ガードをバイパスするようにしました。

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: < 6.13, 7.0.10 ≤ 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 24 Jun 2026 · Last source change 24 Jun 2026, 16:28 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-38833
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceCVE/CNA references
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
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-38833↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
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-52965 · cve.blacktree.nl