CVE Catalog

CVE-2026-80843

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel's xfrm_state_construct() function, there is a memory leak related to the authentication algorithm. The attach_auth_trunc() function can allocate memory for x->aalg but does not set x->props.aalgo when the selected algorithm has no sadb_alg_id (e.g., cmac(aes)). Then xfrm_state_construct() treats the zero value of x->props.aalgo as no algorithm and calls attach_auth(), which overwrites the x->aalg pointer and loses the original allocation. The fix checks whether x->aalg is already attached instead of inferring from x->props.aalgo.

Risk Assessment

The memory leak can lead to gradual exhaustion of system resources, potentially causing system or service crashes in the long run.

Recommendation

Apply the Linux kernel update containing the fix for this memory leak. Monitor memory usage on systems with heavy IPsec operations.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: xfrm: fix xfrm_state_construct() auth-trunc leak attach_auth_trunc() can allocate x->aalg while leaving x->props.aalgo at zero when the selected auth algorithm has no sadb_alg_id. One real case is cmac(aes). xfrm_state_construct() then treats !x->props.aalgo as "no auth algorithm attached yet" and calls attach_auth(). That overwrites x->aalg and loses the first allocation. Any later failure or teardown only frees the replacement pointer. Check whether x->aalg is already attached instead of inferring that state from x->props.aalgo.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS