Talos vulnerable dependency due to race condition in Linux kernel's IP framework XFRM

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.0 · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact A race condition was found in the Linux kernel's IP framework for transforming packets (XFRM subsystem) when multiple calls to xfrmprobealgs occurred simultaneously. This flaw could allow a local attacker to potentially trigger an out-of-bounds write or leak kernel heap memory by performing an out-of-bounds read and copying it into a socket. Patches The fix has been backported to 5.15.64 version of the upstream Linux kernel (5.15 is the upstream Kernel long term version Talos ships with). Talos = v1.2.0 is shipped with Linux Kernel 5.15.64 fixing the above issue. Kubernetes workloads running in Talos are not affected since user namespaces are disabled in Talos kernel config. So an unprivileged user cannot obtain CAPNETADMIN by unsharing. However untrusted workloads that run with privileged: true or having NETADMIN capability poses a risk. Workarounds Audit kubernetes workloads running in the cluster with privileged: true set or having NETADMIN capability and assess the threat…

Published by the source

16 Sep 2022, 17:17 UTC

Last modified by the source

11 Jan 2023, 05:07 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-34vw-m4rh-r36p

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-34vw-m4rh-r36p

Advisory: Talos vulnerable dependency due to race condition in Linux kernel's IP framework XFRM
IDs: GHSA-34vw-m4rh-r36p
Record: https://patchnext.com/advisories/ghsa-34vw-m4rh-r36p (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/talos-systems/talos 1.2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/talos-systems/talos: affected < 1.2.0; fixed in 1.2.0

## Suggested inspection (read-only)
- Go github.com/talos-systems/talos: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/talos-systems/talos.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-34vw-m4rh-r36p (GitHub-reviewed advisory GHSA-34vw-m4rh-r36p lists affected ranges: Go github.com/talos-systems/talos >=0 <1.2.0)

Commands are suggestions: review each one before running it.