Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

redhat логотип

CVE-2026-99272

Опубликовано: 07 нояб. 2026
Источник: redhat
CVSS3: 7.1
EPSS Низкий

Описание

In the Linux kernel, the following vulnerability has been resolved: smb: client: validate the data area in SMB2_read() SMB2_read() copies le32_to_cpu(rsp->DataLength) bytes from (char *)rsp + rsp->DataOffset without checking that the range lies within the response actually received. A READ response with DataOffset == 0 makes smb2_get_data_area_len() zero the data length, so smb2_check_message() accepts a frame as short as the fixed response, while SMB2_read() still uses the server-supplied DataLength, capped only by CIFS_MAX_MSGSIZE and the caller's length. A malicious server can answer the synchronous read used by the mfsymlinks (or SFU) symlink parser with an 81-byte READ response carrying DataOffset 0 and DataLength 1067, making the client copy 1067 bytes from a 448-byte receive object (KASAN slab-out-of-bounds; up to 16 KiB in the general case). Clamp a zero (or header-overlapping) DataOffset to read_rsp_size, as handle_read_data() does for the asynchronous path, and reject the response unless DataOffset + DataLength fits within rsp_iov.iov_len. The SMB1 helper was fixed the same way in 5be5bdda5863.

A flaw was found in the Linux kernel's Server Message Block (SMB) client. The SMB2 read handler does not properly validate whether the data range specified by the server fits within the boundaries of the received packet. A malicious SMB server could exploit this vulnerability by sending a crafted read response with an invalid data offset and length, triggering an out-of-bounds memory read. This issue can lead to a system crash, resulting in a Denial of Service (DoS), or potentially expose sensitive kernel memory.

Отчет

This vulnerability is rated as Important because a rogue or compromised SMB server can induce a kernel-space slab out-of-bounds read, leading directly to a client system crash or potential memory disclosure. Exploitation depends on a user or automated process initiating file operations against an untrusted network share, limiting the attack surface to active CIFS client connections. Red Hat Enterprise Linux systems that do not mount remote SMB shares or that restrict mounts to trusted internal infrastructure are not vulnerable to external exploitation.

Меры по смягчению последствий

To mitigate this vulnerability, prevent the cifs kernel module from loading if SMB client mounts are not required:

  1. Create a configuration file to prevent the module from being loaded: echo "install cifs /bin/true" > /etc/modprobe.d/disable-cifs.conf
  2. If the module is currently loaded, unmount all active CIFS shares and attempt to remove it: modprobe -r cifs Warning: Unloading the kernel module will terminate active SMB connections, and a system reboot may be required to fully ensure the module remains unloaded if it is currently held in use by running processes. Caveats: Disabling the cifs module prevents the system from mounting remote SMB/CIFS file shares. If SMB client functionality is business-critical, ensure mounts are strictly restricted to trusted internal SMB servers.

Затронутые пакеты

ПлатформаПакетСостояниеРекомендацияРелиз
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelAffected
Red Hat Enterprise Linux 8kernel-rtAffected
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtAffected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Affected

Показывать по

Дополнительная информация

Статус:

Important
Дефект:
CWE-125
https://bugzilla.redhat.com/show_bug.cgi?id=2568632kernel: kernel: out-of-bounds read in SMB client via crafted read response

EPSS

Процентиль: 5%
0.00157
Низкий

7.1 High

CVSS3

Связанные уязвимости

ubuntu
13 дней назад

In the Linux kernel, the following vulnerability has been resolved: smb: client: validate the data area in SMB2_read() SMB2_read() copies le32_to_cpu(rsp->DataLength) bytes from (char *)rsp + rsp->DataOffset without checking that the range lies within the response actually received. A READ response with DataOffset == 0 makes smb2_get_data_area_len() zero the data length, so smb2_check_message() accepts a frame as short as the fixed response, while SMB2_read() still uses the server-supplied DataLength, capped only by CIFS_MAX_MSGSIZE and the caller's length. A malicious server can answer the synchronous read used by the mfsymlinks (or SFU) symlink parser with an 81-byte READ response carrying DataOffset 0 and DataLength 1067, making the client copy 1067 bytes from a 448-byte receive object (KASAN slab-out-of-bounds; up to 16 KiB in the general case). Clamp a zero (or header-overlapping) DataOffset to read_rsp_size, as handle_read_data() does for the asynchronous path, and reject the ...

nvd
13 дней назад

In the Linux kernel, the following vulnerability has been resolved: smb: client: validate the data area in SMB2_read() SMB2_read() copies le32_to_cpu(rsp->DataLength) bytes from (char *)rsp + rsp->DataOffset without checking that the range lies within the response actually received. A READ response with DataOffset == 0 makes smb2_get_data_area_len() zero the data length, so smb2_check_message() accepts a frame as short as the fixed response, while SMB2_read() still uses the server-supplied DataLength, capped only by CIFS_MAX_MSGSIZE and the caller's length. A malicious server can answer the synchronous read used by the mfsymlinks (or SFU) symlink parser with an 81-byte READ response carrying DataOffset 0 and DataLength 1067, making the client copy 1067 bytes from a 448-byte receive object (KASAN slab-out-of-bounds; up to 16 KiB in the general case). Clamp a zero (or header-overlapping) DataOffset to read_rsp_size, as handle_read_data() does for the asynchronous path, and reject the

CVSS3: 6.5
msrc
8 дней назад

smb: client: validate the data area in SMB2_read()

debian
13 дней назад

In the Linux kernel, the following vulnerability has been resolved: s ...

github
13 дней назад

In the Linux kernel, the following vulnerability has been resolved: smb: client: validate the data area in SMB2_read() SMB2_read() copies le32_to_cpu(rsp->DataLength) bytes from (char *)rsp + rsp->DataOffset without checking that the range lies within the response actually received. A READ response with DataOffset == 0 makes smb2_get_data_area_len() zero the data length, so smb2_check_message() accepts a frame as short as the fixed response, while SMB2_read() still uses the server-supplied DataLength, capped only by CIFS_MAX_MSGSIZE and the caller's length. A malicious server can answer the synchronous read used by the mfsymlinks (or SFU) symlink parser with an 81-byte READ response carrying DataOffset 0 and DataLength 1067, making the client copy 1067 bytes from a 448-byte receive object (KASAN slab-out-of-bounds; up to 16 KiB in the general case). Clamp a zero (or header-overlapping) DataOffset to read_rsp_size, as handle_read_data() does for the asynchronous path, and reject ...

EPSS

Процентиль: 5%
0.00157
Низкий

7.1 High

CVSS3