Skip to content

Record state changed

What a record said when it was published, what it says now, and the commit that changed it.

7 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows

Showing changes seen on 2026-01-05. Every day

Counted changes of "Record state changed" published by Linux, changed on 2026-01-05, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.Record, Which record was edited, by its CVE id, or how many records one collapsed line stands on.Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry.What changedDays to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong.
Mon 5 Jan 2026· 7 record changes
2026-01-053 commits
whole record
Linux
stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row.Days to revision 12 to 585
2026-01-05CVE-2024-44972same vendor as the line abovesame change as the line aboveDays to revision 488
2026-01-05CVE-2024-47672same vendor as the line abovesame change as the line aboveDays to revision 453
2026-01-05CVE-2024-56781same vendor as the line abovesame change as the line aboveDays to revision 362
2026-01-05CVE-2023-53183same vendor as the line abovesame change as the line aboveDays to revision 112
2026-01-05CVE-2023-54029same vendor as the line abovesame change as the line aboveDays to revision 12
2026-01-05CVE-2024-36923same vendor as the line abovesame change as the line aboveDays to revision 585
2026-01-05CVE-2023-53779same vendor as the line abovesame change as the line aboveDays to revision 27

This kind is counted once per CVE record, so changes and records are the same number here. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
3,898 records with a counted edit in the 52 weeks to 7 Sep 2026 · snapshot built 12:43 UTC · scroll for earlierfewermore

Data sources and quality

Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.

A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.

The units, the refusals, the cut-offs and every source, in full →

Check my CVEs against these changes →