Skip to main content

Syself security assessment

CVE-2026-52965 in Syself Kubernetes

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.

Syself Autopilot is fully managed Kubernetes on your own Hetzner servers. Every cluster runs a versioned cluster stack release, and this page tracks how CVE-2026-52965 affects the kernel component those releases ship, based on Syself's assessments. For the general description and scoring of the vulnerability, see the references.

Not affected in 1.36 v10 Upstream severity: Medium Last assessed

Syself Kubernetes is not affected by CVE-2026-52965 in any of the 10 releases that ship kernel.

Reason: An attacker cannot reach the vulnerable code.

Our assessment in 1.36 v10, the newest release with this finding

kernel 6.18.63
Not affected Medium
An attacker cannot reach the vulnerable code

This flaw can make a graphics-memory routine loop and waste processor time, but only for a program with direct access to a graphics device. Workloads are given no such access, so it cannot be reached.

Syself Security

Status by release

ReleasesComponentStatusReasonFixed inAssessment
kernel 6.18.42, 6.18.45, 6.18.49, 6.18.54, 6.18.59, 6.18.63Not affectedAn attacker cannot reach the vulnerable code—Details

Frequently asked questions

My scanner reports CVE-2026-52965 in a Syself cluster. What should I do?

Scanners such as Trivy and Grype match package versions, so they report CVE-2026-52965 whenever the vulnerable version is present, even when it cannot be exploited. Syself publishes its assessments as a VEX (Vulnerability Exploitability eXchange) document for every release. Pass it to your scanner to drop the findings Syself has assessed as not affected or fixed:

trivy image --vex hetzner-apalla-1-36-v10-advisory.openvex.json <image>
grype <image> --vex hetzner-apalla-1-36-v10-advisory.openvex.json

Each assessment applies to the package version it names. A finding stays in the report when the document has no assessment for that package, or when the vulnerability is still affected or under investigation.

Download the OpenVEX document for 1.36 v10

What do the statuses mean?

Not affected
The component ships in the release, but Syself has assessed that the vulnerability cannot be exploited there. The reason column says why.
Fixed
The release ships a version of the component that carries the fix.
Affected
The vulnerability can affect the release. Upgrade to a release listed as fixed once one is available.
Under Investigation
Syself is still assessing whether the vulnerability affects the release.

Why can the severity differ from other sources?

The severity shown is the upstream rating of the vulnerability itself. The status is Syself's assessment of whether it can be exploited in the components Syself ships, so a critical vulnerability can still be not affected.

References

Think this assessment is wrong, or found a vulnerability in Syself? Contact us.