scsi: target: target_core_configfs: Add length check to avoid buffer overflow
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 · < 53c6351597e6a17ec6619f6f060d54128cb9a187| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
scsi: target: target_core_configfs: Add length check to avoid buffer overflow
A buffer overflow arises from the usage of snprintf to write into the buffer "buf" in target_lu_gp_members_show function located in /drivers/target/target_core_configfs.c. This buffer is allocated with size LU_GROUP_NAME_BUF (256 bytes).
snprintf(...) formats multiple strings into buf with the HBA name (hba->hba_group.cg_item), a slash character, a devicename (dev-> dev_group.cg_item) and a newline character, the total formatted string length may exceed the buffer size of 256 bytes.
Since snprintf() returns the total number of bytes that would have been written (the length of %s/%sn ), this value may exceed the buffer length (256 bytes) passed to memcpy(), this will ultimately cause function memcpy reporting a buffer overflow error.
An additional check of the return value of snprintf() can avoid this buffer overflow.
From the CVE record · Linux
The Linux kernel's SCSI target configfs code can overflow a 256-byte buffer when a formatted HBA name and device name exceed its size. An attacker who can cause those names to be used may trigger the overflow; the input does not specify whether this requires local access, authentication, or user interaction.
Engineers running Linux kernels with SCSI target configfs should check their versions; affected versions are not specified.