Linux Kernel up to 6.12.8 sctp sctp_association_init integer overflow

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 6.12.8. It has been classified as problematic. The affected element is the function sctp_association_init of the component sctp. The manipulation leads to integer overflow.
This vulnerability is documented as CVE-2024-57938. There is not any exploit available.
Upgrading the affected component is recommended.
Details
A vulnerability was found in Linux Kernel up to 6.12.8. It has been rated as problematic. This issue affects the function sctp_association_init of the component sctp. The manipulation with an unknown input leads to a integer overflow vulnerability. Using CWE to declare the problem leads to 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: net/sctp: Prevent autoclose integer overflow in sctp_association_init() While by default max_autoclose equals to INT_MAX / HZ, one may set net.sctp.max_autoclose to UINT_MAX. There is code in sctp_association_init() that can consequently trigger overflow.
The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2024-57938 since 01/19/2025. 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 02/17/2026).
The vulnerability scanner Nessus provides a plugin with the ID 216191 (SUSE SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2025:0428-1)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 5.4.289, 5.10.233, 5.15.176, 6.1.124, 6.6.70 or 6.12.9 eliminates this vulnerability. Applying the patch 94b7ed0a4896420988e1776942f0a3f67167873e/081bdb3a31674339313c6d702af922bc29de2c53/f9c3adb083d3278f065a83c3f667f1246c74c31f/7af63ef5fe4d480064eb22583b24ffc8b408183a/271f031f4c31c07e2a85a1ba2b4c8e734909a477/2297890b778b0e7c8200d6818154f7e461d78e94/4e86729d1ff329815a6e8a920cb554a1d4cb5b8d 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 (216191) and CERT Bund (WID-SEC-2025-0155). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- RESF Rocky Linux
- Dell NetWorker
- Dell Avamar
- Dell PowerProtect Data Domain
- Open Source Linux Kernel
- Dell Secure Connect Gateway
Product
Type
Vendor
Name
Version
- 5.4.288
- 5.10.232
- 5.15.175
- 6.1.123
- 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.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
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Integer overflowCWE: CWE-190 / CWE-189
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 216191
Nessus Name: SUSE SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2025:0428-1)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kernel 5.4.289/5.10.233/5.15.176/6.1.124/6.6.70/6.12.9
Patch: 94b7ed0a4896420988e1776942f0a3f67167873e/081bdb3a31674339313c6d702af922bc29de2c53/f9c3adb083d3278f065a83c3f667f1246c74c31f/7af63ef5fe4d480064eb22583b24ffc8b408183a/271f031f4c31c07e2a85a1ba2b4c8e734909a477/2297890b778b0e7c8200d6818154f7e461d78e94/4e86729d1ff329815a6e8a920cb554a1d4cb5b8d
Timeline
01/19/2025 🔍01/21/2025 🔍
01/21/2025 🔍
02/17/2026 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2024-57938 (🔍)
GCVE (CVE): GCVE-0-2024-57938
GCVE (VulDB): GCVE-100-292661
CERT Bund: WID-SEC-2025-0155 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service
Entry
Created: 01/21/2025 14:26Updated: 02/17/2026 05:49
Changes: 01/21/2025 14:26 (18), 01/21/2025 14:29 (40), 01/23/2025 09:11 (10), 02/13/2025 09:35 (2), 02/17/2026 05:49 (7)
Complete: 🔍
Committer: sany
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.