🛡️ AZL-74664 — kernel

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

CVE-2025-39770 affecting package kernel 5.15.200.1-1

In the Linux kernel, the following vulnerability has been resolved:

net: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM

When performing Generic Segmentation Offload (GSO) on an IPv6 packet that

contains extension headers, the kernel incorrectly requests checksum offload

if the egress device only advertises NETIF_F_IPV6_CSUM feature, which has

a strict contract: it supports checksum offload only for plain TCP or UDP

over IPv6 and explicitly does not support packets with extension headers.

The current GSO logic violates this contract by failing to disable the feature

for packets with extension headers, such as those used in GREoIPv6 tunnels.

This violation results in the device being asked to perform an operation

it cannot support, leading to a skb_warn_bad_offload warning and a collapse

of network throughput. While device TSO/USO is correctly bypassed in favor

of software GSO for these packets, the GSO stack must be explicitly told not

to request checksum offload.

Mask NETIF_F_IPV6_CSUM, NETIF_F_TSO6 and NETIF_F_GSO_UDP_L4

in gso_features_check if the IPv6 header contains extension headers to compute

checksum in software.

The exception is a BIG TCP extension, which, as stated in commit

68e068cabd2c6c53 ("net: reenable NETIF_F_IPV6_CSUM offload for BIG TCP packets"):

"The feature is only enabled on devices that support BIG TCP TSO.

The header is only present for PF_PACKET taps like tcpdump,

and not transmitted by physical devices."

kernel log output (truncated):

WARNING: CPU: 1 PID: 5273 at net/core/dev.c:3535 skb_warn_bad_offload+0x81/0x140

...

Call Trace:

<TASK>

skb_checksum_help+0x12a/0x1f0

validate_xmit_skb+0x1a3/0x2d0

validate_xmit_skb_list+0x4f/0x80

sch_direct_xmit+0x1a2/0x380

__dev_xmit_skb+0x242/0x670

__dev_queue_xmit+0x3fc/0x7f0

ip6_finish_output2+0x25e/0x5d0

ip6_finish_output+0x1fc/0x3f0

ip6_tnl_xmit+0x608/0xc00 [ip6_tunnel]

ip6gre_tunnel_xmit+0x1c0/0x390 [ip6_gre]

dev_hard_start_xmit+0x63/0x1c0

__dev_queue_xmit+0x6d0/0x7f0

ip6_finish_output2+0x214/0x5d0

ip6_finish_output+0x1fc/0x3f0

ip6_xmit+0x2ca/0x6f0

ip6_finish_output+0x1fc/0x3f0

ip6_xmit+0x2ca/0x6f0

inet6_csk_xmit+0xeb/0x150

__tcp_transmit_skb+0x555/0xa80

tcp_write_xmit+0x32a/0xe90

tcp_sendmsg_locked+0x437/0x1110

tcp_sendmsg+0x2f/0x50

...

skb linear: 00000000: e4 3d 1a 7d ec 30 e4 3d 1a 7e 5d 90 86 dd 60 0e

skb linear: 00000010: 00 0a 1b 34 3c 40 20 11 00 00 00 00 00 00 00 00

skb linear: 00000020: 00 00 00 00 00 12 20 11 00 00 00 00 00 00 00 00

skb linear: 00000030: 00 00 00 00 00 11 2f 00 04 01 04 01 01 00 00 00

skb linear: 00000040: 86 dd 60 0e 00 0a 1b 00 06 40 20 23 00 00 00 00

skb linear: 00000050: 00 00 00 00 00 00 00 00 00 12 20 23 00 00 00 00

skb linear: 00000060: 00 00 00 00 00 00 00 00 00 11 bf 96 14 51 13 f9

skb linear: 00000070: ae 27 a0 a8 2b e3 80 18 00 40 5b 6f 00 00 01 01

skb linear: 00000080: 08 0a 42 d4 50 d5 4b 70 f8 1a

Affected software

AZL-74664 is recorded against 1 package.

  • kernel

Timeline and source

Published on 11 September 2025 and last revised on 21 April 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

nvd.nist.gov (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2025-09-11
Updated 2026-08-12
Modified 2026-04-21
Fix URL N/A

Affected Packages

Software From version Fixed in
kernel

Similar Threats

Free Vulnerability Check

Is your site affected by AZL-74664?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against AZL-74664 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.