CVE-2026-53343

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-01. 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

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:

ARM: 9475/1: entry: use byte load for KASAN VMAP stack shadow

Commit 44e9a3bb76e5 ("ARM: 9430/1: entry: Do a dummy read from VMAP shadow") added a dummy read from the KASAN VMAP stack shadow in __switch_to(). The read uses ldr, but the KASAN shadow address is byte-granular and is not guaranteed to be word aligned.

ARMv5 faults unaligned word loads. With CONFIG_KASAN_VMALLOC and CONFIG_VMAP_STACK enabled, ARM926/VersatilePB crashes in __switch_to() with an alignment exception before reaching init.

Use ldrb for the dummy shadow access. The code only needs to fault in the shadow mapping if the stack shadow is missing, so a byte load is sufficient and matches the granularity of KASAN shadow memory.

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

July 1, 2026

Last Modified

July 23, 2026

Advisory Details (6)

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

ARM: 9475/1: entry: use byte load for KASAN VMAP stack shadow - kernel/git/stable/linux.git - Linux kernel stable tree

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

ARM: 9475/1: entry: use byte load for KASAN VMAP stack shadow - kernel/git/stable/linux.git - Linux kernel stable tree

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

ARM: 9475/1: entry: use byte load for KASAN VMAP stack shadow - kernel/git/stable/linux.git - Linux kernel stable tree

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

ARM: 9475/1: entry: use byte load for KASAN VMAP stack shadow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/77a1f6883dc6e837bb2cb30b9b02e2f94338e2c6
generic

ARM: 9475/1: entry: use byte load for KASAN VMAP stack shadow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/517720913bd3c17a52cd55a740064f68455ab88e
generic

ARM: 9475/1: entry: use byte load for KASAN VMAP stack shadow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2a4dc9a0ac3326e79fb58fdaae724b92127709a9

Vendor Advisories for CVE-2026-53343(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
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
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 (145 versions)7.0.13-1—

Data Freshness Timeline

(refreshed 8× in last 7d / 69× 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 706 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-53343?
CVE-2026-53343 is a medium vulnerability published on July 1, 2026. In the Linux kernel, the following vulnerability has been resolved: ARM: 9475/1: entry: use byte load for KASAN VMAP stack shadow Commit 44e9a3bb76e5 ("ARM: 9430/1: entry: Do a dummy read from VMAP shadow") added a dummy read from the KASAN VMAP stack shadow in switch_to(). The read uses ldr, but…
When was CVE-2026-53343 disclosed?
CVE-2026-53343 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53343 actively exploited?
CVE-2026-53343 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.2% of all scored CVEs.
What is the CVSS score of CVE-2026-53343?
CVE-2026-53343 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53343?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53343, 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-53343

Explore →

Is Your Infrastructure Affected by CVE-2026-53343?

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

Start Free Scan →Browse All CVEs