Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 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

CVSS scores of CVE-2023-53421, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS: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
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected f73316482977ac401ac37245c9df48079d4e11f3 – < 58c135513562698f222a58ba07dbdfcfb268aa0d
    • affected f73316482977ac401ac37245c9df48079d4e11f3 – < 0561aa6033dd181594116d705c41fc16e97161a2
    • affected f73316482977ac401ac37245c9df48079d4e11f3 – < 892faa76be894d324bf48b12a55c7af7be2bad83
    • affected f73316482977ac401ac37245c9df48079d4e11f3 – < b0d26283af612b9e0cc3188b0b88ad7fdea447e8
    • affected f73316482977ac401ac37245c9df48079d4e11f3 – < abbce7f82613ea5eeefd0fc3c1c8e449b9cef2a2
    • affected f73316482977ac401ac37245c9df48079d4e11f3 – < 3d2af77e31ade05ff7ccc3658c3635ec1bea0979
  • Linux · Linux

    • 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

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53421 badge
[![CVE-2023-53421](https://cveledger.app/badge/CVE-2023-53421.svg)](https://cveledger.app/cve/CVE-2023-53421)

Record last updated .