Answer in brief
CVE-2026-45998 records a High severity (CVSS 7.8) vulnerability in rxrpc: Fix potential UAF after skb_unshare() failure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-45998 records a High severity (CVSS 7.8) vulnerability in rxrpc: Fix potential UAF after skb_unshare() failure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2d1faf7a0ca3c0b327cf064c80e4e775532c9319 <e3bf143b1e98fb3d6d9e6825bcd683974d478e8c || >=2d1faf7a0ca3c0b327cf064c80e4e775532c9319 <bf20f46d94f1db38e6ffc0ca204a5fe0de01b495 || >=2d1faf7a0ca3c0b327cf064c80e4e775532c9319 <996b0487b3cdda4c91811dbb1c9564626bc840bd || >=2d1faf7a0ca3c0b327cf064c80e4e775532c9319 <8fde6296c4d4da2be7ab761305ab7f232b94eefd || >=2d1faf7a0ca3c0b327cf064c80e4e775532c9319 <1f2740150f904bfa60e4bad74d65add3ccb5e7f8 | e3bf143b1e98fb3d6d9e6825bcd683974d478e8c, bf20f46d94f1db38e6ffc0ca204a5fe0de01b495, 996b0487b3cdda4c91811dbb1c9564626bc840bd, 8fde6296c4d4da2be7ab761305ab7f232b94eefd, 1f2740150f904bfa60e4bad74d65add3ccb5e7f8 |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 3, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2d1faf7a0ca3c0b327cf064c80e4e775532c9319 <e3bf143b1e98fb3d6d9e6825bcd683974d478e8c || >=2d1faf7a0ca3c0b327cf064c80e4e775532c9319 <bf20f46d94f1db38e6ffc0ca204a5fe0de01b495 || >=2d1faf7a0ca3c0b327cf064c80e4e775532c9319 <996b0487b3cdda4c91811dbb1c9564626bc840bd || >=2d1faf7a0ca3c0b327cf064c80e4e775532c9319 <8fde6296c4d4da2be7ab761305ab7f232b94eefd || >=2d1faf7a0ca3c0b327cf064c80e4e775532c9319 <1f2740150f904bfa60e4bad74d65add3ccb5e7f8 | e3bf143b1e98fb3d6d9e6825bcd683974d478e8c, bf20f46d94f1db38e6ffc0ca204a5fe0de01b495, 996b0487b3cdda4c91811dbb1c9564626bc840bd, 8fde6296c4d4da2be7ab761305ab7f232b94eefd, 1f2740150f904bfa60e4bad74d65add3ccb5e7f8 |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 3, 2026
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.
Quoted source text, attributed separately from HOL analysis.