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-80626powerpc/perf: fix preempt count underflow in fsl_emb_pmu_del

Description

In the Linux kernel, the following vulnerability has been resolved: powerpc/perf: fix preempt count underflow in fsl_emb_pmu_del fsl_emb_pmu_del() unconditionally calls put_cpu_var(cpu_hw_events) at the 'out:' label, but only calls the matching get_cpu_var() after the 'i < 0' early-return check. When event->hw.idx is negative the function jumps to 'out:' without having taken get_cpu_var(), and the trailing put_cpu_var() then issues an unmatched preempt_enable(), underflowing preempt_count. On a CONFIG_PREEMPT=y kernel preempt_count would underflow and eventually present as a 'scheduling while atomic' BUG. Move put_cpu_var() to pair with get_cpu_var() so the percpu access is correctly bracketed and the 'out:' label only handles perf_pmu_enable.

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    Published

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 (20 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 a11106544f33c104706ae42d27219a409b67478e – < c0c7722308c5f303117d8bd555290fdf26b098da
    • affected a11106544f33c104706ae42d27219a409b67478e – < 67aeb1eb93d4ffd898a3e74a7f3fe46ee71feb28
    • affected a11106544f33c104706ae42d27219a409b67478e – < 9a515e00b00132b6fc3f1dd62dc5204bbda8cb10
    • affected a11106544f33c104706ae42d27219a409b67478e – < 5397142d60aa29dcf636f5459d960bfc4f97c42a
    • affected a11106544f33c104706ae42d27219a409b67478e – < b89477077c834d94381c7bf07d81193bebefcff9
    • affected a11106544f33c104706ae42d27219a409b67478e – < 73711688479df333acc134e3730fff1acba1843e
    • affected a11106544f33c104706ae42d27219a409b67478e – < b504fd953664c3f4d176ae8cb594adb3fda9d577
    • affected a11106544f33c104706ae42d27219a409b67478e – < 81e3a86030462824a67d697739cf3f387f4ba350
  • Linux · Linux

    • affected 2.6.34
    • unaffected < 2.6.34
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .