CPU hang via stale ring-buffer entry counts
Published Oct 7, 2025 · Updated Oct 7, 2025
Denial of service in Linux kernel 3.6 through affected 6.4 releases allows local users to hang a CPU by reading trace_pipe. The rb_reset_cpu function leaves stale page entry counts; after ring-buffer reduction, rb_remove_pages adds them to the overrun count, so tracing_read_pipe repeatedly finds a nonempty buffer but retrieves no entry. Access to kernel tracing is required, and the resulting busy loop consumes a CPU while the trace_pipe read never completes.
Summary
What happened
Denial of service in Linux kernel 3.6 through affected 6.4 releases allows local users to hang a CPU by reading trace_pipe. The rb_reset_cpu function leaves stale page entry counts; after ring-buffer reduction, rb_remove_pages adds them to the overrun count, so tracing_read_pipe repeatedly finds a nonempty buffer but retrieves no entry. Access to kernel tracing is required, and the resulting busy loop consumes a CPU while the trace_pipe read never completes.
The record
- CVE
- CVE-2023-53668
- Published
- Oct 7, 2025
- Updated
- Oct 7, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-833, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 7, 2025CVE publishedPublication date reported by the CVE source.
- Oct 7, 2025Record 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.
- Affected versionversion=3.6
- Affected versionversion=a5fb833172eca69136e9ee1ada778e404086ab8a <0a29dae5786d263016a9aceb1e56bf3fd4cc6fa0
- Affected versionversion=a5fb833172eca69136e9ee1ada778e404086ab8a <27bdd93e44cc28dd9b94893fae146b83d4f5b31e
- Affected versionversion=a5fb833172eca69136e9ee1ada778e404086ab8a <5e68f1f3a20fe9b6bde018e353269fbfa289609c
- Affected versionversion=a5fb833172eca69136e9ee1ada778e404086ab8a <7e42907f3a7b4ce3a2d1757f6d78336984daf8f5
- Affected versionversion=a5fb833172eca69136e9ee1ada778e404086ab8a <8b0b63fdac6b70a45614e7d4b30e5bbb93deb007
- Affected versionversion=a5fb833172eca69136e9ee1ada778e404086ab8a <a55e8a3596048c2f7b574049aeb1885b5abba1cc
- Affected versionversion=a5fb833172eca69136e9ee1ada778e404086ab8a <bb14a93bccc92766b1d9302c6bcbea17d4bce306
- Affected versionversion=a5fb833172eca69136e9ee1ada778e404086ab8a <e84829522fc72bb43556b31575731de0440ac0dd
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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