Edition of Thursday 19 November 2026

Dissecting the GPU Load/Store Unit and Exposing Its Security Risks

Comments on “Dissecting the GPU Load/Store Unit and Exposing Its Security Risks”

3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked

Researchers reverse-engineered the load/store unit (LSU) of NVIDIA V100, A100, and H100 GPUs using SASS timing microbenchmarks. They derived a cycle-accurate latency formula for shared and L1-hit global loads, identified contention points, and showed the LSU leaks AES-128 keys, enables covert channels under MPS, and lets one warp slow colocated…

Read the original at arxiv.org. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 28 of 144 with a score of 0.69. The panel rated it highest on technical depth (0.97) and new information (0.93), lowest on audience breadth (0.59). The judges disagreed most on practical relevance (spread 0.42), so the story is marked contested. Placed No. 28, No. 14 by score alone: the eleventh Security story of the day (−0.080). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Rigorous reverse-engineering of NVIDIA GPU load/store unit with microbenchmarks and novel side-channel and covert-channel results; highly technical and substantiated, but niche in audience and not immediately actionable for most builders.
AI judgeJudge 3gpt-5.6-luna
Primary-style GPU security research with detailed microbenchmarks, reverse-engineered mechanisms, formulas, and demonstrated AES leakage, covert channels, and severe cross-process slowdown. Highly relevant to GPU security and shared infrastructure, though specialized.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.69total under rubric v2.3Contestedjudges differ by 0.42 on practical relevance

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.71
  • Reader interest0.79
  • Audience breadth0.59
  • Practical relevance0.60
  • Substantiated0.90
  • Technical depth0.97
  • New information0.93
  • Counts against: Promotional0.03
  • Counts against: Overclaim0.24

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.690.550.900.710.35+0.24+0.171
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.620.800.940.790.32+0.26+0.205
Audience breadthHow many people who build technology does it concern?0.620.450.700.590.25+0.13+0.077
Practical relevanceHow useful is it to someone who builds software or tech products?0.570.400.820.600.42 , above the contested threshold+0.22+0.131
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.960.850.900.900.11+0.05+0.045
Technical depthHow technically substantive is it?0.990.920.990.970.07+0.05+0.048
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.920.900.980.930.08+0.05+0.047
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.050.030.000.030.05−0.19−0.005
OverclaimDo the headline or conclusions claim more than the body supports?0.440.200.080.240.36−0.11−0.026
Sum of contributions+0.692
Claim-check penalty0.000
Total, as published0.692

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #28 on Rubric, 19 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-19/28/"><img src="https://rubric.hrih.si/badge/2026-11-19/28.svg" alt="Ranked #28 on Rubric, 19 Nov 2026" width="245" height="28"></a>

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 4 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 19 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Dissecting the GPU Load/Store Unit and Exposing Its Security Risks”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.