diff options
| author | Oliver Hartkopp <[email protected]> | 2025-05-19 12:50:26 +0000 |
|---|---|---|
| committer | Marc Kleine-Budde <[email protected]> | 2025-05-19 14:58:12 +0000 |
| commit | c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 (patch) | |
| tree | e5ad5f75e90960a31fb9b585a59118ad2447aa6f /tools/testing/selftests/net/lib/py/netns.py | |
| parent | dt-bindings: can: microchip,mcp2510: Fix $id path (diff) | |
| download | kernel-c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7.tar.gz kernel-c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7.zip | |
can: bcm: add locking for bcm_op runtime updates
The CAN broadcast manager (CAN BCM) can send a sequence of CAN frames via
hrtimer. The content and also the length of the sequence can be changed
resp reduced at runtime where the 'currframe' counter is then set to zero.
Although this appeared to be a safe operation the updates of 'currframe'
can be triggered from user space and hrtimer context in bcm_can_tx().
Anderson Nascimento created a proof of concept that triggered a KASAN
slab-out-of-bounds read access which can be prevented with a spin_lock_bh.
At the rework of bcm_can_tx() the 'count' variable has been moved into
the protected section as this variable can be modified from both contexts
too.
Fixes: ffd980f976e7 ("[CAN]: Add broadcast manager (bcm) protocol")
Reported-by: Anderson Nascimento <[email protected]>
Tested-by: Anderson Nascimento <[email protected]>
Reviewed-by: Marc Kleine-Budde <[email protected]>
Signed-off-by: Oliver Hartkopp <[email protected]>
Link: https://patch.msgid.link/[email protected]
Cc: [email protected]
Signed-off-by: Marc Kleine-Budde <[email protected]>
Diffstat (limited to 'tools/testing/selftests/net/lib/py/netns.py')
0 files changed, 0 insertions, 0 deletions