Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2021-47231

5.5 · MEDIUM

In the Linux kernel, the following vulnerability has been resolved: can: mcba_usb: fix memory leak in mcba_usb Syzbot reported memory leak in SocketCAN driver for Microchip CAN BUS Analyzer Tool.

Published May 21, 2024CWE-401EPSS 0.23%

Overview

CVE-2021-47231 is a medium-severity vulnerability. It was published on May 21, 2024 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

can: mcba_usb: fix memory leak in mcba_usb

Syzbot reported memory leak in SocketCAN driver for Microchip CAN BUS

Analyzer Tool. The problem was in unfreed usb_coherent.

In mcba_usb_start() 20 coherent buffers are allocated and there is

nothing, that frees them:

1) In callback function the urb is resubmitted and that's all

2) In disconnect function urbs are simply killed, but URB_FREE_BUFFER

is not set (see mcba_usb_start) and this flag cannot be used with

coherent buffers.

Fail log:

| [ 1354.053291][ T8413] mcba_usb 1-1:0.0 can0: device disconnected

| [ 1367.059384][ T8420] kmemleak: 20 new suspected memory leaks (see /sys/kernel/debug/kmem)

So, all allocated buffers should be freed with usb_free_coherent()

explicitly

NOTE:

The same pattern for allocating and freeing coherent buffers

is used in drivers/net/can/usb/kvaser_usb/kvaser_usb_core.c

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/6bd3d80d1f019cefa7011056c54b323f1d8b8e83Refgit.kernel.org/stable/c/6f87c0e21ad20dd3d22108e33db1c552dfa352a0Refgit.kernel.org/stable/c/89df95ce32be204eef2e7d4b2f6fb552fb191a68Refgit.kernel.org/stable/c/91c02557174be7f72e46ed7311e3bea1939840b0Refgit.kernel.org/stable/c/a115198caaab6d663bef75823a3c5f0802306d60Refgit.kernel.org/stable/c/d0760a4ef85697bc756d06eae17ae27f3f055401Refgit.kernel.org/stable/c/6bd3d80d1f019cefa7011056c54b323f1d8b8e83Refgit.kernel.org/stable/c/6f87c0e21ad20dd3d22108e33db1c552dfa352a0Refgit.kernel.org/stable/c/89df95ce32be204eef2e7d4b2f6fb552fb191a68Refgit.kernel.org/stable/c/91c02557174be7f72e46ed7311e3bea1939840b0

How CyberStrike helps

Frequently asked questions

What is CVE-2021-47231?

CVE-2021-47231 is a medium-severity vulnerability. It was published on May 21, 2024 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2021-47231?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2021-47231?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2021-47231?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2021-47231 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2021

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999