CVE-2026-68328

nfp: Check resource mutex allocation

N/A
Published: August 10, 2026 at 12:03 PM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.11 ≤ v < 5.10.2654.11 ≤ v < 5.15.2164.11 ≤ v < 6.1.1834.11 ≤ v < 6.12.1014.11 ≤ v < 6.18.424.11 ≤ v < 6.6.1484.11 ≤ v < 7.1.64.11 ≤ v < 7.24.11f01a2161577d31b14581e0db3bbbdfa963f145b6
Vendor states this is fixed in 0dbd85a8cc35c14bd26e686fa5fae8c64a7958ae (fixed)
Vendor states this is fixed in 18737a48acc87e4cbe41d6fea9a3f44eae490e24 (fixed)
Vendor states this is fixed in 3b1d4fc3b73ea6faf008a0996ce6190c6e43efc3 (fixed)
Vendor states this is fixed in 423523f96a681428ce6e214eaf47f0d8242319de (fixed)
Vendor states this is fixed in 6dbd428119cb1fd1b73cf6968c711f4ea964dc8b (fixed)
Vendor states this is fixed in a61b4db34a753bdf5c9e77a7f3d3dddd41dcfacc (fixed)
Vendor states this is fixed in a7dc30b6828c3a30252892827b12b676749f250f (fixed)
Vendor states this is fixed in cfa119aa781c4044dab5b4c1e5864600f53a26bc (fixed)
Vendor states this is fixed in 4.11 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card