CVE-2026-31689

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

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

EDAC/mc: Fix error path ordering in edac_mc_alloc()

When the mci->pvt_info allocation in edac_mc_alloc() fails, the error path will call put_device() which will end up calling the device's release function.

However, the init ordering is wrong such that device_initialize() happens *after* the failed allocation and thus the device itself and the release function pointer are not initialized yet when they're called:

MCE: In-kernel MCE decoding enabled. ------------[ cut here ]------------ kobject: '(null)': is not initialized, yet kobject_put() is being called. WARNING: lib/kobject.c:734 at kobject_put, CPU#22: systemd-udevd CPU: 22 UID: 0 PID: 538 Comm: systemd-udevd Not tainted 7.0.0-rc1+ #2 PREEMPT(full) RIP: 0010:kobject_put Call Trace: edac_mc_alloc+0xbe/0xe0 [edac_core] amd64_edac_init+0x7a4/0xff0 [amd64_edac] ? __pfx_amd64_edac_init+0x10/0x10 [amd64_edac] do_one_initcall ...

Reorder the calling sequence so that the device is initialized and thus the release function pointer is properly set before it can be used.

This was found by Claude while reviewing another EDAC patch.

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

Published

April 27, 2026

Last Modified

May 6, 2026

Advisory Details (6)

Auto-updated May 6, 2026
No patch confirmed yet.
generic

EDAC/mc: Fix error path ordering in edac_mc_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

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

EDAC/mc: Fix error path ordering in edac_mc_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

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

EDAC/mc: Fix error path ordering in edac_mc_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

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

EDAC/mc: Fix error path ordering in edac_mc_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/87ce8ae511962e105bcb3534944208c6a9471ed9
generic

EDAC/mc: Fix error path ordering in edac_mc_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/75825648ce984ca4cebb28e4bd2bf8c3a7e837c5
generic

EDAC/mc: Fix error path ordering in edac_mc_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/51520e03e70d6c73e33ee7cbe0319767d05764fe

Vendor Advisories for CVE-2026-31689(1)

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 10× in last 7d / 41× 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 123 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31689?
CVE-2026-31689 is a medium vulnerability published on April 27, 2026. In the Linux kernel, the following vulnerability has been resolved: EDAC/mc: Fix error path ordering in edacmcalloc() When the mci->pvtinfo allocation in edacmc_alloc() fails, the error path will call put_device() which will end up calling the device's release function. However, the init ordering…
When was CVE-2026-31689 disclosed?
CVE-2026-31689 was first published in the National Vulnerability Database on April 27, 2026, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31689 actively exploited?
CVE-2026-31689 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31689?
CVE-2026-31689 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-31689?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31689, 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-31689

Explore →

Is Your Infrastructure Affected by CVE-2026-31689?

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

Start Free Scan →Browse All CVEs