# CVE-2026-68413: wifi: ipw2100: fix potential memory leak in ipw2100_pci_init_one()

> A memory leak in the ipw2100 WiFi driver allows local attackers to cause resource exhaustion and denial of service.

- **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:** 10 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** BELL-CVE-2026-68413, DEBIAN-CVE-2026-68413, GHSA-x5pr-m9j2-mmv9, UBUNTU-CVE-2026-68413

## What is CVE-2026-68413?

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

wifi: ipw2100: fix potential memory leak in ipw2100_pci_init_one()

The memory allocated in the ipw2100_alloc_device() function is not freed
in some of the error paths in ipw2100_pci_init_one(). Fix that by
converting the direct return into a goto to the error path return.

The error path when pci_enable_device() fails cannot jump to fail, since
at this point priv is not set, so perform error handling inline.

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


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

Apply the vendor's patch.

## Is CVE-2026-68413 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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