CVE-2026-53237

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

gpio: mvebu: fix NULL pointer dereference in suspend/resume

mvebu_pwm_suspend() and mvebu_pwm_resume() are called for all GPIO banks during suspend/resume, but not all banks have PWM functionality. GPIO banks without PWM have mvchip->mvpwm set to NULL.

Calling mvebu_pwm_suspend() with mvpwm == NULL causes a NULL pointer dereference when it tries to access mvpwm->blink_select.

Unable to handle kernel NULL pointer dereference at virtual address 00000020 when write [00000020] *pgd=00000000 Internal error: Oops: 815 [#1] PREEMPT ARM Modules linked in: CPU: 0 UID: 0 PID: 406 Comm: sh Not tainted 6.12.74-rt12-yocto-standard-g4e96f98fb7db-dirty #353 Hardware name: Marvell Armada 370/XP (Device Tree) PC is at regmap_mmio_read+0x38/0x54 LR is at regmap_mmio_read+0x38/0x54 pc : [] lr : [] psr: 200f0013 sp : f0c11d10 ip : 00000000 fp : c100d2f0 r10: c14fb854 r9 : 00000000 r8 : 00000000 r7 : c1799c00 r6 : 00000020 r5 : 00000020 r4 : c179c7c0 r3 : f0a231a0 r2 : 00000020 r1 : 00000020 r0 : 00000000 Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none Control: 10c5387d Table: 135ec059 DAC: 00000051 Call trace: regmap_mmio_read from _regmap_bus_reg_read+0x78/0xac _regmap_bus_reg_read from _regmap_read+0x60/0x154 _regmap_read from regmap_read+0x3c/0x60 regmap_read from mvebu_gpio_suspend+0xa4/0x14c mvebu_gpio_suspend from dpm_run_callback+0x54/0x180 dpm_run_callback from device_suspend+0x124/0x630 device_suspend from dpm_suspend+0x124/0x270 dpm_suspend from dpm_suspend_start+0x64/0x6c dpm_suspend_start from suspend_devices_and_enter+0x140/0x8e8 suspend_devices_and_enter from pm_suspend+0x2fc/0x308 pm_suspend from state_store+0x6c/0xc8 state_store from kernfs_fop_write_iter+0x10c/0x1f8 kernfs_fop_write_iter from vfs_write+0x270/0x468 vfs_write from ksys_write+0x70/0xf0 ksys_write from ret_fast_syscall+0x0/0x54

Add a NULL check for mvchip->mvpwm before calling the PWM suspend/resume functions.

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
6%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 8, 2026

Advisory Details (5)

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

gpio: mvebu: fix NULL pointer dereference in suspend/resume - kernel/git/stable/linux.git - Linux kernel stable tree

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

gpio: mvebu: fix NULL pointer dereference in suspend/resume - kernel/git/stable/linux.git - Linux kernel stable tree

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

gpio: mvebu: fix NULL pointer dereference in suspend/resume - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7db09011ce62162d72897fc4856b4425245dfe35
generic

gpio: mvebu: fix NULL pointer dereference in suspend/resume - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6136c1474db88272231573e222896e1998d34662
generic

gpio: mvebu: fix NULL pointer dereference in suspend/resume - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4ef24338eda3c7e96d6f94a988266ff16ed3985d

Vendor Advisories for CVE-2026-53237(2)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
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 (145 versions)7.0.13-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 62× 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 201 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53237?
CVE-2026-53237 is a medium vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: gpio: mvebu: fix NULL pointer dereference in suspend/resume mvebupwmsuspend() and mvebupwmresume() are called for all GPIO banks during suspend/resume, but not all banks have PWM functionality. GPIO banks without PWM have…
When was CVE-2026-53237 disclosed?
CVE-2026-53237 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53237 actively exploited?
CVE-2026-53237 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 94.3% of all scored CVEs.
What is the CVSS score of CVE-2026-53237?
CVE-2026-53237 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53237?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53237, 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-53237

Explore →

Is Your Infrastructure Affected by CVE-2026-53237?

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