The vulnerability resides in the Linux kernel’s rxrpc subsystem, specifically within the rxgk_extract_token() function. When the underlying decryption routine fails with an out‑of‑memory error, the code previously continued execution and eventually caused an abort. This flaw allows the system to crash, leading to an unplanned reboot. The damage is limited to denial of service; confidentiality and integrity are not directly affected.

Linux kernel builds that include the rxrpc protocol prior to the commit fixing the error handling. No specific version ranges are listed in the advisory, so all releases before the patch are potentially impacted.

The risk stems from the ability of an attacker to trigger a kernel panic through crafted rxrpc traffic. While no EPSS score or KEV listing is provided, the severity is inherently high because a kernel crash can be catastrophic. The likely attack vector is remote, via maliciously constructed network packets that exploit the rxrpc interface. No public exploits are documented, but the lack of a mitigated default state means that unpatched systems remain vulnerable until an update is applied.