nfp: Check resource mutex allocation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f01a2161577d31b14581e0db3bbbdfa963f145b6 · < 3b1d4fc3b73ea6faf008a0996ce6190c6e43efc3| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s nfp resource lookup can report success even when allocation of a resource mutex fails. Opening that resource then dereferences a NULL pointer. The input does not specify an attack path, authentication requirements, or user interaction.
Engineers running the Linux kernel with the nfp component should check whether their kernel includes the fix; affected versions are not specified.