Skip to content

Record state changed

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

233 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes of "Record state changed" published by Linux, 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.
Wed 27 Mar 2024· 1 change
2024-03-27CVE-2024-26624
whole record
Linux
stated at publication PUBLISHED, now states REJECTEDTime to revision 21 days
Wed 20 Mar 2024· 1 change
2024-03-20CVE-2024-26628
whole record
Linux
stated at publication PUBLISHED, now states REJECTEDTime to revision 14 days
Mon 18 Mar 2024· 1 change
2024-03-18CVE-2023-52605
whole record
Linux
stated at publication PUBLISHED, now states REJECTEDTime to revision 12 days
Tue 12 Mar 2024· 2 changes
2024-03-122 commits
whole record
Linux
stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row.Time to revision 12 days
2024-03-12CVE-2024-26609same vendor as the line abovesame change as the line aboveTime to revision 12 days
2024-03-12CVE-2024-26613same vendor as the line abovesame change as the line aboveTime to revision 12 days
Mon 11 Mar 2024· 1 change
2024-03-11CVE-2023-52514
whole record
Linux
stated at publication PUBLISHED, now states REJECTEDTime to revision 9 days
Fri 8 Mar 2024· 1 change
2024-03-08CVE-2023-52496
whole record
Linux
stated at publication PUBLISHED, now states REJECTEDTime to revision 8 days
Thu 7 Mar 2024· 1 change
2024-03-07CVE-2023-52592
whole record
Linux
stated at publication PUBLISHED, now states REJECTEDTime to revision 2 days
Tue 5 Mar 2024· 1 change
2024-03-05CVE-2023-52521
whole record
Linux
stated at publication PUBLISHED, now states REJECTEDTime to revision 3 days
Mon 4 Mar 2024· 1 change
2024-03-04CVE-2023-52579
whole record
Linux
stated at publication PUBLISHED, now states REJECTEDTime to revision 2 days
Sun 3 Mar 2024· 1 change
2024-03-03CVE-2023-52466
whole record
Linux
stated at publication PUBLISHED, now states REJECTEDTime to revision 7 days
Thu 22 Feb 2024· 1 change
2024-02-22CVE-2023-52437
whole record
Linux
stated at publication PUBLISHED, now states REJECTEDTime to revision 2 days

This kind is counted once per CVE record, so changes and records are the same number here. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

What this page cannot see

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 →

Paste your closed CVE tickets and see which of these changes hit them →