Menu

Star on GitHub · 3.2k

CVE-2023-53421

5.5 · MEDIUM

In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats() When blkg_alloc() is called to allocate a blkcg_gq str…

Published Sep 18, 2025CWE-476EPSS 0.17%

Overview

CVE-2023-53421 is a medium-severity vulnerability. It was published on September 18, 2025 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:

blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()

When blkg_alloc() is called to allocate a blkcg_gq structure

with the associated blkg_iostat_set's, there are 2 fields within

blkg_iostat_set that requires proper initialization - blkg & sync.

The former field was introduced by commit 3b8cc6298724 ("blk-cgroup:

Optimize blkcg_rstat_flush()") while the later one was introduced by

commit f73316482977 ("blk-cgroup: reimplement basic IO stats using

cgroup rstat").

Unfortunately those fields in the blkg_iostat_set's are not properly

re-initialized when they are cleared in v1's blkcg_reset_stats(). This

can lead to a kernel panic due to NULL pointer access of the blkg

pointer. The missing initialization of sync is less problematic and

can be a problem in a debug kernel due to missing lockdep initialization.

Fix these problems by re-initializing them after memory clearing.

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.

Frequently asked questions

What is CVE-2023-53421?

CVE-2023-53421 is a medium-severity vulnerability. It was published on September 18, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2023-53421?

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-2023-53421?

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-2023-53421?

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

View all