In the Linux kernel, the following vulnerability has been resolved:
can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path
In es58x_rx_err_msg(), if can->do_set_mode() fails, the function
directly returns without calling netif_rx(skb). This means that the
skb previously allocated by alloc_can_err_skb() is not freed. In other
terms, this is a memory leak.
This patch simply removes the return statement in the error branch and
let the function continue.
Issue was found with GCC -fanalyzer, please follow the link below for
details.
Metrics
Affected Vendors & Products
References
History
Mon, 21 Apr 2025 19:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Linux
Linux linux Kernel |
|
CPEs | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | |
Vendors & Products |
Linux
Linux linux Kernel |
Sat, 19 Apr 2025 01:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
threat_severity
|
Thu, 17 Apr 2025 20:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-401 | |
Metrics |
cvssV3_1
|
Thu, 17 Apr 2025 18:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | In the Linux kernel, the following vulnerability has been resolved: can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path In es58x_rx_err_msg(), if can->do_set_mode() fails, the function directly returns without calling netif_rx(skb). This means that the skb previously allocated by alloc_can_err_skb() is not freed. In other terms, this is a memory leak. This patch simply removes the return statement in the error branch and let the function continue. Issue was found with GCC -fanalyzer, please follow the link below for details. | |
Title | can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path | |
References |
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-04-17T18:01:31.459Z
Updated: 2025-04-17T19:49:36.575Z
Reserved: 2025-04-16T07:16:05.753Z
Link: CVE-2021-47671

Updated: 2025-04-17T19:49:24.576Z

Status : Analyzed
Published: 2025-04-17T18:15:43.933
Modified: 2025-04-21T18:40:48.773
Link: CVE-2021-47671
