CVE-2023-53421: blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()
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.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can let a local authenticated user trigger a kernel panic through a blk-cgroup statistics reset path. The business impact is service interruption, not data theft or tampering. There is no KEV listing or source evidence of active exploitation in the bundle.
Executive priority
Treat as a planned but important availability fix. It is not remote code execution, but a local denial-of-service kernel panic can disrupt production hosts, especially shared infrastructure.
Technical view
blkcg_reset_stats() clears blkg_iostat_set fields used by blk-cgroup v1 but failed to reinitialize blkg and sync. That can cause NULL pointer access and kernel panic. The CVSS vector is local, low complexity, low privileges, no user interaction, availability impact only.
Likely exposure
Exposure is most likely on Linux systems running affected kernel lines in the bundle, including 5.5 through fixed stable releases around 5.10.258, 5.15.199, 6.1.162, 6.3.13, 6.4.4, and 6.5, where blk-cgroup v1 behavior is reachable.
Exploitation context
The bundle marks KEV as false and provides no public exploitation evidence. Exploitation requires local access with low privileges and appears limited to crashing the kernel, causing denial of service rather than confidentiality or integrity compromise.
Researcher notes
Evidence is limited to the CVE record and Linux stable commit references. The root cause is incomplete reinitialization after memory clearing in blkcg_reset_stats(). Do not infer broader impact beyond local availability loss without vendor or kernel-maintainer confirmation.
Mitigation direction
Update kernels using distribution guidance that includes the referenced stable fixes.
Prioritize shared, multi-user, and container-host systems first.
Track vendor advisories for exact fixed package versions and backports.
Avoid deploying custom kernels lacking the referenced blk-cgroup fix.
Validation and detection
Inventory Linux kernel versions across servers, workstations, and container hosts.
Confirm installed kernels include a referenced stable fix or distro backport.
Check whether affected systems expose cgroup v1 blk-cgroup functionality.
Review crash logs for kernel panic traces involving blkcg_reset_stats or blkg_iostat_set.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.