rxrpc: Fix potential UAF after skb_unshare() failure
21Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 7epss 0.1%
probabilidad de explotación
0.1%top 97% de las CVE
explotación observada
noninguna fuente lo reporta
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix potential UAF after skb_unshare() failure
If skb_unshare() fails to unshare a packet due to allocation failure in
rxrpc_input_packet(), the skb pointer in the parent (rxrpc_io_thread())
will be NULL'd out. This will likely cause the call to
trace_rxrpc_rx_done() to oops.
Fix this by moving the unsharing down to where rxrpc_input_call_event()
calls rxrpc_input_call_packet(). There are a number of places prior to
that where we ignore DATA packets for a variety of reasons (such as the
call already being complete) for which an unshare is then avoided.
And with that, rxrpc_input_packet() doesn't need to take a pointer to the
pointer to the packet, so change that to just a pointer.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Productos afectados
Linux · LinuxReferencias
https://access.redhat.com/errata/RHSA-2026:34911https://access.redhat.com/security/cve/CVE-2026-45998https://bugzilla.redhat.com/show_bug.cgi?id=2482024https://git.kernel.org/stable/c/1f2740150f904bfa60e4bad74d65add3ccb5e7f8https://git.kernel.org/stable/c/8fde6296c4d4da2be7ab761305ab7f232b94eefdhttps://git.kernel.org/stable/c/996b0487b3cdda4c91811dbb1c9564626bc840bdhttps://git.kernel.org/stable/c/bf20f46d94f1db38e6ffc0ca204a5fe0de01b495https://git.kernel.org/stable/c/e3bf143b1e98fb3d6d9e6825bcd683974d478e8chttps://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-45998.json