LiveActive security incident?Get immediate response
CVE Record

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.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

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.
Prepared
Confidence
medium
Sources
11

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-57938 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2024-57938Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9f70f46bd4c7267d48ef461a1d613ec9ec0d520c, 9f70f46bd4c7267d48ef461a1d613ec9ec0d520c, 9f70f46bd4c7267d48ef461a1d613ec9ec0d520c, 9f70f46bd4c7267d48ef461a1d613ec9ec0d520c, 9f70f46bd4c7267d48ef461a1d613ec9ec0d520c, 9f70f46bd4c7267d48ef461a1d613ec9ec0d520c, 9f70f46bd4c7267d48ef461a1d613ec9ec0d520cunaffected
LinuxLinux3.13, 0, 5.4.289, 5.10.233, 5.15.176, 6.1.124, 6.6.70, 6.12.9, 6.13affected
Weakness

CWE details

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.