high CVSS 7.8

CVE-2022-48788·Kernel vulnerability

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.

Severity
high
Software
Kernel
Fixed in
5.16.11
Published
2024-07-16

Affected versions

From: 5.16

Until: 5.16.11

Fixed in: 5.16.11

How to fix this CVE

Update your Linux kernel to version 5.16.11 or later to resolve a use-after-free condition in the NVMe-RDMA transport layer's error recovery handler. This vulnerability can lead to kernel crashes or potential privilege escalation when the async event work queue races with the error recovery mechanism. Apply the kernel update immediately and schedule a system reboot to activate the patched version.

sudo dnf update kernel kernel-devel && sudo reboot

Defensia detects this vulnerability

How to check if you are affected

  1. Check installed kernel version: uname -r — verify it is 5.16.11 or newer; if it is between 5.16.0 and 5.16.10 inclusive, the system is vulnerable
  2. Confirm NVMe-RDMA driver is loaded: lsmod | grep nvme_rdma — if present, the vulnerable code path is active on this system
  3. Search kernel logs for NVMe transport errors: dmesg | grep -i 'nvme.*error\|nvme.*reset\|use-after-free' — exploitation attempts may trigger memory access violations
  4. Verify patch application after update: uname -r should report 5.16.11+ and dmesg should not contain nvme_rdma use-after-free warnings

FAQ

What is CVE-2022-48788?

CVE-2022-48788 is a use-after-free vulnerability in the Linux kernel's NVMe-RDMA transport layer where the async event work queue can race with the error recovery handler, potentially causing kernel memory corruption or denial of service.

Is CVE-2022-48788 being actively exploited?

No, CVE-2022-48788 is not listed in the CISA Known Exploited Vulnerabilities catalog and no public exploits are currently available, though local privilege escalation is theoretically possible if the race condition is triggered.

What versions of Kernel are affected by CVE-2022-48788?

Linux kernel versions 5.16.0 through 5.16.10 are vulnerable; the issue was resolved in 5.16.11 and later stable releases.

How do I check if my server is vulnerable to CVE-2022-48788?

Run 'uname -r' to display your kernel version; if it reports 5.16.0 through 5.16.10 and NVMe-RDMA is in use (check 'lsmod | grep nvme_rdma'), your system is vulnerable.

Does Defensia detect CVE-2022-48788?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2022-48788 will appear in your dashboard with remediation steps.

Related Kernel CVEs

CVE-2024-42256CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: cifs: Fix server re-repick on subrequest retry When a subrequest is marked for needing retry, netfs will call cifs_prepare_write() which will make cifs repick the server for the op before renegotiating credits; it then calls cifs_issue_write() which invokes smb2_async_writev() - which re-repicks the server. If a different server is then selected, this causes the increment of server->in_flight to happen against one record and the decrement to happen against another, leading to misaccounting. Fix this by just removing the repick code in smb2_async_writev(). As this is only called from netfslib-driven code, cifs_prepare_write() should always have been called first, and so server should never be NULL and the preparatory step is repeated in the event that we do a retry. The problem manifests as a warning looking something like: WARNING: CPU: 4 PID: 72896 at fs/smb/client/smb2ops.c:97 smb2_add_credits+0x3f0/0x9e0 [cifs] ... RIP: 0010:smb2_add_credits+0x3f0/0x9e0 [cifs] ... smb2_writev_callback+0x334/0x560 [cifs] cifs_demultiplex_thread+0x77a/0x11b0 [cifs] kthread+0x187/0x1d0 ret_from_fork+0x34/0x60 ret_from_fork_asm+0x1a/0x30 Which may be triggered by a number of different xfstests running against an Azure server in multichannel mode. generic/249 seems the most repeatable, but generic/215, generic/249 and generic/308 may also show it.
CVE-2024-36031CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on instantiation The expiry time of a key is unconditionally overwritten during instantiation, defaulting to turn it permanent. This causes a problem for DNS resolution as the expiration set by user-space is overwritten to TIME64_MAX, disabling further DNS updates. Fix this by restoring the condition that key_set_expiry is only called when the pre-parser sets a specific expiry.
CVE-2024-38612CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: fix invalid unregister error path The error path of seg6_init() is wrong in case CONFIG_IPV6_SEG6_LWTUNNEL is not defined. In that case if seg6_hmac_init() fails, the genl_unregister_family() isn't called. This issue exist since commit 46738b1317e1 ("ipv6: sr: add option to control lwtunnel support"), and commit 5559cea2d5aa ("ipv6: sr: fix possible use-after-free and null-ptr-deref") replaced unregister_pernet_subsys() with genl_unregister_family() in this error path.
CVE-2024-38623CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Use variable length array instead of fixed size Should fix smatch warning: ntfs_set_label() error: __builtin_memcpy() 'uni->name' too small (20 vs 256)
CVE-2021-47548CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() The if statement: if (port >= DSAF_GE_NUM) return; limits the value of port less than DSAF_GE_NUM (i.e., 8). However, if the value of port is 6 or 7, an array overflow could occur: port_rst_off = dsaf_dev->mac_cb[port]->port_rst_off; because the length of dsaf_dev->mac_cb is DSAF_MAX_PORT_NUM (i.e., 6). To fix this possible array overflow, we first check port and if it is greater than or equal to DSAF_MAX_PORT_NUM, the function returns.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2022-48788. Free for 1 server.

Get started free