CVE-2022-3910: Use after free in IO_uring in the Linux Kernel

Published Nov 22, 2022
·
Updated

Last updated 24 July 2024

Other sources

Use After Free vulnerability in Linux Kernel allows Privilege Escalation. An improper Update of Reference Count in iouring leads to Use-After-Free and Local Privilege Escalation. When iomsgring was invoked with a fixed file, it called iofputfile() which improperly decreased its reference count (leading to Use-After-Free and Local Privilege Escalation). Fixed files are permanently registered to the ring, and should not be put separately.

We recommend upgrading past commit https://github.com/torvalds/linux/commit/fc7222c3a9f56271fba02aabbfbae999042f1679 https://github.com/torvalds/linux/commit/fc7222c3a9f56271fba02aabbfbae999042f1679

NVD

Affected Software

7 affected componentsFixes available
Linux Linux kernel>=5.18<5.19.11
Linux Linux kernel=6.0-rc1
Linux Linux kernel=6.0-rc2
Linux Linux kernel=6.0-rc3
Linux Linux kernel=6.0-rc4
Linux Linux kernel=6.0-rc5
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
  2. Compensating control

    Ensure that fixed files are permanently registered to the io_uring ring and are not put separately (i.e., avoid invoking io_msg_ring with a separately managed fixed file that would lead to an improper reference-count decrease via io_fput_file()).

Event History

Nov 22, 2022
CVE Published
via MITRE·12:12 PM
Data Sourced
via MITRE·12:12 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 12, 2024
Data Sourced
via Launchpad·12:11 AM
Description
Sep 16, 2024
Data Sourced
via Ubuntu·03:40 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2022-3910?

CVE-2022-3910 is classified as a high-severity vulnerability due to its potential for privilege escalation.

2

How do I fix CVE-2022-3910?

To fix CVE-2022-3910, update the Linux Kernel to a patched version, such as 5.10.223-1, 6.1.123-1, or any version beyond the affected ranges.

3

Which Linux Kernel versions are affected by CVE-2022-3910?

CVE-2022-3910 affects Linux Kernel versions from 5.18 to 5.19.11 and specifically 6.0-rc1 to 6.0-rc5.

4

What does CVE-2022-3910 exploit?

CVE-2022-3910 exploits a Use-After-Free vulnerability in the io_uring component of the Linux Kernel, leading to local privilege escalation.

5

Is CVE-2022-3910 specific to a certain distribution?

CVE-2022-3910 is a vulnerability in the Linux Kernel and can affect any distribution that uses the vulnerable versions, such as Debian and its derivatives.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203