CVE-2026-80611

RCU warnings via instrumented LPI entry

Published Aug 28, 2026 · Updated Aug 28, 2026

Improper function tracing in the Linux kernel allows local users to trigger RCU warnings during ACPI Low Power Idle entry. The acpi_idle_lpi_enter() path runs after RCU stops watching the local CPU but remains instrumentable, so function_trace_call() records where RCU is unavailable. The condition requires function tracing or Kprobes and ACPI LPI entry; the published report identifies a warning rather than a crash, privilege gain, or data exposure.

CVSS severityUnavailable
Unscored
EPSS probability0.17%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper function tracing in the Linux kernel allows local users to trigger RCU warnings during ACPI Low Power Idle entry. The acpi_idle_lpi_enter() path runs after RCU stops watching the local CPU but remains instrumentable, so function_trace_call() records where RCU is unavailable. The condition requires function tracing or Kprobes and ACPI LPI entry; the published report identifies a warning rather than a crash, privilege gain, or data exposure.

The record

CVE
CVE-2026-80611
Published
Aug 28, 2026
Updated
Aug 28, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Aug 28, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 28, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.8
  2. Affected versionversion=a36a7fecfe6071732075ad5aa31196adce13181b <10f675902a5fc88ccfe34bb8aa37de50806b03b1
  3. Affected versionversion=a36a7fecfe6071732075ad5aa31196adce13181b <5b6165d7ec38477e8cfa41bfa464959957953822
  4. Affected versionversion=a36a7fecfe6071732075ad5aa31196adce13181b <8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9
  5. Affected versionversion=a36a7fecfe6071732075ad5aa31196adce13181b <956ca5d72c76504824c8eb601879da9476973e15

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=4.8; version=a36a7fecfe6071732075ad5aa31196adce13181b <10f675902a5fc88ccfe34bb8aa37de50806b03b1; version=a36a7fecfe6071732075ad5aa31196adce13181b <5b6165d7ec38477e8cfa41bfa464959957953822; version=a36a7fecfe6071732075ad5aa31196adce13181b <8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9; version=a36a7fecfe6071732075ad5aa31196adce13181b <956ca5d72c76504824c8eb601879da9476973e15

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo