CVE-2022-50234

io_uring/af_unix: defer registered files gc to io_uring release

HIGH
7.8
CVSS Score
Published: September 15, 2025 at 02:01 PM UTC
Updated: August 5, 2026 at 09:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

Description

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]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.1 ≤ v < 5.10.1505.1 ≤ v < 5.15.755.1 ≤ v < 5.19.175.1 ≤ v < 5.4.2205.1 ≤ v < 6.0.35.1 ≤ v < 6.15.11 ≤ v < 5.15.755.16 ≤ v < 5.19.175.5 ≤ v < 5.10.1506.0 ≤ v < 6.0.35.16b06314c47e141031be043539900d80d2c7ba10f
Vendor states this is fixed in 4df9719df1865f6770af9bc7880874af0e594b2 (fixed)
Vendor states this is fixed in 75e94c7e8859e58aadc15a98cc9704edff47d4f2 (fixed)
Vendor states this is fixed in 813d8fe5d30388f73a21d3a2bf46b0a1fd72498c (fixed)
Vendor states this is fixed in 91bfc81741b8d3aeb3b7ab8636f911b2de6e80 (fixed)
Vendor states this is fixed in b4293c01ee0d0ecdd3cb5801e13f62271144667a (fixed)
Vendor states this is fixed in c378c479c5175833bb22ff71974cda47d7b05401 (fixed)
Vendor states this is fixed in 5.1 (unaffected)
Vendor states this is fixed in 5.10.150 (unaffected)
Vendor states this is fixed in 5.15.75 (unaffected)
Vendor states this is fixed in 5.19.17 (unaffected)
Vendor states this is fixed in 5.4.220 (unaffected)
Vendor states this is fixed in 6.0.3 (unaffected)
Vendor states this is fixed in 6.1 (unaffected)

References (6)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/0091bfc81741b8d3aeb3b7ab8636f911b2de6e80
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/04df9719df1865f6770af9bc7880874af0e594b2
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/75e94c7e8859e58aadc15a98cc9704edff47d4f2
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/813d8fe5d30388f73a21d3a2bf46b0a1fd72498c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b4293c01ee0d0ecdd3cb5801e13f62271144667a
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/c378c479c5175833bb22ff71974cda47d7b05401

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card