CVE-2026-68328 — nfp: Check resource mutex allocation
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ f01a2161577d31b14581e0db3bbbdfa963f145b6 and < 18737a48acc87e4cbe41d6fea9a3f44eae490e24≥ f01a2161577d31b14581e0db3bbbdfa963f145b6 and < 423523f96a681428ce6e214eaf47f0d8242319de≥ f01a2161577d31b14581e0db3bbbdfa963f145b6 and < 0dbd85a8cc35c14bd26e686fa5fae8c64a7958ae≥ f01a2161577d31b14581e0db3bbbdfa963f145b6 and < 6dbd428119cb1fd1b73cf6968c711f4ea964dc8b≥ f01a2161577d31b14581e0db3bbbdfa963f145b6 and < cfa119aa781c4044dab5b4c1e5864600f53a26bc≥ f01a2161577d31b14581e0db3bbbdfa963f145b6 and < 3b1d4fc3b73ea6faf008a0996ce6190c6e43efc3≥ f01a2161577d31b14581e0db3bbbdfa963f145b6 and < a7dc30b6828c3a30252892827b12b676749f250f≥ f01a2161577d31b14581e0db3bbbdfa963f145b6 and < a61b4db34a753bdf5c9e77a7f3d3dddd41dcfacc and 1 moreversion 4.11 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 30, 2026 · 15 reading(s) · max 0.18%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/a61b4db34a753bdf5c9e77a7f3d3dddd41dcfacc
- git.kernel.org/stable/c/6dbd428119cb1fd1b73cf6968c711f4ea964dc8b
- git.kernel.org/stable/c/423523f96a681428ce6e214eaf47f0d8242319de
- git.kernel.org/stable/c/a7dc30b6828c3a30252892827b12b676749f250f
- git.kernel.org/stable/c/3b1d4fc3b73ea6faf008a0996ce6190c6e43efc3
- git.kernel.org/stable/c/0dbd85a8cc35c14bd26e686fa5fae8c64a7958ae
- git.kernel.org/stable/c/18737a48acc87e4cbe41d6fea9a3f44eae490e24
- git.kernel.org/stable/c/cfa119aa781c4044dab5b4c1e5864600f53a26bc
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-68328 is "nfp: Check resource mutex allocation", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.