Linux Kernel block/blk-cgroup.c blkcg_destroy_blkgs use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.4$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Linux Kernel. This affects the function blkcg_destroy_blkgs of the file block/blk-cgroup.c. This manipulation causes use after free. This vulnerability appears as CVE-2024-0443. The attack requires local access. There is no available exploit. To fix this issue, it is recommended to deploy a patch.

Detailsinfo

A vulnerability has been found in Linux Kernel (Operating System) (affected version not known) and classified as critical. Affected by this vulnerability is the function blkcg_destroy_blkgs of the file block/blk-cgroup.c. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect availability.

The weakness was presented 01/12/2024. It is possible to read the advisory at access.redhat.com. This vulnerability is known as CVE-2024-0443 since 01/11/2024. Technical details of the vulnerability are known, but there is no available exploit.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at lore.kernel.org.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-16238). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 5.5
CNA Vector (Red Hat, Inc.): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: lore.kernel.org

Timelineinfo

01/11/2024 🔍
01/11/2024 +0 days 🔍
01/12/2024 +0 days 🔍
07/24/2025 +558 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: RHSA-2023:7077
Status: Confirmed

CVE: CVE-2024-0443 (🔍)
GCVE (CVE): GCVE-0-2024-0443
GCVE (VulDB): GCVE-100-250483
EUVD: 🔍

Entryinfo

Created: 01/12/2024 00:49
Updated: 07/24/2025 00:37
Changes: 01/12/2024 00:49 (49), 01/30/2024 17:50 (2), 01/30/2024 17:57 (1), 07/24/2025 00:37 (16)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!