UBUNTU-CVE-2026-98229: High severity ubuntu/linux-aws vulnerability
In the Linux kernel, the following vulnerability has been resolved: xfrm: save input state data before secpath resets xfrminput() stores the current xfrmstate in the skb secpath while it continues receive-side processing. Some input paths can reset that secpath before xfrminput() has finished dereferencing the state. Receive callback users such as VTI and XFRM interfaces can reset the secpath. The VTI receive path does so before checking whether the packet crosses network namespaces, while the XFRM interface path does so only for cross-network-namespace packets. The XFRMMAXDEPTH error path can also reset the secpath before the final drop callback reports the current state's protocol. If secpathreset() drops the last state reference while the state is concurrently deleted, xfrminput() can still dereference the freed state when selecting transportfinish() or reporting the drop callback protocol. Save the state protocol on the stack while the state is still valid, and use the already saved address family for transportfinish(). A larval XFRMSTATEACQ state has no type, so retain nexthdr as its protocol. This preserves the existing drop-path fallback while avoiding the post-reset state dereferences without adding an extra state reference to every received packet.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
The affected software list includes Ubuntu linux, linux-aws, linux-azure, linux-gcp, and their listed FIPS variants. Exposure is tied to Linux kernel XFRM receive-side processing, including VTI and XFRM interface receive callback paths.
What conditions are needed to trigger the vulnerability?
The issue requires a secpath reset while xfrm_input() still uses the current XFRM state, combined with concurrent deletion of that state. Documented triggering paths include VTI receive processing, cross-network-namespace traffic through XFRM interfaces, and the XFRM_MAX_DEPTH error path.
What is the likely impact if exploitation succeeds?
xfrm_input() may dereference a freed XFRM state while selecting transport_finish() or reporting the protocol to a drop callback. The supplied vector rates impacts to confidentiality, integrity, and availability as high.