Carding 4 Carders
Professional
A logical error was detected in NVMe-oF / TCP, which gives full access to the system.
A vulnerability identified as CVE-2023-5178 has been identified in the Linux subsystem known as nvmet-tcp (NVMe-oF/TCP), which is designed to access NVMe drives over a network using the TCP protocol. The vulnerability potentially allows an attacker to remotely execute arbitrary code at the kernel level or, if local access is available, increase their privileges in the system. The fix is currently available as an update.
The problem appears from the very first version of the NVMe-oF/TCP driver and affects systems with an activated NVMe-oF/TCP server (NVME_TARGET_TCP), which by default accepts connections on network port 4420.
The vulnerability is caused by a logical error that causes the nvmet_tcp_free_crypto function to be called twice, which in turn causes some pointers to be released twice and addresses that have already been released to be dereferenced. This abnormal behavior can cause memory to be used after it is released (use-after-free) and double-free (double-free) when processing a specially constructed client message by the NVMe-oF/TCP server. It is important to note that the client can be located in both the local and global network.
A vulnerability identified as CVE-2023-5178 has been identified in the Linux subsystem known as nvmet-tcp (NVMe-oF/TCP), which is designed to access NVMe drives over a network using the TCP protocol. The vulnerability potentially allows an attacker to remotely execute arbitrary code at the kernel level or, if local access is available, increase their privileges in the system. The fix is currently available as an update.
The problem appears from the very first version of the NVMe-oF/TCP driver and affects systems with an activated NVMe-oF/TCP server (NVME_TARGET_TCP), which by default accepts connections on network port 4420.
The vulnerability is caused by a logical error that causes the nvmet_tcp_free_crypto function to be called twice, which in turn causes some pointers to be released twice and addresses that have already been released to be dereferenced. This abnormal behavior can cause memory to be used after it is released (use-after-free) and double-free (double-free) when processing a specially constructed client message by the NVMe-oF/TCP server. It is important to note that the client can be located in both the local and global network.
