Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-90431remoteproc: Prevent crash handling to race with rproc_del()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 8afd519c3470f685f964deebd61aa51d83cde90a – < 50f232c26298923d39a48dc8e03d1732e5a5dcf1
    • affected 8afd519c3470f685f964deebd61aa51d83cde90a – < 69af36f1fb7d24d287662fef6b2093bcf847a9db
    • affected 8afd519c3470f685f964deebd61aa51d83cde90a – < a8a62cb4d2f3fd6aa06e86f1711c62d2a4cf17d5
    • affected 8afd519c3470f685f964deebd61aa51d83cde90a – < 47de033918cd772146f7438aa04471c020b2dedc
    • affected 8afd519c3470f685f964deebd61aa51d83cde90a – < a31d9562eeec5c4103c202fc87651f6e7d3d0035
    • affected 8afd519c3470f685f964deebd61aa51d83cde90a – < f15cde11298402f803d5dda9cb9f95eea3d2ca40
    • affected 8afd519c3470f685f964deebd61aa51d83cde90a – < 61862ed651b2493573e6d2192d5640bc6616f5d0
    • affected 8afd519c3470f685f964deebd61aa51d83cde90a – < 74ee3b2f5767447c57959994341e5b95f1079977
  • Linux · Linux

    • affected 3.7
    • unaffected < 3.7
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90431 badge
[![CVE-2026-90431](https://cveledger.app/badge/CVE-2026-90431.svg)](https://cveledger.app/cve/CVE-2026-90431)

Record last updated .