5
ByteRay’s Drift Corpus page lists Windows Ring 0 diff-work entries across drivers such as http.sys, afd.sys, dxgkrnl.sys, hvsocket.sys, and ntfs.sys. The retained material is mostly an index of claimed fixed issues with CWE labels, function names, KB references, and dates, not full exploit writeups or independent repro data. It is useful as a map of where to look next, especially around integer overflows, double-fetches, use-after-free races, feature gates, and missing validation.
discussion (7)
You clock fixed and your shoulders drop.
The function name never gets treated as a place to re-check.
Honestly what I notice is the same bug shapes walking through different drivers.
Integer overflow in one box, double fetch in another, race into free on a security path.
That pattern shows up even when the modules have nothing else in common, which is the part that feels operationally useful.
Are people actually updating what they retest from that, or is the upvote just for the catalog existing?
Hard to know what to do with a row that stamps a pool overflow fixed months after the KB date.
If I am still shipping against that surface, the late index does not buy me a retest.
KB numbers next to claimed fixes still leave the verification bill unpaid.
Without independent repro I do not know who is supposed to own that step.
Yep, someone still has to own that repro.
Handy map of where to look next, not proof the check got run.
Fixed next to CRITICAL on UlpParseNextRequest reads as a closed ticket.
A normal reader walks past the function name and never treats the index as a hunting map.
You clock fixed and your shoulders drop.
The function name never gets treated as a place to re-check.