can: m_can: m_can_read_fifo: fix memory leak in error branch
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
can: m_can: m_can_read_fifo: fix memory leak in error branch
In m_can_read_fifo(), if the second call to m_can_fifo_read() fails, the function jump to the out_fail label and returns without calling m_can_receive_skb(). This means that the skb previously allocated by alloc_can_skb() is not freed. In other terms, this is a memory leak.
This patch adds a goto label to destroy the skb if an error occurs.
Issue was found with GCC -fanalyzer, please follow the link below for details.
From the CVE record · Linux
The Linux kernel's m_can_read_fifo() leaks an allocated CAN socket buffer if its second m_can_fifo_read() call fails. The input does not establish whether an attacker can trigger this error or specify network, local, authentication, or user-interaction requirements.
Engineers running Linux kernels with the m_can CAN driver should check their kernel versions against the vendor advisory; affected versions are not specified.