Review reviewHigh

CVE-2022-50234

Linux Linux, linux kernel

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]

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2025.09.15
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

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 product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 6b06314c47e141031be043539900d80d2c7ba10f < 04df9719df1865f6770af9bc7880874af0e594b2, >= 6b06314c47e141031be043539900d80d2c7ba10f < c378c479c5175833bb22ff71974cda47d7b05401, >= 6b06314c47e141031be043539900d80d2c7ba10f < 813d8fe5d30388f73a21d3a2bf46b0a1fd72498c, >= 6b06314c47e141031be043539900d80d2c7ba10f < b4293c01ee0d0ecdd3cb5801e13f62271144667a, >= 6b06314c47e141031be043539900d80d2c7ba10f < 75e94c7e8859e58aadc15a98cc9704edff47d4f2, >= 6b06314c47e141031be043539900d80d2c7ba10f < 0091bfc81741b8d3aeb3b7ab8636f911b2de6e80, >= 5.1, >= 5.1 < 5.4.220, >= 5.5 < 5.10.150, >= 5.11 < 5.15.75, >= 5.16 < 5.19.17, >= 6.0 < 6.0.3
Fixed versions
5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available