19 Apr
2024
19 Apr
'24
3:57 a.m.
On Thu, 11 Apr 2024 19:52:37 +0200, Caleb Connolly wrote:
If a button device fails to probe, it will still be added to the uclass device list, and therefore will still be iterated over in button_read_keys() resulting in a UAF on the buttons private data.
Resolve this by unbinding button devices that aren't active after probing, and print a warning so it's clear that the button is broken.
[...]
Applied to u-boot/master, thanks!
--
Tom