PT-2026-35495 · Linux · Linux
Published
2026-04-27
·
Updated
2026-04-27
·
CVE-2026-31689
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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.
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux