Skip to main content
VulnerabilityPublished Updated

CVE-2026-68328: Linux kernel · nfp: Check resource mutex allocation

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in cfa119aa781c4044dab5b4c1e5864600f53a26bc : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:19 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in cfa119aa781c4044dab5b4c1e5864600f53a26bc, a61b4db34a753bdf5c9e77a7f3d3dddd41dcfacc, a7dc30b6828c3a30252892827b12b676749f250f +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ f01a2161577d31b14581e0db3bbbdfa963f145b6, < cfa119aa781c4044dab5b4c1e5864600f53a26bc
Fixed in
  • cfa119aa781c4044dab5b4c1e5864600f53a26bc
LinuxLinuxAffected
  • ≥ f01a2161577d31b14581e0db3bbbdfa963f145b6, < a61b4db34a753bdf5c9e77a7f3d3dddd41dcfacc
Fixed in
  • a61b4db34a753bdf5c9e77a7f3d3dddd41dcfacc
LinuxLinuxAffected
  • ≥ f01a2161577d31b14581e0db3bbbdfa963f145b6, < a7dc30b6828c3a30252892827b12b676749f250f
Fixed in
  • a7dc30b6828c3a30252892827b12b676749f250f
LinuxLinuxAffected
  • ≥ f01a2161577d31b14581e0db3bbbdfa963f145b6, < 423523f96a681428ce6e214eaf47f0d8242319de
Fixed in
  • 423523f96a681428ce6e214eaf47f0d8242319de
LinuxLinuxAffected
  • ≥ f01a2161577d31b14581e0db3bbbdfa963f145b6, < 18737a48acc87e4cbe41d6fea9a3f44eae490e24
Fixed in
  • 18737a48acc87e4cbe41d6fea9a3f44eae490e24
LinuxLinuxAffected
  • ≥ f01a2161577d31b14581e0db3bbbdfa963f145b6, < 6dbd428119cb1fd1b73cf6968c711f4ea964dc8b
Fixed in
  • 6dbd428119cb1fd1b73cf6968c711f4ea964dc8b

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.

References

Community reviews

Loading reviews…