Linux Kernel up to 6.1.128/6.6.77/6.12.13/6.13.2 on 32-bit ksmbd ipc_msg_alloc integer overflow

Summaryinfo

A vulnerability has been found in Linux Kernel up to 6.1.128/6.6.77/6.12.13/6.13.2 on 32-bit and classified as problematic. This vulnerability affects the function ipc_msg_alloc of the component ksmbd. This manipulation causes integer overflow. This vulnerability is registered as CVE-2025-21748. No exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as problematic was found in Linux Kernel up to 6.1.128/6.6.77/6.12.13/6.13.2 on 32-bit. Affected by this vulnerability is the function ipc_msg_alloc of the component ksmbd. The manipulation with an unknown input leads to a integer overflow vulnerability. The CWE definition for the vulnerability is CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix integer overflows on 32 bit systems On 32bit systems the addition operations in ipc_msg_alloc() can potentially overflow leading to memory corruption. Add bounds checking using KSMBD_IPC_MAX_PAYLOAD to avoid overflow.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2025-21748 since 12/29/2024. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/25/2026).

The vulnerability scanner Nessus provides a plugin with the ID 230863 (Linux Distros Unpatched Vulnerability : CVE-2025-21748), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.1.129, 6.6.78, 6.12.14, 6.13.3 or 6.14-rc1 eliminates this vulnerability. Applying the patch 760568c1f62ea874e8fb492f9cfa4f47b4b8391e/82f59d64e6297f270311b16b5dcf65be406d1ea3/b4b902737746c490258de5cb55cab39e79927a67/ecb9947fa7c99a77b04d43404c6988a0d326e4a0/aab98e2dbd648510f8f51b83fbf4721206ccae45 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (230863) and CERT Bund (WID-SEC-2025-0453). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• Google Container-Optimized OS
• Debian Linux
• Amazon Linux 2
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• Oracle Linux
• Siemens SIMATIC S7
• RESF Rocky Linux
• Dell NetWorker
• Dell Avamar
• Red Hat OpenShift
• IBM QRadar SIEM
• SolarWinds Security Event Manager
• Dell PowerProtect Data Domain
• Open Source Linux Kernel
• IBM DataPower Gateway
• Dell Secure Connect Gateway
• Dell PowerScale OneFS
• Dell ECS

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 6.1.128
• 6.6.0
• 6.6.1
• 6.6.2
• 6.6.3
• 6.6.4
• 6.6.5
• 6.6.6
• 6.6.7
• 6.6.8
• 6.6.9
• 6.6.10
• 6.6.11
• 6.6.12
• 6.6.13
• 6.6.14
• 6.6.15
• 6.6.16
• 6.6.17
• 6.6.18
• 6.6.19
• 6.6.20
• 6.6.21
• 6.6.22
• 6.6.23
• 6.6.24
• 6.6.25
• 6.6.26
• 6.6.27
• 6.6.28
• 6.6.29
• 6.6.30
• 6.6.31
• 6.6.32
• 6.6.33
• 6.6.34
• 6.6.35
• 6.6.36
• 6.6.37
• 6.6.38
• 6.6.39
• 6.6.40
• 6.6.41
• 6.6.42
• 6.6.43
• 6.6.44
• 6.6.45
• 6.6.46
• 6.6.47
• 6.6.48
• 6.6.49
• 6.6.50
• 6.6.51
• 6.6.52
• 6.6.53
• 6.6.54
• 6.6.55
• 6.6.56
• 6.6.57
• 6.6.58
• 6.6.59
• 6.6.60
• 6.6.61
• 6.6.62
• 6.6.63
• 6.6.64
• 6.6.65
• 6.6.66
• 6.6.67
• 6.6.68
• 6.6.69
• 6.6.70
• 6.6.71
• 6.6.72
• 6.6.73
• 6.6.74
• 6.6.75
• 6.6.76
• 6.6.77
• 6.12.0
• 6.12.1
• 6.12.2
• 6.12.3
• 6.12.4
• 6.12.5
• 6.12.6
• 6.12.7
• 6.12.8
• 6.12.9
• 6.12.10
• 6.12.11
• 6.12.12
• 6.12.13
• 6.13.0
• 6.13.1
• 6.13.2

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion