CVE-2026-80623 json
coresight: ete: Always save state on power down
published 2026-08-28 2 mo ago modified 2026-10-30 10 d ago also EUVD-2026-67499
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- Linux Linux 6.1.191, 6.6.160, 6.12.114, 6.18.40, 7.1.5, 7.2
- linux Debian 13 6.12.115-2
- linux Debian 14 7.1.5-1
debian advisories DEBIAN-CVE-2026-80623
- linux Ubuntu 26.04 LTS 7.0.0-38.38
- linux-aws Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-gke Ubuntu 26.04 LTS 7.0.0-1008.9
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1015.15
- linux-azure Ubuntu 26.04 LTS 7.0.0-1017.17
- linux-riscv Ubuntu 26.04 LTS 7.0.0-38.38.1
- linux-oracle Ubuntu 26.04 LTS 7.0.0-1013.13
ubuntu advisories UBUNTU-CVE-2026-80623
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/0f8396271d7026583bcaa71ffe2e7f6025244705 commit
- git.kernel.org/stable/c/31633ba13cc49017015f606d5c66eaf5052e99a8 commit
- git.kernel.org/stable/c/f58d17798882a3aa3323f9d80fe85e25a38f4b93 commit
- git.kernel.org/stable/c/65d87f28daec31903fc39fee0744f7a0059c19f2 commit
- git.kernel.org/stable/c/293dacd5b6a9f1275d92ca6c4fd874e54b2c8319 commit
- git.kernel.org/stable/c/2ab4645fe4206c142a5f1491e191c906279686cf commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-80623 updated cvss 5.5
kernel: coresight: ete: Always save state on power down
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/0f8396271d7026583bcaa71ffe2e7f6025244705
- git.kernel.org /stable/c/31633ba13cc49017015f606d5c66eaf5052e99a8
- git.kernel.org /stable/c/f58d17798882a3aa3323f9d80fe85e25a38f4b93
- git.kernel.org /stable/c/65d87f28daec31903fc39fee0744f7a0059c19f2
- git.kernel.org /stable/c/293dacd5b6a9f1275d92ca6c4fd874e54b2c8319
- git.kernel.org /stable/c/2ab4645fe4206c142a5f1491e191c906279686cf
Sources
- CVE List CVE-2026-80623
- NVD CVE-2026-80623
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.