diff options
| author | Maciej Żenczykowski <[email protected]> | 2021-07-01 04:48:34 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2021-07-21 10:04:19 +0200 |
| commit | 8ae01239609b29ec2eff55967c8e0fe3650cfa09 (patch) | |
| tree | 952bb6ba4b5bae52c3710dc5b6d32c2d05e26b74 /tools/perf/scripts/python/stackcollapse.py | |
| parent | 6607d1a4c3c946d3420d33d1b561d7bee8f693c9 (diff) | |
usb: gadget: u_ether: fix a potential null pointer dereference
f_ncm tx timeout can call us with null skb to flush
a pending frame. In this case skb is NULL to begin
with but ceases to be null after dev->wrap() completes.
In such a case in->maxpacket will be read, even though
we've failed to check that 'in' is not NULL.
Though I've never observed this fail in practice,
however the 'flush operation' simply does not make sense with
a null usb IN endpoint - there's nowhere to flush to...
(note that we're the gadget/device, and IN is from the point
of view of the host, so here IN actually means outbound...)
Cc: Brooke Basile <[email protected]>
Cc: "Bryan O'Donoghue" <[email protected]>
Cc: Felipe Balbi <[email protected]>
Cc: Greg Kroah-Hartman <[email protected]>
Cc: Lorenzo Colitti <[email protected]>
Signed-off-by: Maciej Żenczykowski <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions