CVE-2026-43038 remediation guide

Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support

In the Linux kernel, the following vulnerability has been resolved: ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach() Sashiko AI-review observed: In ip6_err_gen_icmpv6_unreach(), the skb is an outer IPv4 ICMP error packet where its cb contains an IPv4 inet_skb_parm. When skb is cloned into skb2 and passed to icmp6_send(), it uses IP6CB(skb2). IP6CB interprets the IPv4 inet_skb_parm as an inet6_skb_parm. The cipso offset in inet_skb_parm.opt directly overlaps with dsthao in inet6_skb_parm at offset 18. If an attacker sends a forged ICMPv4 error with a CIPSO IP option, dsthao would...

Open CVE record

ProductLinux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support

Affected versions>= ca15a078bd907df5fc1c009477869c5cbde3b753 < c438ba010171b70bad22fc18b1d5bdc3627476e8, >= ca15a078bd907df5fc1c009477869c5cbde3b753 < 0452b6526b2f54b2413b9cb4ff1ea2ac542c99c7, >= ca15a078bd907df5fc1c009477869c5cbde3b753 < a4437faf135da293d16fcc4cc607316742bd0ebb, >= ca15a078bd907df5fc1c009477869c5cbde3b753 < 3d5127d998de617b130aae96b138dba22ac6a8a7, >= ca15a078bd907df5fc1c009477869c5cbde3b753 < e41953e7d118e2702bcb217879c173d9d1d3cd4e, >= ca15a078bd907df5fc1c009477869c5cbde3b753 < a2edbb6393972a02114b6003953a5cef3104fada, >= ca15a078bd907df5fc1c009477869c5cbde3b753 < 1ceeebd5bd6d855b17a5df625109bfe29129d7cf, >= ca15a078bd907df5fc1c009477869c5cbde3b753 < 86ab3e55673a7a49a841838776f1ab18d23a67b5, >= 3.13, >= V3.1.6, >= V3.1.5, > 3.13 < 5.10.253, >= 5.11 < 5.15.203, >= 5.16 < 6.1.168, >= 6.2 < 6.6.134, >= 6.7 < 6.12.81, >= 6.13 < 6.18.22, >= 6.19 < 6.19.12, 3.13, 7.0

Fixed versions5.10.253, 5.15.203, 6.1.168, 6.6.134, 6.12.81, 6.18.22, 6.19.12

Priority basisReview · CVSS 9.8 · EPSS 0.26%

Identify the affected asset

Confirm whether Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support 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: >= ca15a078bd907df5fc1c009477869c5cbde3b753 < c438ba010171b70bad22fc18b1d5bdc3627476e8, >= ca15a078bd907df5fc1c009477869c5cbde3b753 < 0452b6526b2f54b2413b9cb4ff1ea2ac542c99c7, >= ca15a078bd907df5fc1c009477869c5cbde3b753 < a4437faf135da293d16fcc4cc607316742bd0ebb, >= ca15a078bd907df5fc1c009477869c5cbde3b753 < 3d5127d998de617b130aae96b138dba22ac6a8a7, >= ca15a078bd907df5fc1c009477869c5cbde3b753 < e41953e7d118e2702bcb217879c173d9d1d3cd4e, >= ca15a078bd907df5fc1c009477869c5cbde3b753 < a2edbb6393972a02114b6003953a5cef3104fada, >= ca15a078bd907df5fc1c009477869c5cbde3b753 < 1ceeebd5bd6d855b17a5df625109bfe29129d7cf, >= ca15a078bd907df5fc1c009477869c5cbde3b753 < 86ab3e55673a7a49a841838776f1ab18d23a67b5, >= 3.13, >= V3.1.6, >= V3.1.5, > 3.13 < 5.10.253, >= 5.11 < 5.15.203, >= 5.16 < 6.1.168, >= 6.2 < 6.6.134, >= 6.7 < 6.12.81, >= 6.13 < 6.18.22, >= 6.19 < 6.19.12, 3.13, 7.0. 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: 5.10.253, 5.15.203, 6.1.168, 6.6.134, 6.12.81, 6.18.22, 6.19.12. 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.