CVE-2026-64162

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-19. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.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: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init()

In idpf_ptp_init(), read_dev_clk_lock is initialized after ptp_schedule_worker() had already been called (and after idpf_ptp_settime64() could reach the lock). The PTP aux worker fires immediately upon scheduling and can call into idpf_ptp_read_src_clk_reg_direct(), which takes spin_lock(&ptp->read_dev_clk_lock) on an uninitialized lock, triggering the lockdep "non-static key" warning:

[12973.796587] idpf 0000:83:00.0: Device HW Reset initiated [12974.094507] INFO: trying to register non-static key. ... [12974.097208] Call Trace: [12974.097213] [12974.097218] dump_stack_lvl+0x93/0xe0 [12974.097234] register_lock_class+0x4c4/0x4e0 [12974.097249] ? __lock_acquire+0x427/0x2290 [12974.097259] __lock_acquire+0x98/0x2290 [12974.097272] lock_acquire+0xc6/0x310 [12974.097281] ? idpf_ptp_read_src_clk_reg+0xb7/0x150 [idpf] [12974.097311] ? lockdep_hardirqs_on_prepare+0xde/0x190 [12974.097318] ? finish_task_switch.isra.0+0xd2/0x350 [12974.097330] ? __pfx_ptp_aux_kworker+0x10/0x10 [ptp] [12974.097343] _raw_spin_lock+0x30/0x40 [12974.097353] ? idpf_ptp_read_src_clk_reg+0xb7/0x150 [idpf] [12974.097373] idpf_ptp_read_src_clk_reg+0xb7/0x150 [idpf] [12974.097391] ? kthread_worker_fn+0x88/0x3d0 [12974.097404] ? kthread_worker_fn+0x4e/0x3d0 [12974.097411] idpf_ptp_update_cached_phctime+0x26/0x120 [idpf] [12974.097428] ? _raw_spin_unlock_irq+0x28/0x50 [12974.097436] idpf_ptp_do_aux_work+0x15/0x20 [idpf] [12974.097454] ptp_aux_kworker+0x20/0x40 [ptp] [12974.097464] kthread_worker_fn+0xd5/0x3d0 [12974.097474] ? __pfx_kthread_worker_fn+0x10/0x10 [12974.097482] kthread+0xf4/0x130 [12974.097489] ? __pfx_kthread+0x10/0x10 [12974.097498] ret_from_fork+0x32c/0x410 [12974.097512] ? __pfx_kthread+0x10/0x10 [12974.097519] ret_from_fork_asm+0x1a/0x30 [12974.097540]

Move the call to spin_lock_init() up a bit to make sure read_dev_clk_lock is not touched before it's been initialized.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 13, 2026

Advisory Details (3)

Auto-updated Aug 27, 2026
No patch confirmed yet.
generic

idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3122d70b7c0101d897fb795658a7b93f854935f2

Vendor Advisories for CVE-2026-64162(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 58× in last 7d / 341× 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 416 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64162?
CVE-2026-64162 is a critical vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: idpf: fix readdevclklock spinlock init in idpfptp_init() In idpfptpinit(), readdevclk_lock is initialized after ptpscheduleworker() had already been called (and after idpfptpsettime64() could reach the lock). The PTP aux worker…
When was CVE-2026-64162 disclosed?
CVE-2026-64162 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64162 actively exploited?
CVE-2026-64162 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 72.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64162?
CVE-2026-64162 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-64162?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64162, 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-64162

Explore →

Is Your Infrastructure Affected by CVE-2026-64162?

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