LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49838: sctp: clear out_curr if all frag chunks of current msg are pruned

In the Linux kernel, the following vulnerability has been resolved: sctp: clear out_curr if all frag chunks of current msg are pruned A crash was reported by Zhen Chen: list_del corruption, ffffa035ddf01c18->next is NULL WARNING: CPU: 1 PID: 250682 at lib/list_debug.c:49 __list_del_entry_valid+0x59/0xe0 RIP: 0010:__list_del_entry_valid+0x59/0xe0 Call Trace: sctp_sched_dequeue_common+0x17/0x70 [sctp] sctp_sched_fcfs_dequeue+0x37/0x50 [sctp] sctp_outq_flush_data+0x85/0x360 [sctp] sctp_outq_uncork+0x77/0xa0 [sctp] sctp_cmd_interpreter.constprop.0+0x164/0x1450 [sctp] sctp_side_effects+0x37/0xe0 [sctp] sctp_do_sm+0xd0/0x230 [sctp] sctp_primitive_SEND+0x2f/0x40 [sctp] sctp_sendmsg_to_asoc+0x3fa/0x5c0 [sctp] sctp_sendmsg+0x3d5/0x440 [sctp] sock_sendmsg+0x5b/0x70 and in sctp_sched_fcfs_dequeue() it dequeued a chunk from stream out_curr outq while this outq was empty. Normally stream->out_curr must be set to NULL once all frag chunks of current msg are dequeued, as we can see in sctp_sched_dequeue_done(). However, in sctp_prsctp_prune_unsent() as it is not a proper dequeue, sctp_sched_dequeue_done() is not called to do this. This patch is to fix it by simply setting out_curr to NULL when the last frag chunk of current msg is dequeued from out_curr stream in sctp_prsctp_prune_unsent().

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-49838 is a Linux kernel SCTP bug that can lead to a crash when SCTP message fragments are pruned incorrectly. Business risk is mainly service disruption on systems that expose or depend on SCTP, not confirmed data theft or remote code execution.

Executive priority

Treat as a targeted reliability risk. Prioritize systems where SCTP is enabled, exposed, or business-critical. Broad emergency action is not supported by the available evidence because exploitation and severity data are incomplete.

Technical view

In SCTP, sctp_prsctp_prune_unsent() could remove all fragments of the current message without clearing stream->out_curr. Later dequeue logic could act on an empty queue, causing list corruption and a kernel crash. The published fix clears out_curr when the last current fragment is pruned.

Likely exposure

Exposure is most likely on Linux systems running affected kernels with SCTP enabled or used by applications. Containers inherit host-kernel exposure. The source bundle does not prove all distributions or backported kernels are affected.

Exploitation context

The bundle cites a reported crash and kernel stable fixes. It does not cite active exploitation, public exploit code, KEV listing, privilege requirements, or whether the crash is remotely reachable in typical deployments.

Researcher notes

The key failure path is PR-SCTP unsent-fragment pruning bypassing normal dequeue cleanup. The evidence supports a kernel crash condition, but does not establish reachability, attacker prerequisites, or CVSS impact. Validate against actual vendor kernel trees because backports may change version conclusions.

Mitigation direction

  • Update to a vendor kernel containing the referenced SCTP stable fixes.
  • Check distribution advisories for backported fixes and exact package versions.
  • Disable or restrict SCTP where it is not operationally required.
  • Prioritize internet-facing or telecom systems that use SCTP.
  • Apply normal reboot or live-patch procedures required by your kernel vendor.

Validation and detection

  • Inventory Linux kernel versions and vendor package release levels.
  • Identify hosts with SCTP loaded, enabled, or required by applications.
  • Confirm fixed kernel packages include the referenced stable commits or vendor equivalents.
  • Review crash logs for SCTP, list_del corruption, or sctp_sched_fcfs_dequeue traces.
  • Test SCTP-dependent services after kernel update or SCTP restriction.
Prepared
Confidence
medium
Sources
6

Public sources used

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-49838 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5bbbbe32a43199c2b9ea5ea66fab6241c64beb51, 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51, 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51, 5bbbbe32a43199c2b9ea5ea66fab6241c64beb51unaffected
LinuxLinux4.15, 0, 5.10.156, 5.15.81, 6.0.10, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.