CVE-2026-80611: ACPI: processor_idle: Mark LPI enter functions as __cpuidle
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 10f675902a5fc88ccfe34bb8aa37de50806b03b1, 5b6165d7ec38477e8cfa41bfa464959957953822, 8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 10f675902a5fc88ccfe34bb8aa37de50806b03b1, 5b6165d7ec38477e8cfa41bfa464959957953822, 8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: ACPI: processor_idle: Mark LPI enter functions as __cpuidle When function tracing or Kprobes is enabled, entering an ACPI Low Power Idle (LPI) state triggers the following RCU splat: RCU not on for: acpi_idle_lpi_enter+0x4/0xd8 WARNING: CPU: 8 PID: 0 at include/linux/trace_recursion.h:162 function_trace_call+0x1e8/0x228 The acpi_idle_lpi_enter() function is invoked within the cpuidle path after RCU has already been disabled for the current local CPU. Consequently, ftrace's function_trace_call() expects RCU to be actively watching before recording trace data, emitting a warning if it is not. Fix this by annotating acpi_idle_lpi_enter(), the generic __weak stub, and the RISC-V implementation of acpi_processor_ffh_lpi_enter() with __cpuidle. This moves these functions into the '.cpuidle.text' section, implicitly disabling ftrace instrumentation (notrace) along this sensitive path and preventing trace-induced RCU warnings during idle entry.
- Published
- Aug 28, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.8affected
- a36a7fecfe6071732075ad5aa31196adce13181b and later · before 8ca5dfe4249bbb6bd34f37d16c2ea933c31f6a2aaffected · git
- a36a7fecfe6071732075ad5aa31196adce13181b and later · before c17fe25dcb55ab94f6aa2930b7504ea666d5fcc2affected · git
- a36a7fecfe6071732075ad5aa31196adce13181b and later · before 10f675902a5fc88ccfe34bb8aa37de50806b03b1affected · git
- a36a7fecfe6071732075ad5aa31196adce13181b and later · before 5b6165d7ec38477e8cfa41bfa464959957953822affected · git
- a36a7fecfe6071732075ad5aa31196adce13181b and later · before 8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9affected · git
- a36a7fecfe6071732075ad5aa31196adce13181b and later · before 956ca5d72c76504824c8eb601879da9476973e15affected · git
- before 4.8not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.192-1 | 6.1.192-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80607Aug 28, 2026 · tracing/probes: Remove WARN_ON_ONCE from parse_btf_arg0Monitor
- ← EarlierCVE-2026-80609Aug 28, 2026 · qede: fix out-of-bounds check for cqe->len_list[]39Monitor
- Later →CVE-2026-80613Aug 28, 2026 · veth: fix NAPI leak in XDP enable error path31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 10f675902a5fc88ccfe34bb8aa37de50806b03b1 | Vendor (CNA) |
| Linux Linux | 5b6165d7ec38477e8cfa41bfa464959957953822 | Vendor (CNA) |
| Linux Linux | 8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9 | Vendor (CNA) |
| Linux Linux | 8ca5dfe4249bbb6bd34f37d16c2ea933c31f6a2a | Vendor (CNA) |
| Linux Linux | 956ca5d72c76504824c8eb601879da9476973e15 | Vendor (CNA) |
| Linux Linux | c17fe25dcb55ab94f6aa2930b7504ea666d5fcc2 | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.192-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.100-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0945 · Aug 31, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/5b6165d7ec38477e8cfa41bfa464959957953822
- git.kernel.org/stable/c/8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9
- git.kernel.org/stable/c/8ca5dfe4249bbb6bd34f37d16c2ea933c31f6a2a
- git.kernel.org/stable/c/956ca5d72c76504824c8eb601879da9476973e15
- git.kernel.org/stable/c/c17fe25dcb55ab94f6aa2930b7504ea666d5fcc2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.