scsi: target: configfs: Bound snprintf() return in tg_pt_gp_members_show()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 · < 00d91bfdce5033f5d9b4915638ae9b0553848b5d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
scsi: target: configfs: Bound snprintf() return in tg_pt_gp_members_show()
target_tg_pt_gp_members_show() formats LUN paths with snprintf() into a 256-byte stack buffer, then will memcpy() cur_len bytes from that buffer. snprintf() returns the length the output would have had, which can exceed the buffer size when the fabric WWN is long because iSCSI IQN names can be up to 223 bytes. The check at the memcpy() site only guards the destination page write, not the source read, so memcpy() will read past the stack buffer and copy adjacent stack contents to the sysfs reader, which when CONFIG_FORTIFY_SOURCE is enabled, fortify_panic() will be triggered.
Commit 27e06650a5ea ("scsi: target: target_core_configfs: Add length check to avoid buffer overflow") added the same bound to the target_lu_gp_members_show() but the tg_pt_gp variant was missed so resolve that here.
From the CVE record · Linux
The Linux kernel’s SCSI target configfs code can read past a stack buffer when formatting a LUN path with a long fabric WWN. A local sysfs reader may receive adjacent stack contents; if CONFIG_FORTIFY_SOURCE is enabled, the read instead triggers fortify_panic().
Engineers running the Linux kernel with SCSI target configfs should check whether their kernel includes the fix; affected versions were not specified.