Skip to content

Every fix version that moved

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

28 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes of "Fix version moved" from 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.
Fri 7 Aug 2026· 4 record changes
2026-08-07CVE-2026-68480
linuxlinux
stated at publication 5.10.263, now states 5.10.264Release branch starts at 5.10.*.same dayDays to revision 1
2026-08-07CVE-2026-68480
linuxlinux
stated at publication 5.15.214, now states 5.15.215Release branch starts at 5.15.*.same dayDays to revision 1
2026-08-07CVE-2026-68480
linuxlinux
stated at publication 6.1.181, now states 6.1.182Release branch starts at 6.1.*.same dayDays to revision 1
2026-08-07CVE-2026-68480
linuxlinux
stated at publication 6.6.149, now states 6.6.150Release branch starts at 6.6.*.same dayDays to revision 1
Fri 19 Jun 2026· 4 record changes
2026-06-19CVE-2026-43064
linuxlinux
stated at publication 6.1.168, now states 6.1.176Release branch starts at 6.1.*.Original value first replaced 2026-06-01; this value first seen 2026-06-19.Days to revision 27
2026-06-19CVE-2026-45852
linuxlinux
stated at publication 5.10.252, now states 5.10.259Release branch starts at 5.10.*.Days to revision 23
2026-06-19CVE-2026-45852
linuxlinux
stated at publication 5.15.202, now states 5.15.210Release branch starts at 5.15.*.Days to revision 23
2026-06-19CVE-2026-45852
linuxlinux
stated at publication 6.1.165, now states 6.1.176Release branch starts at 6.1.*.Days to revision 23
Mon 4 May 2026· 1 record change
2026-05-04CVE-2026-23112
linuxlinux
stated at publication 5.10.250, now states 5.10.253Release branch starts at 5.10.*.Days to revision 80
Fri 3 Apr 2026· 6 record changes
2026-04-03CVE-2025-40219
linuxlinux
stated at publication 5.10.246, now states 5.10.252Release branch starts at 5.10.*.Days to revision 120
2026-04-03CVE-2025-40219
linuxlinux
stated at publication 5.15.195, now states 5.15.202Release branch starts at 5.15.*.Days to revision 120
2026-04-03CVE-2025-40219
linuxlinux
stated at publication 6.1.157, now states 6.1.165Release branch starts at 6.1.*.Days to revision 120
2026-04-03CVE-2025-40219
linuxlinux
stated at publication 6.12.54, now states 6.12.75Release branch starts at 6.12.*.Days to revision 120
2026-04-03CVE-2025-40219
linuxlinux
stated at publication 6.6.113, now states 6.6.128Release branch starts at 6.6.*.Days to revision 120
2026-04-03CVE-2025-40219
linuxlinux
stated at publication 6.18, now states 6.18.16Release branch starts at *.not dated
Thu 2 Oct 2025· 7 record changes
2025-10-02CVE-2025-38709
linuxlinux
stated at publication 6.6.103, now states 6.6.109Release branch starts at 6.6.*.Original value first replaced 2025-09-25; this value first seen 2025-10-02.Days to revision 21
2025-10-02CVE-2023-53431
linuxlinux
stated at publication 4.19.276, now states 4.19.281Release branch starts at 4.19.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02.Days to revision 13
2025-10-02CVE-2023-53431
linuxlinux
stated at publication 5.10.173, now states 5.10.178Release branch starts at 5.10.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02.Days to revision 13
2025-10-02CVE-2023-53431
linuxlinux
stated at publication 5.15.99, now states 5.15.108Release branch starts at 5.15.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02.Days to revision 13
2025-10-02CVE-2023-53431
linuxlinux
stated at publication 5.4.235, now states 5.4.241Release branch starts at 5.4.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02.Days to revision 13
2025-10-02CVE-2023-53431
linuxlinux
stated at publication 6.1.16, now states 6.1.25Release branch starts at 6.1.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02.Days to revision 13
2025-10-02CVE-2023-53431
linuxlinux
stated at publication 6.2.3, now states 6.2.12Release branch starts at 6.2.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02.Days to revision 13
Fri 25 Apr 2025· 3 record changes
2025-04-25CVE-2025-22077
linuxlinux
stated at publication 6.12.23, now states 6.12.25Release branch starts at 6.12.*.Original value first replaced 2025-04-22; this value first seen 2025-04-25.Days to revision 6
2025-04-25CVE-2025-22077
linuxlinux
stated at publication 6.14.2, now states 6.14.4Release branch starts at 6.14.*.Original value first replaced 2025-04-22; this value first seen 2025-04-25.Days to revision 6
2025-04-25CVE-2025-22077
linuxlinux
stated at publication 6.6.87, now states 6.6.88Release branch starts at 6.6.*.Original value first replaced 2025-04-22; this value first seen 2025-04-25.Days to revision 6
Fri 24 Jan 2025· 2 record changes
2025-01-24CVE-2024-26885
linuxlinux
stated at publication 5.10.214, now states 5.10.227Release branch starts at 5.10.*.Days to revision 282
2025-01-24CVE-2025-21654
linuxlinux
stated at publication 6.6.72, now states 6.6.74Release branch starts at 6.6.*.Days to revision 5
Wed 28 Jun 2023· 1 record change
2023-06-28CVE-2023-3389
linuxkernel
Google
stated at publication 6.0, now states 6.4Release branch starts at 0.same dayDays to revision 0

This kind is counted once per record, product and release branch, so one record that moved the boundary on four branches counts four times and the number of records behind these changes is smaller. 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.

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 03:47 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 →