CVE-2026-68480 — x86/bugs: Make Safe-RET robust against interrupt injection
In the Linux kernel, the following vulnerability has been resolved: x86/bugs: Make Safe-RET robust against interrupt injection An attacker injecting interrupts while the Safe-RET mitigation executes on machines affected by SRSO can neutralize the safe return sequence, potentially leading to data leakage through speculative execution. Fixup register state as if the Safe-RET sequence executed successfully by "emulating" it, in a manner of speaking, and avoid executing a RET instruction after returning from the interrupt.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 3f9b7101bea1dcb63410c016ceb266f6e9f733c9 and < dfefa3c51370f84acb643cddf98bb42c885d0483≥ b35087763a44d1eb45857f799579a351332be505 and < 52db77a13be224e09eb4ba6b4252ae8ab9085c2c≥ ac41e90d8daa8815d8bee774a1975435fbfe1ae7 and < d0208e08d64d99383e09852a76cc3038c5a4c3ab≥ fb3bd914b3ec28f5fb697ac55c4846ac2d542855 and < 6703dba1d14cbd6647cd1ccfa3a3fa94b64dd096≥ fb3bd914b3ec28f5fb697ac55c4846ac2d542855 and < e262f28a69ae9e0791248f93b0173c1d1f3e1d5d≥ fb3bd914b3ec28f5fb697ac55c4846ac2d542855 and < bfe7f9993467ba431b2731437949ac1e2634e771≥ fb3bd914b3ec28f5fb697ac55c4846ac2d542855 and < 61649a2d61cb0dbc673f0f232f0f0c298bf50442≥ fb3bd914b3ec28f5fb697ac55c4846ac2d542855 and < 7e7f81cf6f5ca3311e526308f55d7c54d3ba71f9 and 6 moreversion acdc883eb61efbe01b954e782e1124790bd391a8≥ 5.10.189 and < 5.10.264≥ 5.15.125 and < 5.15.215≥ 6.1.44 and < 6.1.182≥ 6.4.9 and < 6.5version 6.5 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 30, 2026 · 15 reading(s) · max 0.23%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
9 on the record
- git.kernel.org/stable/c/e262f28a69ae9e0791248f93b0173c1d1f3e1d5d
- git.kernel.org/stable/c/61649a2d61cb0dbc673f0f232f0f0c298bf50442
- people.csail.mit.edu/mengjia/data/2026.USENIX.TONTOU.pdf
- git.kernel.org/stable/c/52db77a13be224e09eb4ba6b4252ae8ab9085c2c
- git.kernel.org/stable/c/6703dba1d14cbd6647cd1ccfa3a3fa94b64dd096
- git.kernel.org/stable/c/dfefa3c51370f84acb643cddf98bb42c885d0483
- git.kernel.org/stable/c/7e7f81cf6f5ca3311e526308f55d7c54d3ba71f9
- git.kernel.org/stable/c/bfe7f9993467ba431b2731437949ac1e2634e771
- git.kernel.org/stable/c/d0208e08d64d99383e09852a76cc3038c5a4c3ab
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 3d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 3d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 3d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 3d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 3d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-68480 is "x86/bugs: Make Safe-RET robust against interrupt injection", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.23% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.