CVE-2024-57938: net/sctp: Prevent autoclose integer overflow in sctp_association_init()
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.
Security readout for executives and security teams
Plain-English summary
CVE-2024-57938 is a Linux kernel SCTP flaw where an unusually large autoclose setting can trigger integer overflow. The rated impact is denial of service, not data theft or privilege escalation. It needs local access and low privileges, so urgency is higher for shared Linux hosts than isolated single-user systems.
Executive priority
Treat as a scheduled but real availability risk. It is not currently evidenced as exploited, but shared Linux infrastructure should receive timely kernel maintenance because the worst documented impact is service disruption.
Technical view
The issue is CWE-190 in sctp_association_init(). If net.sctp.max_autoclose is set as high as UINT_MAX, SCTP autoclose handling can overflow. CVSS 3.1 is 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. Kernel stable commits and Debian LTS advisories are cited as remediation references.
Likely exposure
Exposure is likely on Linux systems running affected kernels where SCTP is available and local users can influence relevant SCTP behavior. Prioritize multi-user servers, container hosts, and systems using SCTP. The provided sources do not identify remote-only exposure.
Exploitation context
No KEV listing or cited source in the bundle reports active exploitation. The CVSS vector indicates local, low-complexity exploitation requiring low privileges and no user interaction, with availability impact only.
Researcher notes
The affected-version data in the bundle is not fully self-explanatory and includes commit identifiers plus version entries. Validate against upstream stable commits and distribution package advisories before declaring a host vulnerable or fixed.
Mitigation direction
Apply kernel updates containing the referenced stable fixes.
Use distribution advisories, including Debian LTS notices, to map patched package versions.
Review whether SCTP is required on exposed or shared Linux systems.
Check vendor guidance before changing sysctl or kernel-module policy.
Prioritize updates on multi-user and container-host Linux systems.
Validation and detection
Inventory Linux kernel versions across servers and images.
Compare installed kernels with vendor advisories and fixed stable commits.
Check whether SCTP is enabled or required in the environment.
Review net.sctp.max_autoclose configuration for unusual high values.
Confirm patched kernels are running after reboot or live patching.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-190 · source CWE mapping
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.