CVE-2026-31689EDAC/mc: Fix error path ordering in edac_mc_alloc()
- 5.5MediumCVSS base score
- 0.11%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 49 days later
· 49 days later
Published
- 14 days later
· 14 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.11% · top 98% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 0bbb265f7089584aaa6d440805ca75ea4f3930d4 – < aae95970fad2127a1bd49d8713c7cd0677dcd2d6
- affected 0bbb265f7089584aaa6d440805ca75ea4f3930d4 – < d3de72e2a2b9ee3a57734c1c068823e41a707715
- affected 0bbb265f7089584aaa6d440805ca75ea4f3930d4 – < d20e98c2df9354cc744431ad8ccbf49405b8b40f
- affected 0bbb265f7089584aaa6d440805ca75ea4f3930d4 – < 87ce8ae511962e105bcb3534944208c6a9471ed9
- affected 0bbb265f7089584aaa6d440805ca75ea4f3930d4 – < 75825648ce984ca4cebb28e4bd2bf8c3a7e837c5
- affected 0bbb265f7089584aaa6d440805ca75ea4f3930d4 – < 51520e03e70d6c73e33ee7cbe0319767d05764fe
- affected 5.19
- unaffected < 5.19
- unaffected 6.1.169 – ≤ 6.1.*
- unaffected 6.6.135 – ≤ 6.6.*
- unaffected 6.12.82 – ≤ 6.12.*
- unaffected 6.18.23 – ≤ 6.18.*
- unaffected 6.19.13 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References6
- https://git.kernel.org/stable/c/aae95970fad2127a1bd49d8713c7cd0677dcd2d6 (opens in a new tab)
- https://git.kernel.org/stable/c/d3de72e2a2b9ee3a57734c1c068823e41a707715 (opens in a new tab)
- https://git.kernel.org/stable/c/d20e98c2df9354cc744431ad8ccbf49405b8b40f (opens in a new tab)
- https://git.kernel.org/stable/c/87ce8ae511962e105bcb3534944208c6a9471ed9 (opens in a new tab)
- https://git.kernel.org/stable/c/75825648ce984ca4cebb28e4bd2bf8c3a7e837c5 (opens in a new tab)
- https://git.kernel.org/stable/c/51520e03e70d6c73e33ee7cbe0319767d05764fe (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-25886 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-31689)Record last updated .