Technical impact
Linux kernel contains a flaw in the pipe fasync handling code where a failure to allocate resources for a writer incorrectly removes an existing reader registration, leaving a stale reference. The fault triggers a use‑after‑free in the send_sigio() routine, leading to kernel memory corruption. The description indicates that an unprivileged user could cause this issue via a memory‑pressure condition but does not explicitly state that privilege escalation or code execution is possible.
Affected Systems
Affected systems are Linux kernel installations that do not include the patch introduced in commit 2259809e5b7043c4ba20af7b14ba3e471cf55521. The specific kernel versions are not enumerated in the available data, but any kernel revision prior to the application of that commit is vulnerable. Operators should check kernel sources or build logs for the presence of the mentioned commit hash to determine exposure.
Risk and Exploitability
The vulnerability is a classic use‑after‑free that can be exploited locally by an unprivileged user. The bug is triggered through normal pipe operations and the kernel’s async notification mechanism, requiring no network access or elevated privileges to initiate. The EPSS score of < 1% indicates a very low probability of exploitation, and the vulnerability is not listed in KEV. The risk assessment therefore relies on the KASAN evidence of kernel memory corruption and the CVSS score of 7.8. While the description does not confirm privilege escalation or code execution, the kernel memory corruption could potentially lead to security impact depending on surrounding code paths.
Debian DLA