CVE-2022-49455·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: misc: ocxl: fix possible double free in ocxl_file_register_afu info_release() will be called in device_unregister() when info->dev's reference count is 0. So there is no need to call ocxl_afu_put() and kfree() again. Fix this by adding free_minor() and return to err_unregister error path.
- Severity
- high
- Software
- Kernel
- Fixed in
- 5.18.3
- Published
- 2025-02-26
Affected versions
From: 5.18
Until: 5.18.3
Fixed in: 5.18.3
How to fix this CVE
Update your Linux kernel to version 5.18.3 or later to resolve a memory management flaw in the OCX AFU file registration routine. This vulnerability could lead to system instability or privilege escalation when the affected kernel module is unloaded. Apply the patch immediately if you are running kernel versions 5.18 through 5.18.2.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check your installed kernel version: uname -r
- Verify if OCX (Open Coherence eXtensions) support is enabled in your kernel: grep -i ocxl /boot/config-$(uname -r) | grep -i CONFIG_OCXL
- Search system logs for ocxl_file_register_afu errors or double-free warnings: grep -i 'ocxl\|double free\|use-after-free' /var/log/kern.log /var/log/messages
- Confirm the fix by checking if kernel version is 5.18.3 or newer and OCXL module is properly loaded without errors: lsmod | grep ocxl && dmesg | tail -20
FAQ
What is CVE-2022-49455?
CVE-2022-49455 is a double-free vulnerability in the Linux kernel's OCX AFU (Attached Functional Unit) file registration code that occurs when device unregistration prematurely releases memory that is freed again during cleanup, potentially leading to kernel memory corruption.
Is CVE-2022-49455 being actively exploited?
No, this vulnerability is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are currently available.
What versions of Kernel are affected by CVE-2022-49455?
Linux kernel versions 5.18 through 5.18.2 are affected; the vulnerability is fixed in version 5.18.3 and later.
How do I check if my server is vulnerable to CVE-2022-49455?
Run 'uname -r' to check your kernel version—if it shows 5.18.0 through 5.18.2, you are vulnerable. Additionally, verify OCX support is enabled with 'grep CONFIG_OCXL /boot/config-$(uname -r)'.
Does Defensia detect CVE-2022-49455?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2022-49455 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/252768d32e92c1214aeebb5fec0844ca479bcf5c
- https://git.kernel.org/stable/c/8fb674216835e1f0c143762696d645facebb4685
- https://git.kernel.org/stable/c/950cf957fe34d40d63dfa3bf3968210430b6491e
- https://git.kernel.org/stable/c/9e9087cf34ee69f4e95d146ac29385d6e367a97b
- https://git.kernel.org/stable/c/de65c32ace9aa70d51facc61ba986607075e3a25
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2022-49455. Free for 1 server.
Get started free