CVE-2026-31521

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 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:

module: Fix kernel panic when a symbol st_shndx is out of bounds

The module loader doesn't check for bounds of the ELF section index in simplify_symbols():

for (i = 1; i < symsec->sh_size / sizeof(Elf_Sym); i++) { const char *name = info->strtab + sym[i].st_name;

switch (sym[i].st_shndx) { case SHN_COMMON:

[...]

default: /* Divert to percpu allocation if a percpu var. */ if (sym[i].st_shndx == info->index.pcpu) secbase = (unsigned long)mod_percpu(mod); else / HERE --> / secbase = info->sechdrs[sym[i].st_shndx].sh_addr; sym[i].st_value += secbase; break; } }

A symbol with an out-of-bounds st_shndx value, for example 0xffff (known as SHN_XINDEX or SHN_HIRESERVE), may cause a kernel panic:

BUG: unable to handle page fault for address: ... RIP: 0010:simplify_symbols+0x2b2/0x480 ... Kernel panic - not syncing: Fatal exception

This can happen when module ELF is legitimately using SHN_XINDEX or when it is corrupted.

Add a bounds check in simplify_symbols() to validate that st_shndx is within the valid range before using it.

This issue was discovered due to a bug in llvm-objcopy, see relevant discussion for details [1].

[1] https://lore.kernel.org/linux-modules/[email protected]/

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
2.6%
KEV
Not listed

Published

April 22, 2026

Last Modified

July 14, 2026

Vendor Advisories for CVE-2026-31521(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 45× 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 136 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31521?
CVE-2026-31521 is a medium vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: module: Fix kernel panic when a symbol st_shndx is out of bounds The module loader doesn't check for bounds of the ELF section index in simplify_symbols(): for (i = 1; i < symsec->shsize / sizeof(ElfSym); i++) { const char *name =…
When was CVE-2026-31521 disclosed?
CVE-2026-31521 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31521 actively exploited?
CVE-2026-31521 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31521?
CVE-2026-31521 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-31521?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31521, 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

Explore the affected products and dependency analysis for CVE-2026-31521

Explore →

Is Your Infrastructure Affected by CVE-2026-31521?

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