LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50234: io_uring/af_unix: defer registered files gc to io_uring release

In the Linux kernel, the following vulnerability has been resolved: io_uring/af_unix: defer registered files gc to io_uring release Instead of putting io_uring's registered files in unix_gc() we want it to be done by io_uring itself. The trick here is to consider io_uring registered files for cycle detection but not actually putting them down. Because io_uring can't register other ring instances, this will remove all refs to the ring file triggering the ->release path and clean up with io_ring_ctx_free(). [axboe: add kerneldoc comment to skb, fold in skb leak fix]

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50234 is a Linux kernel issue involving io_uring and Unix socket garbage collection. The public record says the vulnerability has been resolved, but it does not state business impact, CVSS severity, or exploitability. Organizations running affected Linux kernel lines should verify whether their vendor kernel includes the referenced stable fixes.

Executive priority

Treat as a kernel maintenance priority, not an emergency based on current evidence. Because impact and exploitation are unclear, focus on confirming exposure and applying normal supported kernel updates, especially on shared infrastructure where kernel flaws can carry higher operational risk.

Technical view

The fix changes how io_uring registered files are handled during af_unix garbage collection. Registered files are considered for cycle detection, but cleanup is deferred to io_uring release handling. The source bundle identifies affected Linux kernel versions and multiple stable commit references, but does not provide a CWE, CVSS score, or detailed impact statement.

Likely exposure

Exposure is limited to systems running affected Linux kernels with the vulnerable io_uring/af_unix code path. The source lists Linux kernel versions including 5.1 through 6.1-era stable lines, but distribution backports may change exposure. Confirm with vendor kernel advisories and commit inclusion.

Exploitation context

No active exploitation is indicated in the provided sources, and this CVE is not listed as KEV in the source bundle. The public description is a kernel fix note, not an exploit advisory. Exploitability and real-world attack prerequisites are not established by the provided evidence.

Researcher notes

The public record provides a resolved kernel commit narrative but omits CVSS, CWE, exploit status, and concrete impact. Analysis should center on whether downstream kernels include the stable commits. Avoid assuming privilege escalation, denial of service, or remote reachability without additional vendor evidence.

Mitigation direction

  • Update affected Linux kernels using distribution or vendor-supported packages.
  • Verify the kernel includes one of the referenced stable fixes.
  • If immediate updating is not possible, monitor vendor guidance for supported mitigations.
  • Prioritize internet-facing or multi-tenant Linux systems after vendor confirmation.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, and appliances.
  • Compare installed kernels against vendor advisories for CVE-2022-50234.
  • Check package changelogs for the referenced io_uring/af_unix fix.
  • Confirm rebooted systems are running the remediated kernel.
Prepared
Confidence
medium
Sources
8

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-50234 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
7Source 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
LinuxLinux6b06314c47e141031be043539900d80d2c7ba10f, 6b06314c47e141031be043539900d80d2c7ba10f, 6b06314c47e141031be043539900d80d2c7ba10f, 6b06314c47e141031be043539900d80d2c7ba10f, 6b06314c47e141031be043539900d80d2c7ba10f, 6b06314c47e141031be043539900d80d2c7ba10funaffected
LinuxLinux5.1, 0, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 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.