Kernel data disclosure via interruptible Safe-RET sequence
Published Aug 6, 2026 · Updated Aug 6, 2026
Speculative-execution flaw in Linux Safe-RET allows local users to read sensitive kernel data by injecting precisely timed interrupts. An interrupt between Safe-RET's CALL and RET destroys its protected predictor state, letting the resumed RET speculate through an attacker-trained target. The flaw requires affected AMD Zen hardware, local code execution, and the Safe-RET SRSO mitigation; successful abuse discloses kernel memory.
Summary
What happened
Speculative-execution flaw in Linux Safe-RET allows local users to read sensitive kernel data by injecting precisely timed interrupts. An interrupt between Safe-RET's CALL and RET destroys its protected predictor state, letting the resumed RET speculate through an attacker-trained target. The flaw requires affected AMD Zen hardware, local code execution, and the Safe-RET SRSO mitigation; successful abuse discloses kernel memory.
The record
- CVE
- CVE-2026-68480
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-201, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 6, 2026CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=0 <5.10.263
- Affected versionversion=0 <5.15.214
- Affected versionversion=0 <6.1.181
- Affected versionversion=0 <6.18.43
- Affected versionversion=0 <6.6.149
- Affected versionversion=0 <7.1.7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <608c8f5dccaaf8b8d2b28c0fbdd439d144be62b0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <61649a2d61cb0dbc673f0f232f0f0c298bf50442
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <95b08cdd603fe79d2e9d5212fbb13d577c835f4f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9c0b8105e919be5208c81d5516a194a28c58fe1e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9de1a49e8f1fbf7c372902573a27a97d4ab4d0af
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bfe7f9993467ba431b2731437949ac1e2634e771
What conditions does exploitation require?
What is affected?
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
- TONTOU Safe-RET end-to-end exploitfunctional · demonstrated
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