Skip to main content

Syself security assessment

CVE-2026-98155 in Syself Kubernetes

In the Linux kernel, the following vulnerability has been resolved: accel/qaic: Address potential out-of-bounds read in resp_worker() Although 'commit 2feec5ae5df7 ("accel/qaic: Handle DBC deactivation if the owner went away")' fixes the scenario it was intended for by walking the message and only decoding QAIC_TRANS_DEACTIVATE_FROM_DEV, if present, it skipped over the bounds checking code that is included in decode_message(). This could lead to issues such as reading past the slab allocation's end, infinite loops or kernel panics. For those issues to happen, a malformed wire message is needed to be sent from the device. Instead of duplicating the bounds checking code already present in decode_message(), use the function inside resp_worker().

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-98155 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 v6 Upstream severity: High Last assessed

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

Reason: The vulnerable code is never executed.

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

kernel 6.18.49
Not affected High
The vulnerable code is never executed

The flaw is an out-of-bounds read in a driver for a Qualcomm cloud AI accelerator card. No such card is present on the nodes, so the driver never loads and the affected code is never executed.

Syself Security

Status by release

ReleasesComponentStatusReasonFixed inAssessment
kernel 6.18.42, 6.18.45, 6.18.49Not affectedThe vulnerable code is never executed—Details

Frequently asked questions

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

Scanners such as Trivy and Grype match package versions, so they report CVE-2026-98155 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-v6-advisory.openvex.json <image>
grype <image> --vex hetzner-apalla-1-36-v6-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 v6

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.