In the Linux kernel, the following vulnerability has been resolved:EOL][EOL]spmi: trace: fix stack-out-of-bound access in SPMI tracing functions[EOL][EOL]trace_spmi_write_begin() and trace_spmi_read_end() both call[EOL]memcpy() with a length of "len + 1". This leads to one extra[EOL]byte being read beyond the end of the specified buffer. Fix[EOL]this out-of-bound memory access by using a length of "len"[EOL]instead.[EOL][EOL]Here is a KASAN log showing the issue:[EOL][EOL]BUG: KASAN: stack-out-of-bounds in trace_event_raw_event_spmi_read_end+0x1d0/0x234[EOL]Read of size 2 at addr ffffffc0265b7540 by task thermal@2.0-ser/1314[EOL]...[EOL]Call trace:[EOL] dump_backtrace+0x0/0x3e8[EOL] show_stack+0x2c/0x3c[EOL] dump_stack_lvl+0xdc/0x11c[EOL] print_address_description+0x74/0x384[EOL] kasan_report+0x188/0x268[EOL] kasan_check_range+0x270/0x2b0[EOL] memcpy+0x90/0xe8[EOL] trace_event_raw_event_spmi_read_end+0x1d0/0x234[EOL] spmi_read_cmd+0x294/0x3ac[EOL] spmi_ext_register_readl+0x84/0x9c[EOL] regmap_spmi_ext_read+0x144/0x1b0 [regmap_spmi][EOL] _regmap_raw_read+0x40c/0x754[EOL] regmap_raw_read+0x3a0/0x514[EOL] regmap_bulk_read+0x418/0x494[EOL] adc5_gen3_poll_wait_hs+0xe8/0x1e0 [qcom_spmi_adc5_gen3][EOL] ...[EOL] __arm64_sys_read+0x4c/0x60[EOL] invoke_syscall+0x80/0x218[EOL] el0_svc_common+0xec/0x1c8[EOL] ...[EOL][EOL]addr ffffffc0265b7540 is located in stack of task thermal@2.0-ser/1314 at offset 32 in frame:[EOL] adc5_gen3_poll_wait_hs+0x0/0x1e0 [qcom_spmi_adc5_gen3][EOL][EOL]this frame has 1 object:[EOL] [32, 33) 'status'[EOL][EOL]Memory state around the buggy address:[EOL] ffffffc0265b7400: 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1[EOL] ffffffc0265b7480: 04 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00[EOL]>ffffffc0265b7500: 00 00 00 00 f1 f1 f1 f1 01 f3 f3 f3 00 00 00 00[EOL] ^[EOL] ffffffc0265b7580: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00[EOL] ffffffc0265b7600: f1 f1 f1 f1 01 f2 07 f2 f2 f2 01 f3 00 00 00 00[EOL]================================================================== CREATE(Triage):(User=lchen-cn) [CVE-2022-50094 (https://nvd.nist.gov/vuln/detail/CVE-2022-50094)
