summaryrefslogtreecommitdiff
path: root/drivers/tty/serial/ucc_uart.c
diff options
context:
space:
mode:
authorTodd Brandt <todd.e.brandt@intel.com>2023-03-14 21:12:56 +0300
committerJiri Kosina <jkosina@suse.cz>2023-03-24 16:09:29 +0300
commit7c3650a8007c43bc1a60d8bdb4cdbea3ad9a7dd4 (patch)
tree0991968f95b5d54392de0cdaef69bd4c9b014790 /drivers/tty/serial/ucc_uart.c
parentdbf56d2fb53b7397002219bd221cfc72aadfdc82 (diff)
downloadlinux-7c3650a8007c43bc1a60d8bdb4cdbea3ad9a7dd4.tar.xz
HID: hid-sensor-custom: Fix buffer overrun in device name
On some platforms there are some platform devices created with invalid names. For example: "HID-SENSOR-INT-020b?.39.auto" instead of "HID-SENSOR-INT-020b.39.auto" This string include some invalid characters, hence it will fail to properly load the driver which will handle this custom sensor. Also it is a problem for some user space tools, which parses the device names from ftrace and dmesg. This is because the string, real_usage, is not NULL terminated and printed with %s to form device name. To address this, initialize the real_usage string with 0s. Reported-and-tested-by: Todd Brandt <todd.e.brandt@linux.intel.com> Link: https://bugzilla.kernel.org/show_bug.cgi?id=217169 Fixes: 98c062e82451 ("HID: hid-sensor-custom: Allow more custom iio sensors") Cc: stable@vger.kernel.org Suggested-by: Philipp Jungkamp <p.jungkamp@gmx.net> Signed-off-by: Philipp Jungkamp <p.jungkamp@gmx.net> Signed-off-by: Todd Brandt <todd.e.brandt@intel.com> Reviewed-by: Andi Shyti <andi.shyti@kernel.org> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'drivers/tty/serial/ucc_uart.c')
0 files changed, 0 insertions, 0 deletions