Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2024-27043

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: media: edia: dvbdev: fix a use-after-free In dvb_register_device, *pdvbdev is set equal to dvbdev, which is freed in several er…

Published May 1, 2024CWE-416EPSS 0.29%

Overview

CVE-2024-27043 is a high-severity vulnerability. It was published on May 1, 2024 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. 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:

media: edia: dvbdev: fix a use-after-free

In dvb_register_device, *pdvbdev is set equal to dvbdev, which is freed

in several error-handling paths. However, *pdvbdev is not set to NULL

after dvbdev's deallocation, causing use-after-frees in many places,

for example, in the following call chain:

budget_register

|-> dvb_dmxdev_init

|-> dvb_register_device

|-> dvb_dmxdev_release

|-> dvb_unregister_device

|-> dvb_remove_device

|-> dvb_device_put

|-> kref_put

When calling dvb_unregister_device, dmxdev->dvbdev (i.e. *pdvbdev in

dvb_register_device) could point to memory that had been freed in

dvb_register_device. Thereafter, this pointer is transferred to

kref_put and triggering a use-after-free.

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/096237039d00c839f3e3a5fe6d001bf0db45b644Refgit.kernel.org/stable/c/0d3fe80b6d175c220b3e252efc6c6777e700e98eRefgit.kernel.org/stable/c/35674111a043b0482a9bc69da8850a83f465b07dRefgit.kernel.org/stable/c/437a111f79a2f5b2a5f21e27fdec6f40c8768712Refgit.kernel.org/stable/c/779e8db7efb22316c8581d6c229636d2f5694a62Refgit.kernel.org/stable/c/8c64f4cdf4e6cc5682c52523713af8c39c94e6d5Refgit.kernel.org/stable/c/b7586e902128e4fb7bfbb661cb52e4215a65637bRefgit.kernel.org/stable/c/d0f5c28333822f9baa5280d813124920720fd856Refgit.kernel.org/stable/c/f20c3270f3ed5aa6919a87e4de9bf6c05fb57086Refgit.kernel.org/stable/c/096237039d00c839f3e3a5fe6d001bf0db45b644

How CyberStrike helps

Frequently asked questions

What is CVE-2024-27043?

CVE-2024-27043 is a high-severity vulnerability. It was published on May 1, 2024 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2024-27043?

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

How do I fix or remediate CVE-2024-27043?

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-2024-27043?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2024-27043 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 HIGH CVEs from 2024

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999