# CVE-2026-80643: EDAC/igen6: Fix call trace due to missing release()

> A missing release function in the Linux kernel EDAC driver causes a call trace and potential crash when unloading the module.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-98159, BELL-CVE-2026-80643, DEBIAN-CVE-2026-80643, GHSA-v4h2-gggg-pg57, UBUNTU-CVE-2026-80643

## What is CVE-2026-80643?

CVE-2026-80643 is a vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

EDAC/igen6: Fix call trace due to missing release()

When unloading the igen6_edac driver, there is a call trace:

  Device '(null)' does not have a release() function, it is broken and must be fixed.
  See Documentation/core-api/kobject.rst.
  WARNING: drivers/base/core.c:2567 at device_release+0x84/0x90, CPU#5: rmmod/127209
  ...
  RIP: 0010:device_release+0x84/0x90
  Call Trace:
   <TASK>
   kobject_put+0x8c/0x220
   put_device+0x17/0x30
   igen6_unregister_mcis+0xa2/0xe0 [igen6_edac]
   igen6_remove+0x82/0xb0 [igen6_edac]
   ...

Fix the call trace by providing empty release() functions for the
memory controller devices.

## Which versions are affected by CVE-2026-80643?


## How do I fix CVE-2026-80643?

Apply the vendor's patch.

## Is CVE-2026-80643 being exploited?

There is no known exploitation of CVE-2026-80643 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80643 and fix it if it is affected.

What it is: CVE-2026-80643 is a vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80643 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80643/ (Markdown: https://insights.sbomify.com/CVE-2026-80643/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80643
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80643
- OSV: https://osv.dev/vulnerability/CVE-2026-80643

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80643/
Summaries are generated and may contain mistakes; the official description above is the record.