CVE-2024-57979

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-02-27. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week

Also known asEUVD-2025-5270 (ENISA EUVD) · GHSA-579q-3q2m-34fw (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

pps: Fix a use-after-free

On a board running ntpd and gpsd, I'm seeing a consistent use-after-free in sys_exit() from gpsd when rebooting:

pps pps1: removed ------------[ cut here ]------------ kobject: '(null)' (00000000db4bec24): is not initialized, yet kobject_put() is being called. WARNING: CPU: 2 PID: 440 at lib/kobject.c:734 kobject_put+0x120/0x150 CPU: 2 UID: 299 PID: 440 Comm: gpsd Not tainted 6.11.0-rc6-00308-gb31c44928842 #1 Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : kobject_put+0x120/0x150 lr : kobject_put+0x120/0x150 sp : ffffffc0803d3ae0 x29: ffffffc0803d3ae0 x28: ffffff8042dc9738 x27: 0000000000000001 x26: 0000000000000000 x25: ffffff8042dc9040 x24: ffffff8042dc9440 x23: ffffff80402a4620 x22: ffffff8042ef4bd0 x21: ffffff80405cb600 x20: 000000000008001b x19: ffffff8040b3b6e0 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 696e6920746f6e20 x14: 7369203a29343263 x13: 205d303434542020 x12: 0000000000000000 x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000 x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000 Call trace: kobject_put+0x120/0x150 cdev_put+0x20/0x3c __fput+0x2c4/0x2d8 ____fput+0x1c/0x38 task_work_run+0x70/0xfc do_exit+0x2a0/0x924 do_group_exit+0x34/0x90 get_signal+0x7fc/0x8c0 do_signal+0x128/0x13b4 do_notify_resume+0xdc/0x160 el0_svc+0xd4/0xf8 el0t_64_sync_handler+0x140/0x14c el0t_64_sync+0x190/0x194 ---[ end trace 0000000000000000 ]---

...followed by more symptoms of corruption, with similar stacks:

refcount_t: underflow; use-after-free. kernel BUG at lib/list_debug.c:62! Kernel panic - not syncing: Oops - BUG: Fatal exception

This happens because pps_device_destruct() frees the pps_device with the embedded cdev immediately after calling cdev_del(), but, as the comment above cdev_del() notes, fops for previously opened cdevs are still callable even after cdev_del() returns. I think this bug has always been there: I can't explain why it suddenly started happening every time I reboot this particular board.

In commit d953e0e837e6 ("pps: Fix a use-after free bug when unregistering a source."), George Spelvin suggested removing the embedded cdev. That seems like the simplest way to fix this, so I've implemented his suggestion, using __register_chrdev() with pps_idr becoming the source of truth for which minor corresponds to which device.

But now that pps_idr defines userspace visibility instead of cdev_add(), we need to be sure the pps->dev refcount can't reach zero while userspace can still find it again. So, the idr_remove() call moves to pps_unregister_cdev(), and pps_idr now holds a reference to pps->dev.

pps_core: source serial1 got cdev (251:1) <...> pps pps1: removed pps_core: unregistering pps1 pps_core: deallocating pps1

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 27, 2025

Last Modified

October 15, 2026

Advisory Details (10)

Auto-updated Jul 14, 2026
Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4178-1] linux security update

https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4102-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/03/msg00028.html
Web page

pps: Fix a use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cd3bbcb6b3a7caa5ce67de76723b6d8531fb7f64
Web page

pps: Fix a use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c79a39dc8d060b9e64e8b0fa9d245d44befeefbe
Web page

pps: Fix a use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c4041b6b0a7a3def8cf3f3d6120ff337bc4c40f7
Web page

pps: Fix a use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/91932db1d96b2952299ce30c1c693d834d10ace6
Web page

pps: Fix a use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/85241f7de216f8298f6e48540ea13d7dcd100870
Web page

pps: Fix a use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7e5ee3281dc09014367f5112b6d566ba36ea2d49
Web page

pps: Fix a use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/785c78ed0d39d1717cca3ef931d3e51337b5e90e
Web page

pps: Fix a use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1a7735ab2cb9747518a7416fb5929e85442dec62

