Linux Kernel up to 5.16.10 nvme-rdma error_recovery use after free

Summaryinfo

A vulnerability classified as critical was found in Linux Kernel up to 4.19.230/5.4.180/5.10.101/5.15.24/5.16.10. This issue affects the function error_recovery of the component nvme-rdma. The manipulation results in use after free. This vulnerability is reported as CVE-2022-48788. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Linux Kernel up to 4.19.230/5.4.180/5.10.101/5.15.24/5.16.10. It has been classified as critical. Affected is the function error_recovery of the component nvme-rdma. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: nvme-rdma: fix possible use-after-free in transport error_recovery work While nvme_rdma_submit_async_event_work is checking the ctrl and queue state before preparing the AER command and scheduling io_work, in order to fully prevent a race where this check is not reliable the error recovery work must flush async_event_work before continuing to destroy the admin queue after setting the ctrl state to RESETTING such that there is no race .submit_async_event and the error recovery handler itself changing the ctrl state.

The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2022-48788 since 07/16/2024. The exploitability is told to be difficult. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 01/11/2025).

The vulnerability scanner Nessus provides a plugin with the ID 208672 (SUSE SLES12 Security Update : kernel (SUSE-SU-2024:3566-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.19.231, 5.4.181, 5.10.102, 5.15.25 or 5.16.11 eliminates this vulnerability. Applying the patch 5593f72d1922/d411b2a5da68/324f5bdc52ec/646952b2210f/ea86027ac467/b6bb1722f34b is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (208672). Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 4.19.230
• 5.4.180
• 5.10.101
• 5.15.0
• 5.15.1
• 5.15.2
• 5.15.3
• 5.15.4
• 5.15.5
• 5.15.6
• 5.15.7
• 5.15.8
• 5.15.9
• 5.15.10
• 5.15.11
• 5.15.12
• 5.15.13
• 5.15.14
• 5.15.15
• 5.15.16
• 5.15.17
• 5.15.18
• 5.15.19
• 5.15.20
• 5.15.21
• 5.15.22
• 5.15.23
• 5.15.24
• 5.16.0
• 5.16.1
• 5.16.2
• 5.16.3
• 5.16.4
• 5.16.5
• 5.16.6
• 5.16.7
• 5.16.8
• 5.16.9
• 5.16.10

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion