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-2026-53126blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current()

Description

In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current() Add the missing put_disk() on the error path in blkcg_maybe_throttle_current(). When blkcg lookup, blkg lookup, or blkg_tryget() fails, the function jumps to the out label which only calls rcu_read_unlock() but does not release the disk reference acquired by blkcg_schedule_throttle() via get_device(). Since current->throttle_disk is already set to NULL before the lookup, blkcg_exit() cannot release this reference either, causing the disk to never be freed. Restore the reference release that was present as blk_put_queue() in the original code but was inadvertently dropped during the conversion from request_queue to gendisk.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 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-2026-53126, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.11% · top 98% of all CVEs (17 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 f05837ed73d0c73e950b2d9f2612febb0d3d451e – < 4048ed98860d3785645ebbd34f69566a6c7320c3
    • affected f05837ed73d0c73e950b2d9f2612febb0d3d451e – < 73a5af059905d171b398c8b2381632ee499948b5
    • affected f05837ed73d0c73e950b2d9f2612febb0d3d451e – < b3e005f16cd98f815429a87aef4c61e9c140779f
    • affected f05837ed73d0c73e950b2d9f2612febb0d3d451e – < 000e8454692cab9d1f1b80130e2870e355301d06
    • affected f05837ed73d0c73e950b2d9f2612febb0d3d451e – < 23308af722fefed00af5f238024c11710938fba3
  • Linux · Linux

    • affected 6.3
    • unaffected < 6.3
    • unaffected 6.6.141 – ≤ 6.6.*
    • unaffected 6.12.91 – ≤ 6.12.*
    • unaffected 6.18.33 – ≤ 6.18.*
    • unaffected 7.0.10 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .