# CVE-2026-68327: wan: wanxl: Only reset hardware after BAR mapping

> A null pointer dereference in the Linux kernel WAN XL driver during early probe failures can cause a system crash, requiring a kernel patch.

- **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-68327, DEBIAN-CVE-2026-68327, GHSA-hgpj-pm42-vw5v, UBUNTU-CVE-2026-68327

## What is CVE-2026-68327?

CVE-2026-68327 is a 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:

wan: wanxl: Only reset hardware after BAR mapping

wanxl_pci_init_one() stores the freshly allocated card in driver data
before the PLX BAR is mapped.  Several early probe failures then unwind
through wanxl_pci_remove_one(), including failure to allocate the coherent
status area or to restore the DMA mask.

wanxl_pci_remove_one() unconditionally calls wanxl_reset(), and
wanxl_reset() dereferences card->plx.  On those early failures card->plx
is still NULL, so the error path can dereference a NULL MMIO pointer.

Only issue the hardware reset once the BAR mapping exists.  The remaining
cleanup in wanxl_pci_remove_one() already checks whether later resources
were allocated.

This issue was found by a static analysis checker and confirmed by
manual source review.

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


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

Apply the vendor's patch.

## Is CVE-2026-68327 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68327 is a 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-68327 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-68327/ (Markdown: https://insights.sbomify.com/CVE-2026-68327/index.md)
```

## Sources

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

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