CVE-2026-45998 remediation guide

Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6

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) fo...

Open CVE record

ProductLinux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6

Affected versions>= 2d1faf7a0ca3c0b327cf064c80e4e775532c9319 < e3bf143b1e98fb3d6d9e6825bcd683974d478e8c, >= 2d1faf7a0ca3c0b327cf064c80e4e775532c9319 < bf20f46d94f1db38e6ffc0ca204a5fe0de01b495, >= 2d1faf7a0ca3c0b327cf064c80e4e775532c9319 < 996b0487b3cdda4c91811dbb1c9564626bc840bd, >= 2d1faf7a0ca3c0b327cf064c80e4e775532c9319 < 8fde6296c4d4da2be7ab761305ab7f232b94eefd, >= 2d1faf7a0ca3c0b327cf064c80e4e775532c9319 < 1f2740150f904bfa60e4bad74d65add3ccb5e7f8, >= 6.2, >= 6.2 < 6.6.140, >= 6.7 < 6.12.86, >= 6.13 < 6.18.27, >= 6.19 < 7.0.4

Fixed versions6.6.140, 6.12.86, 6.18.27, 7.0.4

Priority basisReview · CVSS 7.8 · EPSS 0.13%

Identify the affected asset

Confirm whether Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6 is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: >= 2d1faf7a0ca3c0b327cf064c80e4e775532c9319 < e3bf143b1e98fb3d6d9e6825bcd683974d478e8c, >= 2d1faf7a0ca3c0b327cf064c80e4e775532c9319 < bf20f46d94f1db38e6ffc0ca204a5fe0de01b495, >= 2d1faf7a0ca3c0b327cf064c80e4e775532c9319 < 996b0487b3cdda4c91811dbb1c9564626bc840bd, >= 2d1faf7a0ca3c0b327cf064c80e4e775532c9319 < 8fde6296c4d4da2be7ab761305ab7f232b94eefd, >= 2d1faf7a0ca3c0b327cf064c80e4e775532c9319 < 1f2740150f904bfa60e4bad74d65add3ccb5e7f8, >= 6.2, >= 6.2 < 6.6.140, >= 6.7 < 6.12.86, >= 6.13 < 6.18.27, >= 6.19 < 7.0.4. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 6.6.140, 6.12.86, 6.18.27, 7.0.4. Preserve configuration and rollback material before change.

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.