Local kernel panic via tracing buffer race
Published Sep 17, 2025 · Updated Sep 17, 2025
Race condition in the Linux kernel tracing subsystem allows local users to trigger a kernel warning through concurrent per-CPU snapshots. The ring_buffer_swap_cpu path replaces buffer->buffers[cpu] while an event writer retains the old cpu_buffer, so rb_commit checks the wrong committing state. Low-privileged local access to the tracing snapshot interface and a successful race are required; the warning becomes a system panic when panic_on_warn is enabled.
Summary
What happened
Race condition in the Linux kernel tracing subsystem allows local users to trigger a kernel warning through concurrent per-CPU snapshots. The ring_buffer_swap_cpu path replaces buffer->buffers[cpu] while an event writer retains the old cpu_buffer, so rb_commit checks the wrong committing state. Low-privileged local access to the tracing snapshot interface and a successful race are required; the warning becomes a system panic when panic_on_warn is enabled.
The record
- CVE
- CVE-2023-53368
- Published
- Sep 17, 2025
- Updated
- Sep 17, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2025CVE publishedPublication date reported by the CVE source.
- Sep 17, 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.10
- Affected versionversion=f1affcaaa861f27752a769f889bf1486ebd301fe <3163f635b20e9e1fb4659e74f47918c9dddfe64e
- Affected versionversion=f1affcaaa861f27752a769f889bf1486ebd301fe <37ca1b686078b00cc4ffa008e2190615f7709b5d
- Affected versionversion=f1affcaaa861f27752a769f889bf1486ebd301fe <6182318ac04648b46db9d441fd7d696337fcdd0b
- Affected versionversion=f1affcaaa861f27752a769f889bf1486ebd301fe <74c85396bd73eca80b96510b4edf93b9a3aff75f
- Affected versionversion=f1affcaaa861f27752a769f889bf1486ebd301fe <89c89da92a60028013f9539be0dcce7e44405a43
- Affected versionversion=f1affcaaa861f27752a769f889bf1486ebd301fe <90e037cabc2c2dfc39b3dd9c5b22ea91f995539a
- Affected versionversion=f1affcaaa861f27752a769f889bf1486ebd301fe <c5d30d6aa83d99fba8dfdd9cf6c4e4e7a63244db
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.
Weakness, pattern, technique
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