Review reviewHigh

CVE-2026-53389

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: net/tcp-ao: fix use-after-free of key in del_async path In tcp_ao_delete_key(), the del_async path skips the current_key and rnext_key validity checks present in the synchronous path, assuming these pointers are always NULL on LISTEN sockets. However, if a key was added with set_current=1/set_rnext=1 while the socket was in CLOSE state, current_key and rnext_key will be non-NULL after listen() transitions the socket to LISTEN. When such a key is deleted with del_async=1, hlist_del_rcu() and call_rcu() free the key without c...

CVSS
7.8
EPSS
0.13%
2.60% percentile
CISA KEV
Not listed
Published
2026.07.19
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.13%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: net/tcp-ao: fix use-after-free of key in del_async path In tcp_ao_delete_key(), the del_async path skips the current_key and rnext_key validity checks present in the synchronous path, assuming these pointers are always NULL on LISTEN sockets. However, if a key was added with set_current=1/set_rnext=1 while the socket was in CLOSE state, current_key and rnext_key will be non-NULL after listen() transitions the socket to LISTEN. When such a key is deleted with del_async=1, hlist_del_rcu() and call_rcu() free the key without c...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= d6732b95b6fbbc6d5bb9d2f809e275763640c4a2 < 6ce7ef41743740ce15c2061561b784148b565b3f, >= d6732b95b6fbbc6d5bb9d2f809e275763640c4a2 < e77fbefd1269b5c123e7c651a1ebdce1b87d19a0, >= d6732b95b6fbbc6d5bb9d2f809e275763640c4a2 < 7ddc29a094d96e9b3aa280433c6dc443df9eabf2, >= d6732b95b6fbbc6d5bb9d2f809e275763640c4a2 < 5ba9950bc9078e19b69cca1e56d1553b125c6857, >= 6.7, >= 6.7 < 6.12.95, >= 6.13 < 6.18.38, >= 6.19 < 7.1.3
Fixed versions
6.12.95, 6.18.38, 7.1.3

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416