CVE-2026-80643

What it actually does

The igen6_edac driver registers memory controller devices without providing a release() callback, violating kernel device model requirements and triggering warnings plus call traces during module unload via device_release and kobject_put.

Why it matters to the business

Kernel warnings and potential instability appear when unloading the driver on systems using Intel E8000 series memory controllers, increasing maintenance overhead and risk of unexpected behavior during driver updates or reboots.

How an attack unfolds

An attacker with local access could trigger repeated load/unload cycles of the igen6_edac module to generate noise in logs or attempt to leverage the incomplete device teardown for denial-of-service, though the issue is primarily a stability defect rather than a direct code-execution vector.

How to fix it

Update the Linux kernel to a version containing the commit that adds empty release() functions for the memory controller devices in igen6_edac; rebuild and deploy the updated kernel image across affected systems.

How to confirm the fix worked

After applying the kernel update, load and unload the igen6_edac module and confirm absence of the device_release warning and call trace in dmesg; inspect /sys/devices for proper device registration.

Typical attack path

1. Obtain local access on a system with the igen6_edac driver loaded
2. Unload and reload the module repeatedly via rmmod and modprobe
3. Observe resulting call traces and warnings in dmesg
4. Use log volume or system instability for secondary disruption

How to detect it

Search kernel logs and dmesg for the strings 'does not have a release() function' and 'device_release' originating from igen6_edac module unload operations; correlate with rmmod events.

• Device '(null)' does not have a release() function
• WARNING: drivers/base/core.c.*device_release
• igen6_unregister_mcis.*igen6_edac

What your security team should do

• Prioritize kernel upgrade on systems using Intel E8000 EDAC hardware within standard change windows
• Monitor dmesg and kernel logs for the specific device_release warning pattern
• Test driver unload behavior in staging environments before production rollout