LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49198: mptcp: Fix crash due to tcp_tsorted_anchor was initialized before release skb

In the Linux kernel, the following vulnerability has been resolved: mptcp: Fix crash due to tcp_tsorted_anchor was initialized before release skb Got crash when doing pressure test of mptcp: =========================================================================== dst_release: dst:ffffa06ce6e5c058 refcnt:-1 kernel tried to execute NX-protected page - exploit attempt? (uid: 0) BUG: unable to handle kernel paging request at ffffa06ce6e5c058 PGD 190a01067 P4D 190a01067 PUD 43fffb067 PMD 22e403063 PTE 8000000226e5c063 Oops: 0011 [#1] SMP PTI CPU: 7 PID: 7823 Comm: kworker/7:0 Kdump: loaded Tainted: G E Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.2.1 04/01/2014 Call Trace: ? skb_release_head_state+0x68/0x100 ? skb_release_all+0xe/0x30 ? kfree_skb+0x32/0xa0 ? mptcp_sendmsg_frag+0x57e/0x750 ? __mptcp_retrans+0x21b/0x3c0 ? __switch_to_asm+0x35/0x70 ? mptcp_worker+0x25e/0x320 ? process_one_work+0x1a7/0x360 ? worker_thread+0x30/0x390 ? create_worker+0x1a0/0x1a0 ? kthread+0x112/0x130 ? kthread_flush_work_fn+0x10/0x10 ? ret_from_fork+0x35/0x40 =========================================================================== In __mptcp_alloc_tx_skb skb was allocated and skb->tcp_tsorted_anchor will be initialized, in under memory pressure situation sk_wmem_schedule will return false and then kfree_skb. In this case skb->_skb_refdst is not null because_skb_refdst and tcp_tsorted_anchor are stored in the same mem, and kfree_skb will try to release dst and cause crash.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can crash a system when Multipath TCP handles memory pressure. The public record describes a resolved kernel bug, not confirmed active exploitation. Business impact is primarily availability risk for systems running affected kernel versions with MPTCP enabled or in use.

Executive priority

Treat as a patch-management priority for Linux hosts where MPTCP is enabled or availability is critical. It is not supported by the supplied evidence as an emergency internet-wide exploitation issue.

Technical view

The issue is in MPTCP transmit skb handling. tcp_tsorted_anchor was initialized before a failed memory scheduling path released the skb, corrupting overlapping storage with _skb_refdst and causing kfree_skb to release an invalid dst pointer and crash the kernel.

Likely exposure

Exposure appears limited to Linux systems on the listed affected kernel versions or unpatched downstream builds, especially where MPTCP is enabled or exercised. Distribution backports may change actual exposure.

Exploitation context

The sources describe crashes during MPTCP pressure testing. They do not identify active exploitation, public exploit availability, or a confirmed remote attack path. CISA KEV status is false in the bundle.

Researcher notes

The record lacks CVSS, CWE, and detailed affected range semantics. The strongest evidence is the kernel fix description and stable commit references. Avoid assuming remote exploitability without additional vendor or maintainer analysis.

Mitigation direction

  • Apply kernel updates containing the referenced stable fixes.
  • Check distribution advisories for backported fixes and affected package versions.
  • Review whether MPTCP is enabled or required on exposed systems.
  • Prioritize availability-sensitive servers using affected kernel branches.

Validation and detection

  • Inventory Linux kernel versions across production and edge systems.
  • Confirm whether MPTCP is enabled or used in relevant workloads.
  • Map installed kernels to vendor advisories or the referenced stable commits.
  • Review crash logs for MPTCP, skb, dst_release, or kfree_skb traces.
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-49198 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
LinuxLinux289f2f58266777f45a52cd55dea96d736e6244c9, f70cad1085d1e01d3ec73c1078405f906237feee, f70cad1085d1e01d3ec73c1078405f906237feee, f70cad1085d1e01d3ec73c1078405f906237feeeunaffected
LinuxLinux5.16, 0, 5.16.19, 5.17.2, 5.18affected
Weakness

CWE details

No CWE listed

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