Answer in brief
CVE-2026-68328 records a Unknown severity vulnerability in nfp: Check resource mutex allocation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f01a2161577d31b14581e0db3bbbdfa963f145b6 <6dbd428119cb1fd1b73cf6968c711f4ea964dc8b || >=f01a2161577d31b14581e0db3bbbdfa963f145b6 <cfa119aa781c4044dab5b4c1e5864600f53a26bc || >=f01a2161577d31b14581e0db3bbbdfa963f145b6 <3b1d4fc3b73ea6faf008a0996ce6190c6e43efc3 || >=f01a2161577d31b14581e0db3bbbdfa963f145b6 <a7dc30b6828c3a30252892827b12b676749f250f || >=f01a2161577d31b14581e0db3bbbdfa963f145b6 <a61b4db34a753bdf5c9e77a7f3d3dddd41dcfacc | 6dbd428119cb1fd1b73cf6968c711f4ea964dc8b, cfa119aa781c4044dab5b4c1e5864600f53a26bc, 3b1d4fc3b73ea6faf008a0996ce6190c6e43efc3, a7dc30b6828c3a30252892827b12b676749f250f, a61b4db34a753bdf5c9e77a7f3d3dddd41dcfacc |
| Linux/Linuxgeneric | 4.11 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68328 records a Unknown severity vulnerability in nfp: Check resource mutex allocation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f01a2161577d31b14581e0db3bbbdfa963f145b6 <6dbd428119cb1fd1b73cf6968c711f4ea964dc8b || >=f01a2161577d31b14581e0db3bbbdfa963f145b6 <cfa119aa781c4044dab5b4c1e5864600f53a26bc || >=f01a2161577d31b14581e0db3bbbdfa963f145b6 <3b1d4fc3b73ea6faf008a0996ce6190c6e43efc3 || >=f01a2161577d31b14581e0db3bbbdfa963f145b6 <a7dc30b6828c3a30252892827b12b676749f250f || >=f01a2161577d31b14581e0db3bbbdfa963f145b6 <a61b4db34a753bdf5c9e77a7f3d3dddd41dcfacc | 6dbd428119cb1fd1b73cf6968c711f4ea964dc8b, cfa119aa781c4044dab5b4c1e5864600f53a26bc, 3b1d4fc3b73ea6faf008a0996ce6190c6e43efc3, a7dc30b6828c3a30252892827b12b676749f250f, a61b4db34a753bdf5c9e77a7f3d3dddd41dcfacc |
| Linux/Linuxgeneric | 4.11 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.