Public vulnerability disclosure

CVE-2026-68328

nfp: Check resource mutex allocation

published

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.

Technical severityUnscoredNo score in collected sources
Published2026-08-10Source updated 2026-11-06
Collected2026-11-062 attributed sources

Fixes and workarounds

No remediation reported in collected sources.

Missing remediation information is not evidence that no patch exists.

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Linux
Linux
≥ f01a2161577d31b14581e0db3bbbdfa963f145b6; < 18737a48acc87e4cbe41d6fea9a3f44eae490e24 (affected, git)
≥ f01a2161577d31b14581e0db3bbbdfa963f145b6; < 423523f96a681428ce6e214eaf47f0d8242319de (affected, git)
≥ f01a2161577d31b14581e0db3bbbdfa963f145b6; < 0dbd85a8cc35c14bd26e686fa5fae8c64a7958ae (affected, git)
≥ f01a2161577d31b14581e0db3bbbdfa963f145b6; < 6dbd428119cb1fd1b73cf6968c711f4ea964dc8b (affected, git)
≥ f01a2161577d31b14581e0db3bbbdfa963f145b6; < cfa119aa781c4044dab5b4c1e5864600f53a26bc (affected, git)
≥ f01a2161577d31b14581e0db3bbbdfa963f145b6; < 3b1d4fc3b73ea6faf008a0996ce6190c6e43efc3 (affected, git)
≥ f01a2161577d31b14581e0db3bbbdfa963f145b6; < a7dc30b6828c3a30252892827b12b676749f250f (affected, git)
≥ f01a2161577d31b14581e0db3bbbdfa963f145b6; < a61b4db34a753bdf5c9e77a7f3d3dddd41dcfacc (affected, git)
Other versions: unaffected
CNA: Linux
Linux
Linux
4.11 (affected)
≥ 0; < 4.11 (unaffected, semver)
≥ 5.10.265; ≤ 5.10.* (unaffected, semver)
≥ 5.15.216; ≤ 5.15.* (unaffected, semver)
≥ 6.1.183; ≤ 6.1.* (unaffected, semver)
≥ 6.6.148; ≤ 6.6.* (unaffected, semver)
≥ 6.12.101; ≤ 6.12.* (unaffected, semver)
≥ 6.18.42; ≤ 6.18.* (unaffected, semver)
≥ 7.1.6; ≤ 7.1.* (unaffected, semver)
≥ 7.2; ≤ * (unaffected, original_commit_for_fix)
Other versions: affected
CNA: Linux

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

No CVSS assessment reported. An unscored record is not a low-severity determination.

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide