# CVE-2026-68328: nfp: Check resource mutex allocation

> A null pointer dereference in the Linux kernel nfp driver can cause a system crash when acquiring resources, 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-68328, DEBIAN-CVE-2026-68328, GHSA-pcvh-8mrv-q3wv, UBUNTU-CVE-2026-68328

## What is CVE-2026-68328?

CVE-2026-68328 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:

nfp: Check resource mutex allocation

nfp_cpp_resource_find() allocates a CPP mutex handle for the matching
resource-table entry and then reports success.  nfp_resource_try_acquire()
immediately passes that handle to nfp_cpp_mutex_trylock().

However, nfp_cpp_mutex_alloc() returns NULL on failure.  If that happens
for a matching table entry, the resource lookup still returns success and
the following trylock dereferences a NULL mutex pointer while opening the
resource.

nfp_resource_acquire() already treats failure to allocate the table mutex
as -ENOMEM.  Do the same for the resource mutex and fail the lookup before
publishing the rest of the resource handle.

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

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


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

Apply the vendor's patch.

## Is CVE-2026-68328 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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