CVE-2022-50234
published 2025-09-15CVE-2022-50234: 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…
PriorityP338high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.15%
5.0th percentile
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
17 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.0.3-1 (bookworm) | linux 6.0.3-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 6b06314c47e141031be043539900d80d2c7ba10f < 04df9719df1865f6770af9bc7880874af0e594b2 | 04df9719df1865f6770af9bc7880874af0e594b2 |
| linux | linux | >= 6b06314c47e141031be043539900d80d2c7ba10f < c378c479c5175833bb22ff71974cda47d7b05401 | c378c479c5175833bb22ff71974cda47d7b05401 |
| linux | linux | >= 6b06314c47e141031be043539900d80d2c7ba10f < 813d8fe5d30388f73a21d3a2bf46b0a1fd72498c | 813d8fe5d30388f73a21d3a2bf46b0a1fd72498c |
| linux | linux | >= 6b06314c47e141031be043539900d80d2c7ba10f < b4293c01ee0d0ecdd3cb5801e13f62271144667a | b4293c01ee0d0ecdd3cb5801e13f62271144667a |
| linux | linux | >= 6b06314c47e141031be043539900d80d2c7ba10f < 75e94c7e8859e58aadc15a98cc9704edff47d4f2 | 75e94c7e8859e58aadc15a98cc9704edff47d4f2 |
| linux | linux | >= 6b06314c47e141031be043539900d80d2c7ba10f < 0091bfc81741b8d3aeb3b7ab8636f911b2de6e80 | 0091bfc81741b8d3aeb3b7ab8636f911b2de6e80 |
| linux | linux_kernel | >= 0 < 5.10.158-1 | 5.10.158-1 |
| linux | linux_kernel | >= 0 < 6.0.3-1 | 6.0.3-1 |
| linux | linux_kernel | >= 0 < 6.0.3-1 | 6.0.3-1 |
| linux | linux_kernel | >= 0 < 6.0.3-1 | 6.0.3-1 |
| linux | linux_kernel | >= 5.1 < 5.4.220 | 5.4.220 |
| linux | linux_kernel | >= 5.11 < 5.15.75 | 5.15.75 |
| linux | linux_kernel | >= 5.16 < 5.19.17 | 5.19.17 |
| linux | linux_kernel | >= 5.5 < 5.10.150 | 5.10.150 |
| linux | linux_kernel | >= 6.0 < 6.0.3 | 6.0.3 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: Linux kernel: Denial of Service due to improper io_uring/af_unix file cleanup
vendor_redhat·2025-09-15·CVSS 7.8
CVE-2022-50234 [HIGH] CWE-459 kernel: Linux kernel: Denial of Service due to improper io_uring/af_unix file cleanup
kernel: Linux kernel: Denial of Service due to improper io_uring/af_unix file cleanup
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]
A flaw was found in the Linux kernel's `io_uring/af_unix` component. A local user could exploit improper handling of registered files during
Debian
CVE-2022-50234: linux - In the Linux kernel, the following vulnerability has been resolved: io_uring/af...
vendor_debian·2022·CVSS 7.8
CVE-2022-50234 [HIGH] CVE-2022-50234: linux - In the Linux kernel, the following vulnerability has been resolved: io_uring/af...
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]
Scope: local
bookworm: resolved (fixed in 6.0.3-1)
bullseye: resolved (fixed in 5.10.158-1)
forky: resolved (fixed in 6.0.3-1)
sid: resolved (fixed in 6.0.3-1)
trixie: resolved (fixed in 6.0.3-1)
OSV
CVE-2022-50234: 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
osv·2025-09-15·CVSS 7.8
CVE-2022-50234 [HIGH] CVE-2022-50234: 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
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]
GHSA
GHSA-qhp4-v642-v3xp: In the Linux kernel, the following vulnerability has been resolved:
io_uring/af_unix: defer registered files gc to io_uring release
Instead of putti
ghsa_unreviewed·2025-09-15
CVE-2022-50234 [HIGH] GHSA-qhp4-v642-v3xp: In the Linux kernel, the following vulnerability has been resolved:
io_uring/af_unix: defer registered files gc to io_uring release
Instead of putti
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]
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0091bfc81741b8d3aeb3b7ab8636f911b2de6e80https://git.kernel.org/stable/c/04df9719df1865f6770af9bc7880874af0e594b2https://git.kernel.org/stable/c/75e94c7e8859e58aadc15a98cc9704edff47d4f2https://git.kernel.org/stable/c/813d8fe5d30388f73a21d3a2bf46b0a1fd72498chttps://git.kernel.org/stable/c/b4293c01ee0d0ecdd3cb5801e13f62271144667ahttps://git.kernel.org/stable/c/c378c479c5175833bb22ff71974cda47d7b05401
2025-09-15
Published