Technical impact
A use‑after‑free flaw exists in the TCP stack’s getsockopt handler for congestion‑control information. The handler accesses a function pointer in the socket’s congestion‑control operations without holding an RCU read lock, allowing concurrent freeing of that memory and resulting in a stale pointer dereference. This kernel memory corruption can enable an attacker to execute arbitrary code at ring‑0, effectively allowing privilege escalation on the affected system.
Affected Systems
This vulnerability affects all Linux kernel releases that contain the unpatched TCP get_sockopt path. The exact version range is not specified in the advisory, but any kernel lacking the recent patch for TCP_CC_INFO is potentially vulnerable. The issue applies to generic Linux distributions and free‑software kernels that include the standard TCP implementation.
Risk and Exploitability
Based on the description, the vulnerability requires a scenario where a BPF program defines a congestion‑control struct_ops that points to dynamically allocated memory. If an attacker can load such a program locally, the kernel may dereference a freed pointer when processing a getsockopt request for TCP_CC_INFO. The EPSS score of less than 1% indicates low probability of exploitation, and the vulnerability is not listed in the CISA KEV catalog, suggesting no known widespread exploitation. However, the CVSS score of 7.0 reflects a high severity, giving an attacker the potential to achieve privilege escalation on a vulnerable system if the flaw is successfully triggered.
Debian DLA