aboutsummaryrefslogtreecommitdiff
path: root/lib/mpi/mpi-sub-ui.c
diff options
context:
space:
mode:
authorXiaomeng Tong <[email protected]>2022-03-29 09:21:34 +0800
committerMark Brown <[email protected]>2022-04-05 10:24:44 +0100
commitf730a46b931d894816af34a0ff8e4ad51565b39f (patch)
tree3698abbb440c675bb3abe454b33087b9bed5a4d9 /lib/mpi/mpi-sub-ui.c
parentfb6d679fee95d272c0a94912c4e534146823ee89 (diff)
ASoC: soc-dapm: fix two incorrect uses of list iterator
These two bug are here: list_for_each_entry_safe_continue(w, n, list, power_list); list_for_each_entry_safe_continue(w, n, list, power_list); After the list_for_each_entry_safe_continue() exits, the list iterator will always be a bogus pointer which point to an invalid struct objdect containing HEAD member. The funciton poniter 'w->event' will be a invalid value which can lead to a control-flow hijack if the 'w' can be controlled. The original intention was to continue the outer list_for_each_entry_safe() loop with the same entry if w->event is NULL, but misunderstanding the meaning of list_for_each_entry_safe_continue(). So just add a 'continue;' to fix the bug. Cc: [email protected] Fixes: 163cac061c973 ("ASoC: Factor out DAPM sequence execution") Signed-off-by: Xiaomeng Tong <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Mark Brown <[email protected]>
Diffstat (limited to 'lib/mpi/mpi-sub-ui.c')
0 files changed, 0 insertions, 0 deletions