CVE-2026-64165

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-19. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

ARM: integrator: Fix early initialization

Starting with commit bdb249fce9ad4 ("ARM: integrator: read counter using syscon/regmap"), intcp_init_early calls syscon_regmap_lookup_by_compatible which in turn calls of_syscon_register. This function allocates memory. Since the memory management code has not been initialized at that time, the call always fails. It either returns -ENOMEM or crashes as follows.

Unable to handle kernel NULL pointer dereference at virtual address 0000000c when read [0000000c] *pgd=00000000 Internal error: Oops: 5 [#1] ARM Modules linked in: CPU: 0 UID: 0 PID: 0 Comm: swapper Not tainted 6.15.0-rc5-00026-g5fcc9bf84ee5 #1 PREEMPT Hardware name: ARM Integrator/CP (Device Tree) PC is at __kmalloc_cache_noprof+0xec/0x39c LR is at __kmalloc_cache_noprof+0x34/0x39c ... Call trace: __kmalloc_cache_noprof from of_syscon_register+0x7c/0x310 of_syscon_register from device_node_get_regmap+0xa4/0xb0 device_node_get_regmap from intcp_init_early+0xc/0x40 intcp_init_early from start_kernel+0x60/0x688 start_kernel from 0x0

The crash is seen due to a dereferenced pointer which is not supposed to be NULL but is NULL if the memory management subsystem has not been initialized. The crash is not seen with all versions of gcc. Some versions such as gcc 9.x apparently do not dereference the pointer, presumably if tracing is disabled. The problem has been reproduced with gcc 10.x, 11.x, and 13.x. Either case, if the crash is not seen, the call to syscon_regmap_lookup_by_compatible returns -ENOMEM, and sched_clock_register is never called.

Fix the problem by moving the early initialization code into the standard machine initialization code.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 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 13, 2026

Advisory Details (8)

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

ARM: integrator: Fix early initialization - kernel/git/stable/linux.git - Linux kernel stable tree

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

ARM: integrator: Fix early initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/90d77b30a666049ad24df463f52e5d529c44e8cd
generic

ARM: integrator: Fix early initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/812103fb6da904bd03d62cf6a9826e537318ceed
generic

ARM: integrator: Fix early initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6624854554c4c2bdfed3559e5c11bb03b16e7bd1
generic

ARM: integrator: Fix early initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/58a112b0973f6cd6bcb8c503d1ff88be411ed0f0
generic

ARM: integrator: Fix early initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/508b1193d63b5e073a3fe103eeb785fcba2d368c
generic

ARM: integrator: Fix early initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/33ad014abec90f37dade0e00560f28864187e21a
generic

ARM: integrator: Fix early initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/22c738fb51f2d8b23ddff5cc0ccb2dd685bb39d3

Vendor Advisories for CVE-2026-64165(1)

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

Patch Availability(16)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

Weakness Classification(1)

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

All Vendor Advisories

(16)

Data Freshness Timeline

(refreshed 21× in last 7d / 73× 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 105 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64165?
CVE-2026-64165 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: ARM: integrator: Fix early initialization Starting with commit bdb249fce9ad4 ("ARM: integrator: read counter using syscon/regmap"), intcpinitearly calls sysconregmaplookupbycompatible which in turn calls ofsysconregister. This…
When was CVE-2026-64165 disclosed?
CVE-2026-64165 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-64165 actively exploited?
CVE-2026-64165 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 98.0% of all scored CVEs.
What is the CVSS score of CVE-2026-64165?
CVE-2026-64165 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64165?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64165, 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-64165

Explore →

Is Your Infrastructure Affected by CVE-2026-64165?

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