Analyst readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-safety flaw in SCTP handling. A local low-privileged user may be able to trigger memory corruption with high confidentiality, integrity, and availability impact. The sources show kernel stable fixes, but no public source in the bundle proves active exploitation.
Executive priority
Handle as a high-priority kernel patching item, especially on shared Linux systems. It is not shown as actively exploited in the supplied sources, but impact is high if triggered locally.
Technical view
The vulnerable SCTP I-FWD-TSN skip traversal checked only against the chunk end. If the remaining bytes were smaller than struct sctp_ifwdtsn_skip, dereferencing the trailing position could cause an out-of-bounds condition. The fix tightens bounds checking before dereference.
Likely exposure
Exposure is limited to Linux systems running affected kernel code with SCTP support present. The bundle lists Linux kernel affected version markers including 4.16, 4.19.281, 5.4.241, 5.10.178, 5.15.108, 6.1.25, 6.2.12, and 6.3.
Exploitation context
The CVSS vector is local, low complexity, low privileges, no user interaction. The bundle marks KEV as false and provides no cited evidence of exploitation in the wild. Treat exploit status as unproven from the supplied evidence.
Researcher notes
The key validation point is whether the running kernel contains the corrected sctp_ifwdtsn_skip bounds check. Source evidence is limited to the CVE record, CVE List data, and Linux stable commit references; no exploitability details beyond CVSS are supplied.
Mitigation direction
- Update Linux kernels to vendor releases containing the referenced stable fixes.
- Confirm distribution advisories map the fix into your packaged kernel version.
- Prioritize hosts where untrusted local users or workloads can execute code.
- If SCTP is unnecessary, check vendor guidance for reducing SCTP availability.
Validation and detection
- Inventory running kernel versions across servers, endpoints, containers, and appliances.
- Check whether each kernel includes the referenced stable fix commits or vendor backports.
- Identify systems where low-privileged local users can run code.
- Confirm SCTP support is present or enabled before treating exposure as reachable.
Public sources used
Based on public source material and reviewed before publication.
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-787: 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 lookupCVE-2023-53372 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/4fbd094d4131a10d06a45d64158567052a35b3f4CVE reference, Linux
- https://git.kernel.org/stable/c/ad831a7079c99c01e801764b53bc9997c2e9c0f7CVE reference, Linux
- https://git.kernel.org/stable/c/79b28f42214a3d0d6a8c514db3602260bd5d6cb5CVE reference, Linux
- https://git.kernel.org/stable/c/6109f5b13ce3e3e537db6f18976ec0e9118d1c6fCVE reference, Linux
- https://git.kernel.org/stable/c/5c9367ac5a22d71841bcd00130f9146c9b227d57CVE reference, Linux
- https://git.kernel.org/stable/c/ad988e9b5ff04607e624a459209e8c2d0c15fc73CVE reference, Linux
- https://git.kernel.org/stable/c/32832a2caf82663870126c5186cf8f86c8b2a649CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.