Description
In the Linux kernel, the following vulnerability has been resolved: rxrpc: rxrpc_verify_data ensure rx_dec_buffer alloc rxrpc_recvmsg_data() calls rxrpc_verify_data() whenever the rxrpc_call.rx_dec_buffer is unallocated and assumes that upon successful return that rx_dec_buffer must be allocated. However, rxrpc_verify_data() does not request an allocation if the rxrpc_skb_priv.len is zero. In addition, failure to allocate rx_dec_buffer will result in a call to skb_copy_bits() with a NULL destination which can trigger a NULL pointer dereference. To prevent these issues rxrpc_verify_data() is modified to always attempt to allocate the rxrpc_call.rx_dec_buffer if it is NULL. This issue was identified with assistance of a private sashiko instance.
References5
- git.kernel.org/stable/c/16c8ae9735c5bd7e54dd7478d6348e0fc860842d
- git.kernel.org/stable/c/6563b4eb38c35d75892445bcf8aacdc29914821c
- git.kernel.org/stable/c/8bbede0afced346b24e4fbde0c68cf12980ba948
- git.kernel.org/stable/c/a962bc8508592c4d51092edac68579bd8b18fe44
- git.kernel.org/stable/c/d3b642cf95d48234590cc91450d8705a9bf6b540
Metrics
- CVSS 3.1
-
7.5
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 1% percentile: 51 · as of 11 November 2026
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.