Description
In the Linux kernel, the following vulnerability has been resolved:

remoteproc: Prevent crash handling to race with rproc_del()

There's no synchronization between rproc_crash_handler_work() and
rproc_del(), as such it's possible for a driver to be removed while
crash-handler work is scheduled, or even executing - resulting in
use-after-free issues.

To avoid this the scheduled work need to be cancelled and synchronized
against before the removal proceeds.

In order to ensure that this doesn't race with the reporting, and
thereby scheduling new work, a "deleting" flag is introduced. This is
similar to the RPROC_DELETE state that was introduced to ensure that
"start" didn't race with rproc_del(), but the existing mechanism can not
be used as it's valid to call rproc_report_crash() in atomic context -
and the "state" is protected by a mutex.

In the event that work is cancelled the pm_stay_awake() is left
unbalanced and need to be unrolled.

The blocking and cancelling of crash-handler work prior to the actual
rproc_shutdown() call does have the explicit side-effect that crashes
resulting from the shutdown process will not enter the crash-handling
path, and as such will not generate devcoredumps etc. Due to the
existing mutual exclusion between these code paths there's no concrete
reduction in functionality, but further work would be needed to handle
this case.
Published: 2026-09-17
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: Use-After-Free
Action: Apply Patch
AI Analysis

Impact

The remoteproc subsystem in the Linux kernel lacks proper synchronization between crash‑handler work and driver removal. This allows a driver to be freed while crash‑handler work is still scheduled or executing, resulting in a use‑after‑free condition that can corrupt kernel memory and provide an opportunity for a local attacker to execute arbitrary code with kernel privileges.

Affected Systems

All Linux kernel releases that compile and run the remoteproc subsystem and have not yet incorporated the patch that introduces a deleting flag to cancel pending crash‑handler work. Because no specific version numbers are provided, any kernel containing the vulnerable code before the fix is considered at risk.

Risk and Exploitability

The EPSS score indicates a very low probability of exploitation (<1%) and the vulnerability is not listed in CISA’s KEV catalog, implying no public exploits are known. However, the flaw can lead to kernel privilege escalation if an attacker can trigger the use‑after‑free, which would typically require local kernel access or the ability to initiate driver removal. Consequently, the overall risk is moderate for systems that load vulnerable remoteproc drivers without the patch.

Generated by OpenCVE AI on September 19, 2026 at 13:43 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest kernel patch that adds a deleting flag and cancels crash‑handler work prior to driver removal.
  • Reboot the system to ensure the updated kernel is active.
  • If the patch cannot be applied immediately, disable or unload nonessential remoteproc drivers until the patch is installed.

Generated by OpenCVE AI on September 19, 2026 at 13:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4817-1 linux-6.12 security update
Debian DSA Debian DSA DSA-6528-1 linux security update
History

Sat, 19 Sep 2026 14:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362
CWE-416

Thu, 17 Sep 2026 16:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: remoteproc: Prevent crash handling to race with rproc_del() There's no synchronization between rproc_crash_handler_work() and rproc_del(), as such it's possible for a driver to be removed while crash-handler work is scheduled, or even executing - resulting in use-after-free issues. To avoid this the scheduled work need to be cancelled and synchronized against before the removal proceeds. In order to ensure that this doesn't race with the reporting, and thereby scheduling new work, a "deleting" flag is introduced. This is similar to the RPROC_DELETE state that was introduced to ensure that "start" didn't race with rproc_del(), but the existing mechanism can not be used as it's valid to call rproc_report_crash() in atomic context - and the "state" is protected by a mutex. In the event that work is cancelled the pm_stay_awake() is left unbalanced and need to be unrolled. The blocking and cancelling of crash-handler work prior to the actual rproc_shutdown() call does have the explicit side-effect that crashes resulting from the shutdown process will not enter the crash-handling path, and as such will not generate devcoredumps etc. Due to the existing mutual exclusion between these code paths there's no concrete reduction in functionality, but further work would be needed to handle this case.
Title remoteproc: Prevent crash handling to race with rproc_del()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-17T16:09:51.759Z

Reserved: 2026-09-11T19:38:34.815Z

Link: CVE-2026-90431

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-17T17:17:48.110

Modified: 2026-09-17T17:17:48.110

Link: CVE-2026-90431

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-19T13:45:15Z

Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

  • CWE-416

    Use After Free