Vendor Advisories for CVE-2024-57979(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-raspi-6.8 (6.8.0-1031.35) @ noble2026-10-28ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2026.27) @ noble2026-10-28ubuntu
ubuntulinux-tools-gcp-lts-24.04 (6.8.0-1033.35) @ noble2026-10-28ubuntu
ubuntulinux-tools-fips (5.15.0.140.80) @ jammy2026-10-28ubuntu
ubuntulinux-tools-gcp-lts-22.04 (5.15.0.1083.79) @ jammy2026-10-28ubuntu
ubuntulinux-tools-gcp-fips (5.15.0.1083.73) @ jammy2026-10-28ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1083.92~20.04.1) @ focal2026-10-28ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.216.208) @ focal2026-10-28ubuntu
ubuntulinux-tools-gcp-fips (5.4.0.1149.91) @ focal2026-10-28ubuntu
ubuntulinux-tools-azure-fips (5.4.0.1151.88) @ focal2026-10-28ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1029.30) @ noble2026-10-28ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-64.67.1) @ noble2026-10-28ubuntu
ubuntulinux-tools-azure-nvidia-lts-24.04 (6.8.0-1022.23) @ noble2026-10-28ubuntu
ubuntulinux-tools-aws-fips (5.15.0.1084.80) @ jammy2026-10-28ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1081.87~20.04.1) @ focal2026-10-28ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-26.26) @ oracular2026-10-28ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1037.37) @ jammy2026-10-28ubuntu
ubuntulinux-tools-realtime (5.15.0.1084.88) @ jammy2026-10-28ubuntu
ubuntulinux-tools-azure-fips (5.15.0.1089.74) @ jammy2026-10-28ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1081.80) @ jammy2026-10-28ubuntu
ubuntulinux-tools-kvm (5.4.0.1133.129) @ focal2026-10-28ubuntu
ubuntulinux-tools-oracle-edge (5.4.0.1144.154~18.04.1) @ bionic2026-10-28ubuntu
ubuntulinux-tools-ibm-edge (5.4.0.1092.97~18.04.1) @ bionic2026-10-28ubuntu
ubuntulinux-tools-aws (6.11.0-1014.15) @ oracular2026-10-28ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.216.236~18.04.1) @ bionic2026-10-28ubuntu
ubuntulinux-tools-ibm-lts-20.04 (5.4.0.1092.121) @ focal2026-10-28ubuntu
ubuntulinux-tools-bluefield (5.4.0.1105.101) @ focal2026-10-28ubuntu
ubuntulinux-tools-oracle-64k (6.11.0-1016.17) @ oracular2026-10-28ubuntu
redhatkernel-0:4.18.0-553.44.1.el8_102025-03-10redhat
redhatkernel-rt-0:4.18.0-553.44.1.rt7.385.el8_102025-03-10redhat
linuxKernel @ 5.4.291 (fixes >=3.9.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (45 versions)
  • every version up to 5.10.237-1: fixed in 5.10.237-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.128-1~deb11u1 (6 versions)
  • every version up to 6.1.129-1~deb11u1: fixed in 6.1.129-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (35 versions)
  • every version up to 6.1.129-1: fixed in 6.1.129-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.13-1: fixed in 6.12.13-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.13-1: fixed in 6.12.13-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(22)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 243 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 148 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:41 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  5. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-10-28 23:42 UTCEG score recompute
  7. 2026-10-28 23:42 UTCVendor advisory
  8. 2026-10-28 23:41 UTCGHSA enrichmentGHSA-579q-3q2m-34fw · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  11. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  12. 2026-10-25 16:54 UTCEG score recompute
  13. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  14. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-10-21 22:11 UTCEG score recompute
  18. 2026-10-21 22:11 UTCVendor advisory
  19. 2026-10-21 22:10 UTCGHSA enrichmentGHSA-579q-3q2m-34fw · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  23. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-10-18 05:57 UTCEG score recompute
  25. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
Show 70 more
  1. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  3. 2026-10-15 02:41 UTCEG score recompute
  4. 2026-10-15 02:41 UTCVendor advisory
  5. 2026-10-15 02:40 UTCGHSA enrichmentGHSA-579q-3q2m-34fw · GitHub severity HIGH · GitHub CVSS 7.8
  6. 2026-10-15 01:46 UTCEG score recompute
  7. 2026-10-15 01:46 UTCVendor advisory
  8. 2026-10-15 01:45 UTCGHSA enrichmentGHSA-579q-3q2m-34fw · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  10. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-10-12 17:36 UTCEG score recompute
  12. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-10-11 21:02 UTCEG score recompute
  14. 2026-10-11 15:54 UTCEG score recompute
  15. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  16. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  17. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  18. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  19. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  20. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  21. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  22. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  23. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  24. 2026-10-02 16:26 UTCEG score recompute
  25. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  26. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  27. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  28. 2026-09-28 02:02 UTCOSV refresh
  29. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  30. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  31. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  32. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  33. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  34. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  35. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  36. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  37. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  38. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  39. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  40. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  41. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  42. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  43. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  44. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  45. 2026-09-08 09:54 UTCEG score recompute
  46. 2026-09-08 09:54 UTCVendor advisory
  47. 2026-09-08 09:54 UTCGHSA enrichmentGHSA-579q-3q2m-34fw · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  49. 2026-09-07 13:17 UTCOSV refresh
  50. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  51. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  52. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  53. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  54. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  55. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  56. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  57. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  58. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  59. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  60. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  61. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  62. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  63. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  64. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  65. 2026-08-20 22:31 UTCOSV refresh
  66. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  67. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  68. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  69. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  70. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.3% · 17th percentile

Related CVEs(same vendor + same CWE)· as of October 31, 2026

Frequently asked(5)

What is CVE-2024-57979?
CVE-2024-57979 is a high-severity vulnerability; its CVE record was published on February 27, 2025. In the Linux kernel, the following vulnerability has been resolved: pps: Fix a use-after-free On a board running ntpd and gpsd, I'm seeing a consistent use-after-free in sys_exit() from gpsd when rebooting: pps pps1: removed ------------[ cut here ]------------ kobject: '(null)' (00000000db4bec24):…
When was the CVE record for CVE-2024-57979 published?
The CVE record for CVE-2024-57979 was published on February 27, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2024-57979 actively exploited?
CVE-2024-57979 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-57979?
CVE-2024-57979 has a CVSS v3.1 base score of 7.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2024-57979?
A fix for CVE-2024-57979 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-57979 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-57979

Explore →

Is Your Infrastructure Affected by CVE-2024-57979?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs