Linux kernel vulnerabilities impact ksmbd, ktls, uio, and network stack

In the ksmbd module, which offers an implementation of a file server based on the SMB protocol built into the Linux kernel, two vulnerabilities, which allow you to remotely execute your code with kernel rights without authentication or determine the contents of kernel memory on systems with the ksmbd module activated. Problems appear starting from kernel 5.15, which included the ksmbd module. Vulnerabilities eliminated in kernel updates 6.7.2, 6.6.14, 6.1.75 and 5.15.145. You can track the fixes in the distributions on the following pages: Debian, Ubuntu, Gentoo, RHEL, SUSE, Fedora, Arch.

First vulnerability (CVE-2024-26592) can lead to attacker code execution with kernel rights when sending specially crafted unauthenticated TCP requests to the ksmbd server. The vulnerability is caused by incorrect organization of blocking objects in the installation code and interrupting the TCP connection to ksmbd, which allows creating conditions for accessing already freed memory (use-after-free).

Second vulnerability (CVE-2024-26594) causes kernel memory to leak when processing an incorrect mech token in a client-sent session setup request. The vulnerability is caused by incorrect processing of data with the SMB2 Mech token and leads to data being read from an area outside the allocated buffer.

Additionally, several more vulnerabilities in the Linux kernel can be noted:

  • CVE-2023-52439 – access to already freed memory (use-after-free) in the uio_open function of the uio subsystem, potentially allowing a local user to execute their code with kernel rights.
  • CVE-2024-26582 – access to already freed memory (use-after-free) in the kernel-level TLS implementation (ktls), potentially allowing you to increase your privileges when performing decryption operations.
  • CVE-2024-0646 – writing to a memory area outside the buffer in the ktls subsystem during certain local manipulation of the ktls socket using the splice function. The vulnerability potentially allows you to escalate your privileges in the system.
  • CVE-2023-6932 – a race condition in the implementation of the IGMP (Internet Group Management Protoco) protocol in the IPv4 stack, leading to access to already freed memory (use-after-free). The vulnerability potentially allows a local user to escalate their privileges on the system.
  • CVE-2023-52435 – MSS overflow in the skb_segment() function of the kernel network stack.
  • CVE-2024-26601 – error in the block release code in the ext4 file system
    can be used to damage the buddy bitmap.
  • CVE-2024-26598 – accessing already freed memory (use-after-free) in the KVM hypervisor.

Thanks for reading: