# CVE-2026-98710: wifi: iwlegacy: 3945: free EEPROM data on remove

> A memory leak in the Linux kernel iwlegacy driver allows local attackers to cause denial of service by repeatedly removing the PCI device.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-109134, BELL-CVE-2026-98710, DEBIAN-CVE-2026-98710, GHSA-8m9r-p559-452q, UBUNTU-CVE-2026-98710

## What is CVE-2026-98710?

CVE-2026-98710 is a memory corruption vulnerability in Linux, published on 18 Oct 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:

wifi: iwlegacy: 3945: free EEPROM data on remove

il3945_pci_probe() calls il_eeprom_init(), which allocates memory for
the EEPROM data. The probe failure paths release this allocation with
il_eeprom_free(), but the remove path does not free it after a
successful probe.

As a result, the EEPROM data is leaked when the PCI device is removed.

Free the EEPROM data in il3945_pci_remove() before releasing the
mac80211 hardware structure.

This issue was found by manual code inspection.

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


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

Apply the vendor's patch.

## Is CVE-2026-98710 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98710 is a memory corruption vulnerability in Linux, published on 18 Oct 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-98710 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-98710/ (Markdown: https://insights.sbomify.com/CVE-2026-98710/index.md)
```

## Sources

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

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