CVE-2026-31689
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| sles | affected | | |
| debian | bookworm | fixed | 6.1.170-1 |
| debian | bullseye | fixed | 0 |
| debian | forky | fixed | 6.19.13-1 |
| debian | sid | fixed | 6.19.13-1 |
| debian | trixie | fixed | 6.12.85-1 |
| linux-kernel | affected | 6.1.169 | |
| linux-kernel | 7.0 | affected | |
References
- https://git.kernel.org/stable/c/51520e03e70d6c73e33ee7cbe0319767d05764fe
- https://git.kernel.org/stable/c/75825648ce984ca4cebb28e4bd2bf8c3a7e837c5
- https://git.kernel.org/stable/c/87ce8ae511962e105bcb3534944208c6a9471ed9
- https://git.kernel.org/stable/c/aae95970fad2127a1bd49d8713c7cd0677dcd2d6
- https://git.kernel.org/stable/c/d20e98c2df9354cc744431ad8ccbf49405b8b40f
- https://git.kernel.org/stable/c/d3de72e2a2b9ee3a57734c1c068823e41a707715
- https://www.suse.com/security/cve/CVE-2026-31689.html
- https://security-tracker.debian.org/tracker/CVE-2026-31689
CWEs
CWE-476
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.