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
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:

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

Published

April 22, 2026

Last Modified

July 14, 2026

Advisory Details (9)

Auto-updated Jul 19, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic

module: Fix kernel panic when a symbol st_shndx is out of bounds - kernel/git/stable/linux.git - Linux kernel stable tree

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

module: Fix kernel panic when a symbol st_shndx is out of bounds - kernel/git/stable/linux.git - Linux kernel stable tree

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

module: Fix kernel panic when a symbol st_shndx is out of bounds - kernel/git/stable/linux.git - Linux kernel stable tree

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

module: Fix kernel panic when a symbol st_shndx is out of bounds - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ba6957c640f58dc8ef046981a045da43e47ea23
generic

module: Fix kernel panic when a symbol st_shndx is out of bounds - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d16f519b6eb1d071807e57efe0df2baa8d32ad6
generic

module: Fix kernel panic when a symbol st_shndx is out of bounds - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4bbdb0e48176fd281c2b9a211b110db6fd94e175
generic

module: Fix kernel panic when a symbol st_shndx is out of bounds - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/082f15d2887329e0f43fd3727e69365f5bfe5d2c

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.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.15.203osv

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (121 versions)6.19.11-1

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

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 0% probability of exploitation in the next 30 days, which ranks it in the top 97.5% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.