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:
iouring/afunix: defer registered files gc to iouring release
Instead of putting iouring's registered files in unixgc() we want it to be done by iouring itself. The trick here is to consider iouring registered files for cycle detection but not actually putting them down. Because iouring can't register other ring instances, this will remove all refs to the ring file triggering the ->release path and clean up with ioringctxfree().
[axboe: add kerneldoc comment to skb, fold in skb leak fix]
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.0.3-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1
Event History
Frequently Asked Questions
What is the severity of CVE-2022-50234?
The severity of CVE-2022-50234 is classified as medium, as it affects the security and stability of the Linux kernel.
How do I fix CVE-2022-50234?
To fix CVE-2022-50234, update your Linux kernel to the latest version provided by your distribution.
What systems are affected by CVE-2022-50234?
CVE-2022-50234 affects Linux kernel versions prior to the fix being applied in stable releases.
What types of attacks can exploit CVE-2022-50234?
CVE-2022-50234 can potentially be exploited through local privilege escalation attacks.
When was CVE-2022-50234 announced?
CVE-2022-50234 was publicly announced in December 2022.