CVE-2022-24958: Linux kernel vulnerability

:linux_kernel: Updated 02 Oct 2025

Summary

01/06/2022
Yes i
High
Not published

CVE-2022-24958: In dev_config of inode.c, there is a possible arbitrary code execution due to a use after free. Affects :linux_kernel: versions >= :0, < :2022-06-05. Fixed in :2022-06-05. How to fix ↓

Also tracked for

The same CVE-2022-24958 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Linux kernel is a critical component of the Linux operating system, responsible for managing system resources and facilitating communication between hardware and software. It is widely used in various distributions, including Android. The vulnerability identified as CVE-2022-24958 affects the Linux kernel and specifically impacts the dev_config function in inode.c. This vulnerability allows for arbitrary code execution due to a use after free issue, potentially leading to local privilege escalation without requiring additional execution privileges. Exploitation of this vulnerability does not require user interaction.

Vulnerability Detail

The vulnerability arises from a use after free issue in the dev_config function of inode.c. When certain conditions are met, the function fails to properly handle a freed object, resulting in a situation where an attacker can execute arbitrary code. This can be leveraged to escalate privileges locally, potentially gaining unauthorized access to sensitive system resources. The vulnerability was introduced in an earlier version of the Linux kernel and has been fixed in subsequent updates.

How To Fix

Minimum fixed version

:2022-06-05

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no known workarounds for this vulnerability. It is recommended to apply the available patches or updates as soon as possible to mitigate the risk.

Conclusion

The CVE-2022-24958 vulnerability in the Linux kernel poses a significant risk as it allows for arbitrary code execution and local privilege escalation. To mitigate this risk, it is crucial to update the Linux kernel to a version that includes the necessary patches. Users should ensure their systems, especially Android devices, are updated with the latest security patches provided by their respective vendors. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for :linux_kernel: →

Share this vulnerability

FAQ

The vulnerability allows for arbitrary code execution and local privilege escalation, potentially enabling an attacker to gain unauthorized access to sensitive system resources.

No, user interaction is not needed for exploitation of this vulnerability.

This vulnerability affects systems running the Linux kernel, including Android devices.

Yes, the vulnerability has been fixed in the Linux kernel. Users should update their systems with the latest security patches.

Currently, there are no known workarounds for this vulnerability. It is recommended to apply the available patches or updates as soon as possible.

Related vulnerabilities

Recent vulnerabilities recorded for :linux_kernel:.

How To Fix

Minimum fixed version

:2022-06-05

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback