Local kernel memory corruption via stale taprio entry
Published Jun 24, 2026 · Updated Jun 24, 2026
Use-after-free in affected Linux Kernel branches starting at 5.2 allows local users to corrupt kernel memory during a taprio schedule switch. In advance_sched(), switch_schedules() queues the old operational schedule for RCU freeing but leaves next pointing to its entry, which is then written through and assigned as q->current_entry. The attack is local, requires low privileges and a configured taprio schedule transition, and can compromise kernel memory without user interaction.
Summary
What happened
Use-after-free in affected Linux Kernel branches starting at 5.2 allows local users to corrupt kernel memory during a taprio schedule switch. In advance_sched(), switch_schedules() queues the old operational schedule for RCU freeing but leaves next pointing to its entry, which is then written through and assigned as q->current_entry. The attack is local, requires low privileges and a configured taprio schedule transition, and can compromise kernel memory without user interaction.
The record
- CVE
- CVE-2026-53011
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 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.
- Affected versionversion=5.2
- Affected versionversion=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <0e62171df8ed4804d00db088f17eed06468233fa
- Affected versionversion=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <105425b1969c5affe532713cfac1c0b320d7ac2b
- Affected versionversion=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <1bd286fa3e21200133478ed523cc6a2788baf38a
- Affected versionversion=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <3471874578160a28c171a607fa069f24062634b8
- Affected versionversion=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <7256996e1ef553716817f3bfd077c2f3b48b582f
- Affected versionversion=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <a8fc396519ef4f081bc545e88f61241728bb78d7
- Affected versionversion=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <b73235da5dde77ed1264f9767b62c28c9d71fd78
- Affected versionversion=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <eee072fe16c646190d33ae69c9983d8de1562bf8
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