From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-68328][LOW] nfp: Check resource mutex allocation [ Upstream Date: Mon, 10 Aug 2026 18:22:18 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-68328 X-AL-KERNEL-Priority: LOW X-AL-KERNEL-Severity: LOW X-AL-KERNEL-Base-Severity: LOW X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 1 X-AL-KERNEL-ActionableScore-Lower: 0 X-AL-KERNEL-Commit: 6dbd428119cb1fd1b73cf6968c711f4ea964dc8b List-Id: CVE: CVE-2026-68328 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: nfp: Check resource mutex allocation [ Upstream Commit: 6dbd428119cb1fd1b73cf6968c711f4ea964dc8b Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6dbd428119cb1fd1b73cf6968c711f4ea964dc8b Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68328 Analysis date: Mon, 10 Aug 2026 18:22:18 -0400 ActionableScore: 1 ActionableScore lower bound: 0 Actionable bucket: Ordinary Moderate / Low-like Manual review required: NO Summary: The nfp driver may dereference a NULL resource mutex after an unchecked allocation failure in `nfp_cpp_resource_find()`, causing a local device-specific denial of service without evidence of memory corruption or privilege escalation. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-68328 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68328 The original announcement does not normally provide a security severity estimate, CVSS assessment, or enough information to determine whether the reported kernel bug represents a practically relevant security issue. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. It combines an autonomous classifier with LLM-assisted technical analysis and a separate ActionableScore mechanism. The purpose of this report is to prioritize Linux kernel CVEs before manual review, identify cases that require prompt investigation, and support automatic closure of issues that are unlikely to have meaningful security impact. Published priority for this report: LOW Manual review required: NO A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-68328 LOW CHECK WITH IMPACT FROM ORIG NN MODERATE Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-690;**CWE-476;CWE-252;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'The nfp driver can dereference a NULL resource mutex because nfp_cpp_resource_find reports success even when nfp_cpp_mutex_alloc fails for a matching resource table entry. The following resource acquire path may pass this NULL handle to nfp_cpp_mutex_trylock while opening the resource, which can crash the kernel or break the driver. For the CVSS the PR:L is used only in the paranoid score because a local unprivileged user may be able to contribute to allocation failure through memory pressure, but reliable triggering usually depends on local driver operations and the presence of Netronome NFP hardware. The issue is not network reachable from packet traffic. Impact is denial of service only because the patch supports a NULL pointer dereference and does not show UAF, OOB access, arbitrary write, information disclosure, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1) YES REMOTE NOMEMCHK SIMPLEFIX NETWORK DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 NO NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 ActionableScoreLower=0 ## 1. ActionableScore * Conservative score: 0 * Paranoid score: 1 * Final recommended bucket: **Ordinary Moderate / Low-like** ## 2. Signal breakdown Conservative signals: * Reliable kernel crash / strong DoS: +1. If `nfp_cpp_mutex_alloc()` returns NULL and the result is passed to `nfp_cpp_mutex_trylock()`, the likely result is a NULL pointer dereference and driver or kernel crash. * Hard or unreliable trigger: -1. The bug depends on allocation failure in a specific resource acquisition path. * Rare hardware / difficult-to-reach subsystem: -1. The affected path requires Netronome NFP hardware and driver resource handling. * Requires admin or privileged device context in typical deployments: -2. Reliable triggering normally depends on driver/device operations, not ordinary packet traffic or a broadly exposed unprivileged interface. Paranoid adjustment: * Local unprivileged influence: +1. A local user might contribute to memory pressure, but this does not by itself reliably trigger the exact driver path. * No memory corruption bonus. This is a NULL pointer dereference from unchecked allocation, not UAF, OOB write, double free, refcount corruption, type confusion, or arbitrary write. * No LPE bonus. The patch and call path do not show attacker-controlled reclaim, object replacement, callback control, writable stale object use, or a privilege escalation primitive. * No confidentiality or integrity impact. The demonstrated effect is availability only. Call-site confidence: high. The commit explicitly states that `nfp_resource_try_acquire()` immediately passes the returned mutex handle to `nfp_cpp_mutex_trylock()`. ## 3. Reachability analysis The issue is local and device-specific. It requires the NFP driver, a matching resource-table entry, and failure of `nfp_cpp_mutex_alloc()`. It is not reachable from normal network packet traffic, despite being in an Ethernet driver. Namespaces or containers do not obviously lower the required privilege because the vulnerable path is tied to device resource acquisition rather than a generic unprivileged socket API. A paranoid scenario can consider local memory pressure as an assisting condition, but reliable exploitation still appears difficult and hardware-dependent. ## 4. Severity interpretation This behaves like an ordinary Moderate or Low-like kernel DoS issue, not an Important-class vulnerability. The theoretical failure mode is a kernel NULL pointer dereference, but there is no supported evidence of memory corruption beyond invalid NULL dereference, no stale lifetime object, no attacker-controlled overwrite, and no practical privilege escalation path. The realistic impact is crash or driver failure under constrained conditions. ## 5. One-sentence report phrase The nfp driver may dereference a NULL resource mutex after an unchecked allocation failure in `nfp_cpp_resource_find()`, causing a local device-specific denial of service without evidence of memory corruption or privilege escalation. ## 6. Manual review recommendation NO MANUAL CHECK NEEDED This can be auto-closed for urgent triage purposes because it is a constrained NULL pointer dereference DoS in a rare hardware driver path, with no network reachability, no demonstrated memory corruption primitive, and no plausible LPE evidence from the patch. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: nfp: Check resource mutex allocation [ Upstream Commit: 6dbd428119cb1fd1b73cf6968c711f4ea964dc8b Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6dbd428119cb1fd1b73cf6968c711f4ea964dc8b Changed files: drivers/net/ethernet/netronome/nfp/nfpcore/nfp_resource.c Diff excerpt: Not included in this email. See the upstream URL for the full patch. Full patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6dbd428119cb1fd1b73cf6968c711f4ea964dc8b ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-68328 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68328 The original CVE announcement normally does not include a security-level estimate. In particular, it may not contain a CVSS assessment, an impact level, or enough information to determine whether the reported bug is a practically relevant security issue. One purpose of this parallel CVE list is to provide that missing technical and prioritization information. The original goal of the AL-KERNEL project was to prioritize Linux kernel CVE analysis automatically before manual review. The system can also help identify non-security issues that may be suitable for automatic closure. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. The first analysis stage combines an autonomous classifier with additional LLM-based analysis. The autonomous classifier runs locally on a CPU and is based on a backpropagation neural network. Together, these mechanisms produce a technical vulnerability description, identify likely weakness types, estimate CVSS severity, and provide input for ActionableScore. Two CVSS estimates are retained because incomplete kernel vulnerability information often permits more than one defensible interpretation: Conservative CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 4.7 The conservative vector represents a lower-impact interpretation. The Best/paranoid vector intentionally represents a plausible upper-bound interpretation and should not automatically be treated as demonstrated real-world impact. CVSS may also need to be adjusted for a particular Linux deployment, because actual reachability, privileges, enabled kernel configuration, hardware, namespaces, exposed device nodes, and other environmental conditions can differ significantly between systems. A separate ActionableScore mechanism evaluates practical remediation urgency. Its analysis may include reachability, attack prerequisites, subsystem exposure, memory-corruption characteristics, denial-of-service reliability, and possible confidentiality, integrity, or privilege-escalation impact. Conservative ActionableScore: 0 Paranoid ActionableScore: 1 The final base severity is taken directly from the second tab-separated field of the AL-KERNEL classification result. ActionableScore does not replace or independently override that final AL-KERNEL decision, and if ActionableScore adjusted impact level of ALKERNEL, then you would see self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7. For an AL-KERNEL result of MODERATE, this report uses the following additional presentation split: ActionableScore below 5 -> MODERATE REGULAR ActionableScore 5 or more -> MODERATE 7.0 The distinction between MODERATE REGULAR and MODERATE 7.0 makes it possible to identify Moderate issues that should receive manual analysis and fixes before lower-priority MODERATE REGULAR issues. In many cases, MODERATE REGULAR fixes may wait for a later rebase or routine update. There is one override in which MODERATE REGULAR becomes MODERATE 7.0 even when the ActionableScore is below 5. When the AL-KERNEL result contains the KPANIC flag, a MODERATE result is always presented as MODERATE 7.0. The KPANIC flag selected with few regexps without usage of AI at all, so it helps to detect cases when Kernel Crash happens and similar (to filter False-Negative results from the LLM usage). KPANIC indicates that a reliable kernel crash, kernel panic, or similarly serious kernel availability impact was identified by the classification workflow. AL-KERNEL base severity for this report: LOW KPANIC detected for this report: NO Published priority for this report (same as in Subject): LOW These results are intended to support engineering triage. They are machine-generated estimates, and cases marked for manual review should be validated by a human security engineer before final disposition. For more info read docs linked from here: https://kernelcve.org/ (and you can submit you own patch there to generate such a report for non-existant CVE-id yet). Note that in many cases this AI tool selects higher severity, than real is (means you can expect Importants instead of Moderate 7.0 or Moderates 7.0 instead of regular Moderates). If you see such cases, please use reply email interface to add additional manual analyses info to this particular CVE. And please, please, let me know when you see Lows instead of Importants or Important instead of Low (because particular for such cases I need to tune this AI tool to make it better for this one and next similar). My contact email for such notifications is alexanjelausa@gmail.com (and both send reply to CVE record itself too and see "reply" button below for howto reply).