Syself security assessment
dmaengine: idxd: fix fdev setup failure cleanup in idxd_cdev_open()
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-74574 affects the kernel component those releases ship, based on Syself's assessments. For the general description and scoring of the vulnerability, see the references.
Syself Kubernetes is not affected by CVE-2026-74574 in any of the 2 releases that ship kernel.
Reason: An attacker cannot reach the vulnerable code.
This flaw is in the driver for an on-chip data accelerator and needs a program to open that device. Workloads are given no such device, so only local code could reach it and the flaw cannot be triggered here.
Syself Security| Releases | Component | Status | Reason | Fixed in | Assessment |
|---|---|---|---|---|---|
| kernel 6.18.42 | Not affected | An attacker cannot reach the vulnerable code | — | Details |
Scanners such as Trivy and Grype match package versions, so they report CVE-2026-74574 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-v2-advisory.openvex.json <image>
grype <image> --vex hetzner-apalla-1-36-v2-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 v2The 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.
Think this assessment is wrong, or found a vulnerability in Syself? Contact us.