CVE-2022-49013: sctp: fix memory leak in sctp_stream_outq_migrate()
In the Linux kernel, the following vulnerability has been resolved:
sctp: fix memory leak in sctp_stream_outq_migrate()
When sctp_stream_outq_migrate() is called to release stream out resources,
the memory pointed to by prio_head in stream out is not released.
The memory leak information is as follows:
unreferenced object 0xffff88801fe79f80 (size 64):
comm "sctp_repo", pid 7957, jiffies 4294951704 (age 36.480s)
hex dump (first 32 bytes):
80 9f e7 1f 80 88 ff ff 80 9f e7 1f 80 88 ff ff ................
90 9f e7 1f 80 88 ff ff 90 9f e7 1f 80 88 ff ff ................
backtrace:
[<ffffffff81b215c6>] kmalloc_trace+0x26/0x60
[<ffffffff88ae517c>] sctp_sched_prio_set+0x4cc/0x770
[<ffffffff88ad64f2>] sctp_stream_init_ext+0xd2/0x1b0
[<ffffffff88aa2604>] sctp_sendmsg_to_asoc+0x1614/0x1a30
[<ffffffff88ab7ff1>] sctp_sendmsg+0xda1/0x1ef0
[<ffffffff87f765ed>] inet_sendmsg+0x9d/0xe0
[<ffffffff8754b5b3>] sock_sendmsg+0xd3/0x120
[<ffffffff8755446a>] __sys_sendto+0x23a/0x340
[<ffffffff87554651>] __x64_sys_sendto+0xe1/0x1b0
[<ffffffff89978b49>] do_syscall_64+0x39/0xb0
[<ffffffff89a0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
Security readout for executives and security teams
Plain-English summary
CVE-2022-49013 is a Linux kernel memory leak in SCTP networking code. When certain SCTP stream resources are released, a small allocation is not freed. The public record does not provide CVSS, confirmed exploitation, or business impact beyond the leak. Treat it primarily as availability and hygiene risk for systems using SCTP.
Executive priority
Schedule remediation through normal kernel patch cycles, with faster handling for SCTP-enabled, externally reachable, or multi-tenant systems. There is no sourced evidence of active exploitation, but kernel memory leaks can degrade service availability if triggerable at scale.
Technical view
The bug is in sctp_stream_outq_migrate(). During stream out resource release, memory referenced by prio_head is not released. The CVE record includes a kernel leak trace showing 64-byte unreferenced objects from SCTP send paths. Linux stable commits are referenced as fixes across supported kernel branches.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions with SCTP enabled or used by applications. The source bundle lists affected Linux kernel ranges and stable fix commits, but does not identify distributions, configurations, or default SCTP exposure.
Exploitation context
No CISA KEV listing is provided, and the supplied sources do not report active exploitation. The public details describe a memory leak, not code execution. Practical impact depends on whether an attacker or workload can repeatedly trigger the affected SCTP path.
Researcher notes
The record lacks CVSS, CWE, and distribution-specific advisories. Analysis should focus on mapping stable commits to vendor kernels and confirming SCTP reachability. Avoid assuming exploitability beyond the documented memory leak unless additional vendor or researcher evidence becomes available.
Mitigation direction
Apply Linux vendor kernel updates that include the referenced stable SCTP fix commits.
If SCTP is unnecessary, review vendor guidance for safely reducing SCTP exposure.
Prioritize internet-facing or multi-tenant Linux systems where SCTP is enabled.
Track distribution advisories for backported fixes and supported kernel package names.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and container hosts.
Check whether running kernels include the referenced stable commits or vendor backports.
Identify systems with SCTP modules loaded or SCTP-dependent applications.
Review kernel logs and monitoring for memory pressure on SCTP-using systems.
Confirm remediation after reboot into the updated kernel.
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.
cve · low confidence lookup
CVE-2022-49013 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.