# CVE-2021-47519: linux: In the Linux kernel, the following vulnerability has been resolved:  can: m_can: m_can_read_fifo: fix memory leak in...

CVE-2021-47519 is fixed in linux on 1 platform, first by DEBIAN-CVE-2021-47519, released May 24, 2024. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2021-47519
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: 0.0050
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: May 24, 2024

## Description

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.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 12.15 (bookworm) | 5.15.15-1 | [DEBIAN-CVE-2021-47519](https://patchblox.com/security/data/fix/linux/debian-cve-2021-47519.md) | May 24, 2024 |
| Linux | linux Debian 13.5 (trixie) | 5.15.15-1 | [DEBIAN-CVE-2021-47519](https://patchblox.com/security/data/fix/linux/debian-cve-2021-47519.md) | May 24, 2024 |
| Linux | linux Debian 14 | 5.15.15-1 | [DEBIAN-CVE-2021-47519](https://patchblox.com/security/data/fix/linux/debian-cve-2021-47519.md) | May 24, 2024 |

---

Data as of 2026-11-08T19:12:23Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.