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.
CVE-2026-68328
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: osv:CVE-2026-68328
Kernel
Source reference: /affected/1/package/name
- Affected versions
- Not stated in this record
- Fixed versions
- 5.10.265
Source reference:
/affected/1/ranges5.15.216Source reference:
/affected/1/ranges6.1.183Source reference:
/affected/1/ranges6.6.148Source reference:
/affected/1/ranges6.12.101Source reference:
/affected/1/ranges6.18.42Source reference:
/affected/1/ranges7.1.6Source reference:
/affected/1/ranges - Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "f01a2161577d31b14581e0db3bbbdfa963f145b6"
},
{
"fixed": "18737a48acc87e4cbe41d6fea9a3f44eae490e24"
},
{
"fixed": "423523f96a681428ce6e214eaf47f0d8242319de"
},
{
"fixed": "0dbd85a8cc35c14bd26e686fa5fae8c64a7958ae"
},
{
"fixed": "6dbd428119cb1fd1b73cf6968c711f4ea964dc8b"
},
{
"fixed": "cfa119aa781c4044dab5b4c1e5864600f53a26bc"
},
{
"fixed": "3b1d4fc3b73ea6faf008a0996ce6190c6e43efc3"
},
{
"fixed": "a7dc30b6828c3a30252892827b12b676749f250f"
},
{
"fixed": "a61b4db34a753bdf5c9e77a7f3d3dddd41dcfacc"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68328.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.11.0"
},
{
"fixed": "5.10.265"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.216"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.183"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.148"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.101"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.42"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.1.6"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68328.json"
}
}
]- Related CVEs
- CVE-2026-68328
Source reference:
/id
Publisher severity
No explicit severity was provided.
- Event
- #50792 · Revision 1
- Added to Heist Feed
- Publisher date