CVE-2026-31689: Linux kernel · EDAC/mc: Fix error path ordering in edac_mc_alloc()
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 27 Oct 2026, 00:07 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
Description
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: <TASK> 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.
References
- nvd.nist.gov/vuln/detail/CVE-2026-31689 (opens in a new tab)
- git.kernel.org/stable/c/51520e03e70d6c73e33ee7cbe0319767d05764fe (opens in a new tab)
- git.kernel.org/stable/c/75825648ce984ca4cebb28e4bd2bf8c3a7e837c5 (opens in a new tab)
- git.kernel.org/stable/c/87ce8ae511962e105bcb3534944208c6a9471ed9 (opens in a new tab)
- git.kernel.org/stable/c/aae95970fad2127a1bd49d8713c7cd0677dcd2d6 (opens in a new tab)
- git.kernel.org/stable/c/d20e98c2df9354cc744431ad8ccbf49405b8b40f (opens in a new tab)
- git.kernel.org/stable/c/d3de72e2a2b9ee3a57734c1c068823e41a707715 (opens in a new tab)