CVE-2026-68328nfp: Check resource mutex allocation
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.18% · top 93% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected f01a2161577d31b14581e0db3bbbdfa963f145b6 – < 18737a48acc87e4cbe41d6fea9a3f44eae490e24
- affected f01a2161577d31b14581e0db3bbbdfa963f145b6 – < 423523f96a681428ce6e214eaf47f0d8242319de
- affected f01a2161577d31b14581e0db3bbbdfa963f145b6 – < 0dbd85a8cc35c14bd26e686fa5fae8c64a7958ae
- affected f01a2161577d31b14581e0db3bbbdfa963f145b6 – < 6dbd428119cb1fd1b73cf6968c711f4ea964dc8b
- affected f01a2161577d31b14581e0db3bbbdfa963f145b6 – < cfa119aa781c4044dab5b4c1e5864600f53a26bc
- affected f01a2161577d31b14581e0db3bbbdfa963f145b6 – < 3b1d4fc3b73ea6faf008a0996ce6190c6e43efc3
- affected f01a2161577d31b14581e0db3bbbdfa963f145b6 – < a7dc30b6828c3a30252892827b12b676749f250f
- affected f01a2161577d31b14581e0db3bbbdfa963f145b6 – < a61b4db34a753bdf5c9e77a7f3d3dddd41dcfacc
- affected 4.11
- unaffected < 4.11
- unaffected 5.10.265 – ≤ 5.10.*
- unaffected 5.15.216 – ≤ 5.15.*
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.6 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/18737a48acc87e4cbe41d6fea9a3f44eae490e24 (opens in a new tab)
- https://git.kernel.org/stable/c/423523f96a681428ce6e214eaf47f0d8242319de (opens in a new tab)
- https://git.kernel.org/stable/c/0dbd85a8cc35c14bd26e686fa5fae8c64a7958ae (opens in a new tab)
- https://git.kernel.org/stable/c/6dbd428119cb1fd1b73cf6968c711f4ea964dc8b (opens in a new tab)
- https://git.kernel.org/stable/c/cfa119aa781c4044dab5b4c1e5864600f53a26bc (opens in a new tab)
- https://git.kernel.org/stable/c/3b1d4fc3b73ea6faf008a0996ce6190c6e43efc3 (opens in a new tab)
- https://git.kernel.org/stable/c/a7dc30b6828c3a30252892827b12b676749f250f (opens in a new tab)
- https://git.kernel.org/stable/c/a61b4db34a753bdf5c9e77a7f3d3dddd41dcfacc (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-55429 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-68328)Record last updated .