CVE-2026-63977

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

dpll: zl3073x: use __dpll_device_change_ntf() and remove change_work

The change_work was introduced to send device change notifications from DPLL device callbacks without deadlocking on dpll_lock, since the callbacks are already invoked under that lock. Now that __dpll_device_change_ntf() is exported for callers that already hold dpll_lock, use it directly and remove the change_work infrastructure entirely.

This eliminates a race condition where change_work could be re-scheduled after cancel_work_sync() during device teardown, potentially causing the handler to dereference a freed or NULL dpll_dev pointer.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

dpll: zl3073x: use __dpll_device_change_ntf() and remove change_work - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e7a33807fb3f87a855993474ac21684ce105927b
generic

dpll: zl3073x: use __dpll_device_change_ntf() and remove change_work - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d733f519f6443540f8359461a34e3b0042099bbe

Vendor Advisories for CVE-2026-63977(1)

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

Patch Availability(5)

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 27× in last 7d / 153× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 198 total refreshes for this CVE.

  1. 2026-08-30 02:54 UTCEG score recompute
  2. 2026-08-30 02:54 UTCVendor advisory
  3. 2026-08-30 02:54 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 21:23 UTCEG score recompute
  7. 2026-08-27 21:23 UTCVendor advisory
  8. 2026-08-27 21:23 UTCGHSA enrichment
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-27 03:33 UTCEG score recompute
  11. 2026-08-27 03:33 UTCGHSA enrichment
  12. 2026-08-26 14:46 UTCEPSS rescore
  13. 2026-08-26 14:20 UTCVendor advisory
  14. 2026-08-26 14:19 UTCGHSA enrichment
  15. 2026-08-26 00:52 UTCEG score recompute
  16. 2026-08-26 00:52 UTCVendor advisory
  17. 2026-08-26 00:51 UTCGHSA enrichment
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-25 11:30 UTCVendor advisory
  20. 2026-08-25 11:30 UTCGHSA enrichment
  21. 2026-08-24 22:17 UTCEG score recompute
  22. 2026-08-24 22:17 UTCVendor advisory
  23. 2026-08-24 22:17 UTCGHSA enrichment
  24. 2026-08-24 09:07 UTCVendor advisory
  25. 2026-08-24 09:07 UTCGHSA enrichment
Show 75 more
  1. 2026-08-23 19:41 UTCVendor advisory
  2. 2026-08-23 19:41 UTCGHSA enrichment
  3. 2026-08-23 06:31 UTCEG score recompute
  4. 2026-08-23 06:31 UTCVendor advisory
  5. 2026-08-23 06:31 UTCGHSA enrichment
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 17:18 UTCVendor advisory
  8. 2026-08-22 17:18 UTCGHSA enrichment
  9. 2026-08-22 03:53 UTCEG score recompute
  10. 2026-08-22 03:53 UTCVendor advisory
  11. 2026-08-22 03:53 UTCGHSA enrichment
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-21 14:42 UTCVendor advisory
  14. 2026-08-21 14:42 UTCGHSA enrichment
  15. 2026-08-21 01:31 UTCEG score recompute
  16. 2026-08-21 01:31 UTCVendor advisory
  17. 2026-08-21 01:31 UTCGHSA enrichment
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-20 12:20 UTCVendor advisory
  20. 2026-08-20 12:20 UTCGHSA enrichment
  21. 2026-08-19 23:09 UTCEG score recompute
  22. 2026-08-19 23:09 UTCVendor advisory
  23. 2026-08-19 23:09 UTCGHSA enrichment
  24. 2026-08-19 17:04 UTCEPSS rescore
  25. 2026-08-19 09:09 UTCVendor advisory
  26. 2026-08-19 09:09 UTCGHSA enrichment
  27. 2026-08-18 19:50 UTCEG score recompute
  28. 2026-08-18 19:50 UTCVendor advisory
  29. 2026-08-18 19:50 UTCGHSA enrichment
  30. 2026-08-18 13:48 UTCEPSS rescore
  31. 2026-08-18 04:26 UTCVendor advisory
  32. 2026-08-18 04:26 UTCGHSA enrichment
  33. 2026-08-17 15:15 UTCEG score recompute
  34. 2026-08-17 15:15 UTCVendor advisory
  35. 2026-08-17 15:15 UTCGHSA enrichment
  36. 2026-08-17 13:47 UTCEPSS rescore
  37. 2026-08-17 02:05 UTCEG score recompute
  38. 2026-08-17 02:05 UTCVendor advisory
  39. 2026-08-17 02:05 UTCGHSA enrichment
  40. 2026-08-16 14:56 UTCEPSS rescore
  41. 2026-08-16 12:54 UTCEG score recompute
  42. 2026-08-16 12:54 UTCVendor advisory
  43. 2026-08-16 12:54 UTCGHSA enrichment
  44. 2026-08-15 23:44 UTCVendor advisory
  45. 2026-08-15 23:44 UTCGHSA enrichment
  46. 2026-08-15 10:33 UTCEG score recompute
  47. 2026-08-15 10:33 UTCVendor advisory
  48. 2026-08-15 10:33 UTCGHSA enrichment
  49. 2026-08-15 01:30 UTCEPSS rescore
  50. 2026-08-14 21:22 UTCVendor advisory
  51. 2026-08-14 21:22 UTCGHSA enrichment
  52. 2026-08-14 08:12 UTCEG score recompute
  53. 2026-08-14 08:12 UTCVendor advisory
  54. 2026-08-14 08:12 UTCGHSA enrichment
  55. 2026-08-13 22:00 UTCEPSS rescore
  56. 2026-08-13 19:01 UTCVendor advisory
  57. 2026-08-13 19:01 UTCGHSA enrichment
  58. 2026-08-13 05:51 UTCVendor advisory
  59. 2026-08-13 05:51 UTCGHSA enrichment
  60. 2026-08-12 16:40 UTCEG score recompute
  61. 2026-08-12 16:40 UTCVendor advisory
  62. 2026-08-12 16:40 UTCGHSA enrichment
  63. 2026-08-12 13:51 UTCEPSS rescore
  64. 2026-08-12 03:30 UTCVendor advisory
  65. 2026-08-12 03:30 UTCGHSA enrichment
  66. 2026-08-11 14:19 UTCEG score recompute
  67. 2026-08-11 14:19 UTCVendor advisory
  68. 2026-08-11 14:19 UTCGHSA enrichment
  69. 2026-08-11 01:09 UTCEG score recompute
  70. 2026-08-11 01:09 UTCVendor advisory
  71. 2026-08-11 01:09 UTCGHSA enrichment
  72. 2026-08-11 00:00 UTCEPSS rescore
  73. 2026-08-10 11:59 UTCVendor advisory
  74. 2026-08-10 11:59 UTCGHSA enrichment
  75. 2026-08-09 22:48 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-63977?
CVE-2026-63977 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: dpll: zl3073x: use dplldevicechangentf() and remove changework The change_work was introduced to send device change notifications from DPLL device callbacks without deadlocking on dpll_lock, since the callbacks are already invoked…
When was CVE-2026-63977 disclosed?
CVE-2026-63977 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63977 actively exploited?
CVE-2026-63977 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.9% of all scored CVEs.
What is the CVSS score of CVE-2026-63977?
CVE-2026-63977 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63977?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63977, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63977

Explore →

Is Your Infrastructure Affected by CVE-2026-63977?

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