Incorrect Conversion between Numeric Types Affecting kernel-debuginfo-common-ppc64le package, versions <0:6.12.0-55.33.1.el10_0


Severity

Recommended
medium

Based on CentOS security rating.

Threat Intelligence

EPSS
0.03% (6th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CENTOS10-KERNELDEBUGINFOCOMMONPPC64LE-12675454
  • published16 Sept 2025
  • disclosed25 Jul 2025

Introduced: 25 Jul 2025

CVE-2025-38463  (opens in a new tab)
CWE-681  (opens in a new tab)

How to fix?

Upgrade Centos:10 kernel-debuginfo-common-ppc64le to version 0:6.12.0-55.33.1.el10_0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-debuginfo-common-ppc64le package and not the kernel-debuginfo-common-ppc64le package as distributed by Centos. See How to fix? for Centos:10 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1