CVE-2026-45998

rxrpc: Fix potential UAF after skb_unshare() failure

Published May 27, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability arises when skb_unshare() fails to unshare a packet due to an allocation failure in rxrpc_input_packet(). The skb pointer in the parent rxrpc_io_thread() is then set to NULL, causing trace_rxrpc_rx_done() to dereference a NULL pointer and trigger a kernel oops. The flaw, identified as CWE-416 and CWE-825, can lead to a kernel crash and a denial of service. Based on the description, the attack vector is inferred to involve the transmission of malicious RXRPC packets that trigger the allocation failure and null dereference.

Affected Systems

All Linux kernel builds that include the RXRPC networking stack and have not yet incorporated the fix commit (c/1f2740150f904bfa60e4bad74d65add3ccb5e7f8) are potentially affected. The patch was applied to the mainline kernel, so any system shipping a kernel version prior to that commit is at risk. Since specific version ranges are not listed, administrators should consult the kernel changelog or release notes to determine whether their kernel includes the referenced improvements.

Risk and Exploitability

The CVSS score of 7.8 indicates high severity for this kernel flaw. The EPSS score of < 1% indicates a very low exploitation probability, and the vulnerability is not listed in CISA's KEV catalog, suggesting no known active exploitation at the time of the advisory. Exploitation would require an attacker to send RXRPC traffic that induces an allocation failure, a scenario that might be difficult to reliably reproduce in a stable production environment. Nonetheless, a successful exploit would result in a non‑privileged kernel crash, disrupting availability and potentially allowing privilege escalation if the crash is leveraged in a broader attack chain.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a Linux kernel version that includes the rxrpc UAF bug fix (commit c/1f2740150f904bfa60e4bad74d65add3ccb5e7f8 or later).
  • If upgrading is not immediately feasible, block inbound RXRPC traffic on affected nodes using firewall rules to prevent triggering the bug.
  • As a last resort, apply the specific commit manually to your kernel source tree, rebuild, and reboot to deploy the fix.

Generated by OpenCVE AI on June 17, 2026 at 23:47 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8370-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8371-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8373-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8374-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8440-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8489-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8497-1 Linux kernel (Low Latency) vulnerabilities
Ubuntu USN Ubuntu USN USN-8499-1 Linux kernel (Xilinx) vulnerabilities
Ubuntu USN Ubuntu USN USN-8569-1 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-8393-1 Linux kernel (Azure FIPS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8461-1 Linux kernel (Azure) vulnerabilities
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-416
Metrics cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Weaknesses CWE-825
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Important

Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Description 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.
Title rxrpc: Fix potential UAF after skb_unshare() failure
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Nov 6, 2026, 4:13 PM
Reserved
May 13, 2026, 3:03 PM
Status
Modified
Published
May 27, 2026, 2:17 PM
Modified
Nov 6, 2026, 5:17 PM
Severity
Important
Public date
May 27, 2026, 12:00 AM