CVE-2023-53421blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()
- 5.5MediumCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 1 day later
· 1 day later
Published
- 9 months later
· 9 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected f73316482977ac401ac37245c9df48079d4e11f3 – < 58c135513562698f222a58ba07dbdfcfb268aa0d
- affected f73316482977ac401ac37245c9df48079d4e11f3 – < 0561aa6033dd181594116d705c41fc16e97161a2
- affected f73316482977ac401ac37245c9df48079d4e11f3 – < 892faa76be894d324bf48b12a55c7af7be2bad83
- affected f73316482977ac401ac37245c9df48079d4e11f3 – < b0d26283af612b9e0cc3188b0b88ad7fdea447e8
- affected f73316482977ac401ac37245c9df48079d4e11f3 – < abbce7f82613ea5eeefd0fc3c1c8e449b9cef2a2
- affected f73316482977ac401ac37245c9df48079d4e11f3 – < 3d2af77e31ade05ff7ccc3658c3635ec1bea0979
- affected 5.5
- unaffected < 5.5
- unaffected 5.10.258 – ≤ 5.10.*
- unaffected 5.15.199 – ≤ 5.15.*
- unaffected 6.1.162 – ≤ 6.1.*
- unaffected 6.3.13 – ≤ 6.3.*
- unaffected 6.4.4 – ≤ 6.4.*
- unaffected 6.5 – ≤ *
References
References6
- https://git.kernel.org/stable/c/58c135513562698f222a58ba07dbdfcfb268aa0d (opens in a new tab)
- https://git.kernel.org/stable/c/0561aa6033dd181594116d705c41fc16e97161a2 (opens in a new tab)
- https://git.kernel.org/stable/c/892faa76be894d324bf48b12a55c7af7be2bad83 (opens in a new tab)
- https://git.kernel.org/stable/c/b0d26283af612b9e0cc3188b0b88ad7fdea447e8 (opens in a new tab)
- https://git.kernel.org/stable/c/abbce7f82613ea5eeefd0fc3c1c8e449b9cef2a2 (opens in a new tab)
- https://git.kernel.org/stable/c/3d2af77e31ade05ff7ccc3658c3635ec1bea0979 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-29892 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-53421)Record last updated .