FNFnoord·Dec 31, 2025Submission
35 points · Open discussionThijsRay
l1tf_reloaded
C2025–2025
ThijsRay / l1tf_reloaded
l1tf_reloaded
Read physical memory from other virtual machines using CPU vulnerabilities
2Distinct people
2Mentions
0Explicit recommenders
62GitHub stars
What to know before exploring
What it is
Read physical memory from other virtual machines using CPU vulnerabilities
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week2 dated mentions
Observed mentions: 2025-09-19 17:16:37 UTC to 2025-12-31 02:33:50 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Sep 15 | 2025-09-15 00:00:00 UTC | 2025-09-22 00:00:00 UTC | 1 | 0 | 1 |
| Sep 22 | 2025-09-22 00:00:00 UTC | 2025-09-29 00:00:00 UTC | 0 | 0 | 0 |
| Sep 29 | 2025-09-29 00:00:00 UTC | 2025-10-06 00:00:00 UTC | 0 | 0 | 0 |
| Oct 6 | 2025-10-06 00:00:00 UTC | 2025-10-13 00:00:00 UTC | 0 | 0 | 0 |
| Oct 13 | 2025-10-13 00:00:00 UTC | 2025-10-20 00:00:00 UTC | 0 | 0 | 0 |
| Oct 20 | 2025-10-20 00:00:00 UTC | 2025-10-27 00:00:00 UTC | 0 | 0 | 0 |
| Oct 27 | 2025-10-27 00:00:00 UTC | 2025-11-03 00:00:00 UTC | 0 | 0 | 0 |
| Nov 3 | 2025-11-03 00:00:00 UTC | 2025-11-10 00:00:00 UTC | 0 | 0 | 0 |
| Nov 10 | 2025-11-10 00:00:00 UTC | 2025-11-17 00:00:00 UTC | 0 | 0 | 0 |
| Nov 17 | 2025-11-17 00:00:00 UTC | 2025-11-24 00:00:00 UTC | 0 | 0 | 0 |
| Nov 24 | 2025-11-24 00:00:00 UTC | 2025-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 1 | 2025-12-01 00:00:00 UTC | 2025-12-08 00:00:00 UTC | 0 | 0 | 0 |
| Dec 8 | 2025-12-08 00:00:00 UTC | 2025-12-15 00:00:00 UTC | 0 | 0 | 0 |
| Dec 15 | 2025-12-15 00:00:00 UTC | 2025-12-22 00:00:00 UTC | 0 | 0 | 0 |
| Dec 22 | 2025-12-22 00:00:00 UTC | 2025-12-29 00:00:00 UTC | 0 | 0 | 0 |
| Dec 29 | 2025-12-29 00:00:00 UTC | 2026-01-05 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
2 sourcesThis is a project that we've been working in collaboration with Google and AWS. We present a vulnerability that allows a malicious virtual machine to leak all physical memory of its host, including the memory of other virtual machines running on the system. L1TF Reloaded combines two long-known transient execution vulnerabilities, L1TF and (Half-)Spectre. By combining them, commonly deployed software-based mitigations against L1TF, such as L1d flushing and core scheduling, can be circumvented.
We've demonstrated our attack on real-world KVM-based cloud solutions. Both Google Cloud [1] and AWS [2] wrote a blog post in response to this attack, where they describe how they mitigate against L1TF Reloaded and how they harden their systems against unknown transient execution attacks. Google also decided to award us a bug bounty of $151,515, the
Read the rest
highest bounty of their Cloud VRP yet.
PoC is available at https://github.com/ThijsRay/l1tf_reloaded
[1] this submission
[2] https://aws.amazon.com/blogs/security/ec2-defenses-against-l...