In the Linux kernel, the rxrpc protocol had a flaw where a packet with a misaligned crypto length was not handled safely, leading to a potential decryption failure or abort. The patch adds bounds checking, aborts on non‑ENOMEM decryption errors, and removes the WARN_ON_ONCE guard so that it cannot be repeatedly triggered, though a trace line may still be emitted. The primary effect of the vulnerability is a crash or denial of service of the affected component, not arbitrary code execution.

All Linux kernel implementations that include the rxrpc protocol before the patch that fixes the crypto alignment handling are affected. No specific kernel versions are listed, so any deployment running a pre‑patch Linux kernel with rxrpc support is vulnerable.

Based on the description, it is inferred that the attack requires a remote attacker capable of sending crafted rxrpc packets to a target that accepts such traffic. The EPSS score is not available and the vulnerability is not listed in KEV, indicating no widespread exploitation reports. The risk is primarily a DoS scenario; an attacker can trigger a service crash with a single malformed packet. The severity of the vulnerability is reflected in a high CVSS score, but the lack of public exploitation reduces immediate urgency. The removal of the WARN_ON_ONCE guard lowers the chance of repeated trivial exploitation, yet the possibility of a single attack remains.