LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50639: io-wq: Fix memory leak in worker creation

In the Linux kernel, the following vulnerability has been resolved: io-wq: Fix memory leak in worker creation If the CPU mask allocation for a node fails, then the memory allocated for the 'io_wqe' struct of the current node doesn't get freed on the error handling path, since it has not yet been added to the 'wqes' array. This was spotted when fuzzing v6.1-rc1 with Syzkaller: BUG: memory leak unreferenced object 0xffff8880093d5000 (size 1024): comm "syz-executor.2", pid 7701, jiffies 4295048595 (age 13.900s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<00000000cb463369>] __kmem_cache_alloc_node+0x18e/0x720 [<00000000147a3f9c>] kmalloc_node_trace+0x2a/0x130 [<000000004e107011>] io_wq_create+0x7b9/0xdc0 [<00000000c38b2018>] io_uring_alloc_task_context+0x31e/0x59d [<00000000867399da>] __io_uring_add_tctx_node.cold+0x19/0x1ba [<000000007e0e7a79>] io_uring_setup.cold+0x1b80/0x1dce [<00000000b545e9f6>] __x64_sys_io_uring_setup+0x5d/0x80 [<000000008a8a7508>] do_syscall_64+0x5d/0x90 [<000000004ac08bec>] entry_SYSCALL_64_after_hwframe+0x63/0xcd

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50639 is a Linux kernel memory leak in io-wq worker creation, found by Syzkaller fuzzing. Under a specific allocation failure, kernel memory for an io_wqe structure is not freed. The public record does not show active exploitation or a CVSS score.

Executive priority

Treat as routine-to-priority kernel maintenance, not an emergency, unless you operate multi-user or untrusted-workload Linux systems. Patch through normal kernel update channels after confirming distribution impact.

Technical view

The flaw is in Linux kernel io-wq creation. If CPU mask allocation for a node fails, error handling misses freeing the current node’s io_wqe allocation because it was not added to the wqes array. The trace reaches io_uring_setup, indicating local io_uring activity is the relevant path.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel versions where local users or workloads can invoke io_uring_setup. The source bundle lists Linux kernel 5.14-era affected ranges and stable fix references, but distribution-specific status must be checked.

Exploitation context

The issue was observed during fuzzing, not reported as exploited in the wild. No KEV listing is provided. Practical abuse would require triggering the allocation-failure error path and could plausibly affect availability through memory leakage, but public evidence is limited.

Researcher notes

The record lacks CVSS, CWE, and detailed affected range semantics beyond Linux kernel versions and stable commits. The root cause is a missed free on an io_wq_create error path. Avoid assuming remote exposure; evidence points to local syscall context.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable Linux fixes.
  • Check your Linux distribution advisory for affected and fixed package versions.
  • Restrict unnecessary local access on systems pending kernel updates.
  • Review io_uring hardening options only if recommended by your vendor.

Validation and detection

  • Inventory Linux kernel versions across servers, containers hosts, and appliances.
  • Compare installed kernels against distribution advisories for CVE-2022-50639.
  • Confirm the running kernel includes the referenced stable fix commits.
  • Monitor for unusual local memory pressure until remediation is complete.
Prepared
Confidence
medium
Sources
5

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-50639 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
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0e03496d1967abf1ebb151a24318c07d07f41f7f, 0e03496d1967abf1ebb151a24318c07d07f41f7f, 0e03496d1967abf1ebb151a24318c07d07f41f7funaffected
LinuxLinux5.14, 0, 5.15.75, 6.0.4, 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.