CVE-2025-38463 tcp: Correct signedness in skb remaining space calculation

High 7.8 Published Updated

A signedness error in Linux kernel TCP code allows integer overflow, potentially leading to denial of service.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2025-38463?

CVE-2025-38463 is a high-severity vulnerability in Linux kernel, published on 25 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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

tcp: Correct signedness in skb remaining space calculation

Syzkaller reported a bug [1] where sk->sk_forward_alloc can overflow.

When we send data, if an skb exists at the tail of the write queue, the kernel will attempt to append the new data to that skb. However, the code that checks for available space in the skb is flawed: ''' copy = size_goal - skb->len '''

The types of the variables involved are: ''' copy: ssize_t (s64 on 64-bit systems) size_goal: int skb->len: unsigned int '''

Due to C's type promotion rules, the signed size_goal is converted to an unsigned int to match skb->len before the subtraction. The result is an unsigned int.

When this unsigned int result is then assigned to the s64 copy variable, it is zero-extended, preserving its non-negative value. Consequently, copy is always >= 0.

Assume we are sending 2GB of data and size_goal has been adjusted to a value smaller than skb->len. The subtraction will result in copy holding a very large positive integer. In the subsequent logic, this large value is used to update sk->sk_forward_alloc, which can easily cause it to overflow.

The syzkaller reproducer uses TCP_REPAIR to reliably create this condition. However, this can also occur in real-world scenarios. The tcp_bound_to_half_wnd() function can also reduce size_goal to a small value. This would cause the subsequent tcp_wmem_schedule() to set sk->sk_forward_alloc to a value close to INT_MAX. Further memory allocation requests would then cause sk_forward_alloc to wrap around and become negative.

[1]: https://syzkaller.appspot.com/bug?extid=de6565462ab540f50e47

Weakness: CWE-191

Which versions are affected by CVE-2025-38463?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2025-38463?

Apply the vendor's patch.

Is CVE-2025-38463 being exploited?

There is no known exploitation of CVE-2025-38463 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as AZL-65774, BELL-CVE-2025-38463, DEBIAN-CVE-2025-38463, GHSA-7fhq-j7h5-cjxg, ROOT-OS-UBUNTU-2404-CVE-2025-38463, UBUNTU-CVE-2025-38463.

Is CVE-2025-38463 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free