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-72260ASoC: mediatek: mt8192: Check runtime resume during probe

Description

In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8192: Check runtime resume during probe The MT8192 AFE probe enables runtime PM temporarily while reinitializing the regmap cache from hardware, but it uses pm_runtime_get_sync() without checking the return value. If runtime resume fails, probe keeps going without the device necessarily being accessible, and pm_runtime_get_sync() may leave the PM usage count incremented. The regmap_reinit_cache() failure path also returns before dropping the temporary PM reference and before clearing pm_runtime_bypass_reg_ctl. Use pm_runtime_resume_and_get() so resume failures do not leak a usage count, and clear the temporary bypass flag after dropping the probe PM reference on all regmap_reinit_cache() outcomes.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 125ab5d588b0b3b842064c4d53a666ca74521ae8 – < 9339266a8a720889d0385cfd78ba6652fe7bb1a8
    • affected 125ab5d588b0b3b842064c4d53a666ca74521ae8 – < 91b20e8c9b64042056d14394c89c81fc16a1c327
    • affected 125ab5d588b0b3b842064c4d53a666ca74521ae8 – < 6e2ee6eacc3ec7b339753abcf33812d27e03efe5
    • affected 125ab5d588b0b3b842064c4d53a666ca74521ae8 – < faa97a1a6cab01cd3e2055deb4db4e57efc43ff2
    • affected 125ab5d588b0b3b842064c4d53a666ca74521ae8 – < e0f276f1918a202e9c3ac72baffd311cecb6b8db
    • affected 125ab5d588b0b3b842064c4d53a666ca74521ae8 – < f6e424835cc05d215c57b6370b2c1e353dd02915
    • affected 125ab5d588b0b3b842064c4d53a666ca74521ae8 – < e24d5dde56a50946020b134fa8448869093db76a
  • Linux · Linux

    • affected 5.11
    • unaffected < 5.11
    • unaffected 5.15.217 – ≤ 5.15.*
    • unaffected 6.1.184 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .