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-80623coresight: ete: Always save state on power down

Description

In the Linux kernel, the following vulnerability has been resolved: coresight: ete: Always save state on power down System register ETMs and ETE are unlikely to be preserved on CPU power down. The ETE DT binding also never documented "arm,coresight-loses-context-with-cpu" so nobody would have legitimately been able to use that binding to fix it and ACPI has no such binding at all. Fix it by hard coding the setting for sysreg ETMs (ETE is always sysreg) or ACPI boots. Use a local variable when setting up save_state so that it's immune to concurrent probing when devices have different configurations which is an issue with modifying the global. This fixes the following error when using Coresight with ACPI on the FVP which supports CPU PM: coresight ete0: External agent took claim tag WARNING: drivers/hwtracing/coresight/coresight-core.c:248 at coresight_disclaim_device_unlocked+0xe0/0xe8, CPU#0: perf/117

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    Published

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

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

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (18 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 35e1c9163e025855f23a68f2470c471509e5d779 – < 0f8396271d7026583bcaa71ffe2e7f6025244705
    • affected 35e1c9163e025855f23a68f2470c471509e5d779 – < 31633ba13cc49017015f606d5c66eaf5052e99a8
    • affected 35e1c9163e025855f23a68f2470c471509e5d779 – < f58d17798882a3aa3323f9d80fe85e25a38f4b93
    • affected 35e1c9163e025855f23a68f2470c471509e5d779 – < 65d87f28daec31903fc39fee0744f7a0059c19f2
    • affected 35e1c9163e025855f23a68f2470c471509e5d779 – < 293dacd5b6a9f1275d92ca6c4fd874e54b2c8319
    • affected 35e1c9163e025855f23a68f2470c471509e5d779 – < 2ab4645fe4206c142a5f1491e191c906279686cf
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .