SECUFOCUSNOW
Home›Remediation guides›CVE-2026-43284
CVE REMEDIATION GUIDE
Priority reviewHighFixed-version data available

CVE-2026-43284 remediation guide

Linux Linux, NVIDIA for RHEL 10, Red Hat Enterprise Linux 10

In the Linux kernel, the following vulnerability has been resolved: xfrm: esp: avoid in-place decrypt on shared skb frags MSG_SPLICE_PAGES can attach pages from a pipe directly to an skb. TCP marks such skbs with SKBFL_SHARED_FRAG after skb_splice_from_iter(), so later paths that may modify packet data can first make a private copy. The IPv4/IPv6 datagram append paths did not set this flag when splicing pages into UDP skbs. That leaves an ESP-in-UDP packet made from shared pipe pages looking like an ordinary uncloned nonlinear skb. ESP input then takes the no-COW fast path for uncloned skbs...

Open CVE record
ProductLinux Linux, NVIDIA for RHEL 10, Red Hat Enterprise Linux 10
Affected versions>= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < a6cb440f274a22456ef3e86b457344f1678f38f9, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < ab8b995323e5237041472d07e5055f5f7dcdf15b, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < fe785bb3a8096dffcc4048a85cd0c83337eeecad, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 5d55c7336f8032d434adcc5fab987ccc93a44aec, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 8253aab4659ca16116b522203c2a6b18dccacea7, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 50ed1e7873100f77abad20fd31c51029bc49cd03, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < b54edf1e9a3fd3491bdcb82a21f8d21315271e0d, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 71a1d9d985d26716f74d21f18ee8cac821b06e97, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 52646cbd00e765a6db9c3afe9535f26218276034, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < f4c50a4034e62ab75f1d5cdd191dd5f9c77fdff4, >= 4.11, >= V3.1.6, >= V3.1.5, >= 4.11 < 5.10.255, >= 5.12 < 5.15.205, >= 5.16 < 6.1.171, >= 6.2 < 6.6.138, >= 6.7 < 6.12.87, >= 6.13 < 6.18.28, >= 7.0 < 7.0.5
Fixed versions5.10.255, 5.15.205, 6.1.171, 6.6.138, 6.12.87, 6.18.28, 7.0.5
Priority basisPriority · CVSS 8.8 · EPSS 93.2%
01

Identify the affected asset

Confirm whether Linux Linux, NVIDIA for RHEL 10, Red Hat Enterprise Linux 10 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.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < a6cb440f274a22456ef3e86b457344f1678f38f9, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < ab8b995323e5237041472d07e5055f5f7dcdf15b, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < fe785bb3a8096dffcc4048a85cd0c83337eeecad, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 5d55c7336f8032d434adcc5fab987ccc93a44aec, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 8253aab4659ca16116b522203c2a6b18dccacea7, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 50ed1e7873100f77abad20fd31c51029bc49cd03, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < b54edf1e9a3fd3491bdcb82a21f8d21315271e0d, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 71a1d9d985d26716f74d21f18ee8cac821b06e97, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 52646cbd00e765a6db9c3afe9535f26218276034, >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < f4c50a4034e62ab75f1d5cdd191dd5f9c77fdff4, >= 4.11, >= V3.1.6, >= V3.1.5, >= 4.11 < 5.10.255, >= 5.12 < 5.15.205, >= 5.16 < 6.1.171, >= 6.2 < 6.6.138, >= 6.7 < 6.12.87, >= 6.13 < 6.18.28, >= 7.0 < 7.0.5. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

FIRST EPSS indicates an elevated probability of exploitation. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 5.10.255, 5.15.205, 6.1.171, 6.6.138, 6.12.87, 6.18.28, 7.0.5. Preserve configuration and rollback material before change.

05

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.