can: j1939: j1939_tp_tx_dat_new(): fix out-of-bounds memory access
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9d71dd0c70099914fcd063135da3c580865e924c · < b45193cb4df556fe6251b285a5ce44046dd36b4a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
can: j1939: j1939_tp_tx_dat_new(): fix out-of-bounds memory access
In the j1939_tp_tx_dat_new() function, an out-of-bounds memory access could occur during the memcpy() operation if the size of skb->cb is larger than the size of struct j1939_sk_buff_cb. This is because the memcpy() operation uses the size of skb->cb, leading to a read beyond the struct j1939_sk_buff_cb.
Updated the memcpy() operation to use the size of struct j1939_sk_buff_cb instead of the size of skb->cb. This ensures that the memcpy() operation only reads the memory within the bounds of struct j1939_sk_buff_cb, preventing out-of-bounds memory access.
Additionally, add a BUILD_BUG_ON() to check that the size of skb->cb is greater than or equal to the size of struct j1939_sk_buff_cb. This ensures that the skb->cb buffer is large enough to hold the j1939_sk_buff_cb structure.
[mkl: rephrase commit message]
From the CVE record · Linux
The Linux kernel's j1939_tp_tx_dat_new() function can read beyond a structure during a memcpy() operation. The input does not specify how an attacker could trigger this, or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with CAN J1939 support should check their versions; affected versions are not specified in the input.