In the Linux kernel, the following vulnerability has been resolved: can: xilinxcan: xcanwriteframe(): fix use-after-free of transmitted SKB canputechoskb() takes ownership of the SKB and it may be freed during or after the call. However, xilinxcan xcanwriteframe() keeps using SKB after the call. Fix that by only calling canputechoskb() after the code is done touching the SKB. The txlock is held for the entire xcanwriteframe() execution and also on the cangetechoskb() side so the order of operations does not matter. An earlier fix commit 3d3c817c3a40 ("can: xilinxcan: Fix usage of skb memory") did not move the canputechoskb() call far enough. [mkl: add "commit" in front of sha1 in patch description] [mkl: fix indention]