From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2025-37847][LOW] accel/ivpu: Fix deadlock in ivpu_ms_cleanup() Date: Mon, 12 Oct 2026 22:07:06 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2025-37847 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: unknown X-AL-KERNEL-Commit: 7d12a7d43c7bab9097ba466581d8db702e7908dc List-Id: CVE: CVE-2025-37847 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: accel/ivpu: Fix deadlock in ivpu_ms_cleanup() Commit: 7d12a7d43c7bab9097ba466581d8db702e7908dc Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7d12a7d43c7bab9097ba466581d8db702e7908dc Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2025-37847 Analysis date: Mon, 12 Oct 2026 22:07:06 -0400 ActionableScore: 1 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate Manual review required: NO Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2025-37847 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2025-37847 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-2025-37847 LOW https://www.kernelcve.org/list/?q=CVE-2025-37847 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT LOW AEGIS_AS=0 LEGACY=LOW RESULT=SAME (legacy and Aegis reconciliation agree; DECISION: both LOW) 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-833;CWE-667;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'A deadlock can occur in ivpu_ms_cleanup() because runtime resume may be initiated while file_priv ms_lock is held. If runtime resume fails, the IVPU cold boot path calls ivpu_ms_cleanup_all(), which enters ivpu_ms_cleanup() again and attempts to acquire the same lock. Triggering requires local access to the IVPU device, an active NPU profiling state, runtime suspension, and a resume failure, so the attack complexity is high. For the CVSS the PR:L value is used because a local process with permission to access the IVPU device can reach the relevant file cleanup and profiling paths without full host administrative privileges. The issue is not network reachable. Impact is denial of service through a stalled cleanup or recovery path and possible loss of IVPU availability. There is no supported memory corruption primitive or credible privilege escalation path.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) MAYBE DEADLOCK SIMPLEFIX DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_GUESSCVSS_AND_CIANNH - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 PrimitiveClass=CLASS_C RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=NO ImportantCandidate=NO ManualReview=NO AutoDowngradeAllowed=YES RequiresHostUID0=UNKNOWN AuthorizationDecisionBypass=NO ProtectedResourceImpact=NONE B4PendingReview=NO B4PendingConfirmed=NO 1. ActionableScore * Raw conservative score: 1 * Conservative score: 1 * Raw paranoid score: 1 * Paranoid score: 1 * No floor or cap applied. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown Positive signals: * +1 Concrete denial of service. A failed runtime resume can re-enter `ivpu_ms_cleanup()` through cold boot and `ivpu_ms_cleanup_all()`, causing recursive acquisition of `file_priv->ms_lock` and stalling cleanup or IVPU recovery. Negative signals: * No negative points. Host-admin privilege is not established, so no privilege penalty is applied. * No hardware rarity penalty. Intel IVPU hardware is required, but the supplied evidence does not establish physical-only access or sufficiently rare hardware. Important non-awarded signals: * No UAF, OOB access, heap overwrite, refcount corruption, or stale-object use is established. * No controlled reclaim, arbitrary write, information disclosure, or privilege-escalation primitive is demonstrated. * No remote reachability or ordinary unprivileged reachability bonus is awarded. * No extra Availability point is awarded because the device cleanup deadlock is the only demonstrated consequence. * B5-R does not apply. There is no retry-accumulated heap OOB write or later consumption of corrupted structured state. * B3-PENDING does not apply. There is no shared-backing write. * B4-PENDING does not apply. No authorization decision changes from DENY to ALLOW. 3. Reachability analysis The vulnerable sequence requires an IVPU device, an `ivpu_file_priv` participating in NPU profiling cleanup, runtime suspension, and a failed runtime resume that initiates cold boot. Cold boot then invokes `ivpu_ms_cleanup_all()`, which re-enters cleanup and attempts to acquire the same mutex. The exact device-node permissions and the complete userspace sequence needed to create the relevant profiling state are not shown. Therefore, below-host-admin reachability is not positively established, but host-admin-equivalent privilege is also not established. `HostAdminRequired` is consequently `UNKNOWN`. The path is device-file based rather than namespace-capability based. No attacker-created namespace or namespace-scoped capability completes the trigger. No network trigger exists. This is an ordered re-entrant failure path, not a timing race, so no race penalty is applied. 4. Primitive and severity interpretation The exact defect is recursive mutex acquisition caused by runtime PM re-entry: `ivpu_ms_cleanup()` enters runtime resume while holding `ms_lock`, resume failure initiates cold boot, and cold boot reaches `ivpu_ms_cleanup()` again through `ivpu_ms_cleanup_all()`. This is a deadlock and device-availability defect, classified as `CLASS_C`. It is not an active-object UAF, fixed stale-storage UAF, repeated release, or memory-corruption primitive. The demonstrated consequence is a stalled cleanup or recovery path and possible loss of IVPU availability. Host-wide kernel panic, confidentiality impact, integrity impact, and privilege escalation are not supported. `ImportantCandidate=NO` because no corruption, lifetime, ownership, authorization, or cross-boundary primitive remains unresolved. `AutoDowngradeAllowed=YES` because the evidence supports only a hardware-specific deadlock and device-local DoS. 5. One-sentence report phrase A failed IVPU runtime resume can recursively enter profiling cleanup and deadlock on file_priv ms_lock, potentially leaving the IVPU cleanup or recovery path unavailable. 6. Manual review recommendation NO MANUAL CHECK NEEDED The patch addresses a concrete but constrained lock-ordering deadlock without memory corruption, authorization bypass, host-wide crash evidence, or an Important-preserving primitive. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: accel/ivpu: Fix deadlock in ivpu_ms_cleanup() Commit: 7d12a7d43c7bab9097ba466581d8db702e7908dc Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7d12a7d43c7bab9097ba466581d8db702e7908dc Commit description: Fix deadlock in ivpu_ms_cleanup() by preventing runtime resume after file_priv->ms_lock is acquired. During a failure in runtime resume, a cold boot is executed, which calls ivpu_ms_cleanup_all(). This function calls ivpu_ms_cleanup() that acquires file_priv->ms_lock and causes the deadlock. Fixes: cdfad4d ("accel/ivpu: Add NPU profiling support") Cc: stable@vger.kernel.org # v6.11+ Signed-off-by: Maciej Falkowski Reviewed-by: Lizhi Hou Signed-off-by: Jacek Lawrynowicz Link: https://lore.kernel.org/r/20250325114306.3740022-2-maciej.falkowski@linux.intel.com Signed-off-by: Greg Kroah-Hartman Changed files: drivers/accel/ivpu/ivpu_ms.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=7d12a7d43c7bab9097ba466581d8db702e7908dc ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2025-37847 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2025-37847 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:L/UI:N/S:U/C:N/I:N/A:L 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: unknown 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).