can: pch_can: pch_can_rx_normal: fix use after free
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b21d18b51b31a24d17f883b678432fbdee3d5675 · < 703dde112021c93d6e89443c070e7dbd4dea612e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
can: pch_can: pch_can_rx_normal: fix use after free
After calling netif_receive_skb(skb), dereferencing skb is unsafe. Especially, the can_frame cf which aliases skb memory is dereferenced just after the call netif_receive_skb(skb).
Reordering the lines solves the issue.
From the CVE record · Linux
The Linux kernel's pch_can_rx_normal function dereferences packet memory after passing it to netif_receive_skb, causing a use-after-free. The input does not specify how an attacker could trigger it or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with the pch_can driver should check their versions; affected versions are not specified.