Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 47de033918cd772146f7438aa04471c020b2dedc, 50f232c26298923d39a48dc8e03d1732e5a5dcf1, 61862ed651b2493573e6d2192d5640bc6616f5d0.

Low priority for now. Upgrade to Linux Linux 47de033918cd772146f7438aa04471c020b2dedc, 50f232c26298923d39a48dc8e03d1732e5a5dcf1, 61862ed651b2493573e6d2192d5640bc6616f5d0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Sep 17, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-90431

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.7affected
    • 8afd519c3470f685f964deebd61aa51d83cde90a and later · before 50f232c26298923d39a48dc8e03d1732e5a5dcf1affected · git
    • 8afd519c3470f685f964deebd61aa51d83cde90a and later · before 69af36f1fb7d24d287662fef6b2093bcf847a9dbaffected · git
    • 8afd519c3470f685f964deebd61aa51d83cde90a and later · before a8a62cb4d2f3fd6aa06e86f1711c62d2a4cf17d5affected · git
    • 8afd519c3470f685f964deebd61aa51d83cde90a and later · before 47de033918cd772146f7438aa04471c020b2dedcaffected · git
    • 8afd519c3470f685f964deebd61aa51d83cde90a and later · before a31d9562eeec5c4103c202fc87651f6e7d3d0035affected · git
    • 8afd519c3470f685f964deebd61aa51d83cde90a and later · before f15cde11298402f803d5dda9cb9f95eea3d2ca40affected · git
    • 8afd519c3470f685f964deebd61aa51d83cde90a and later · before 61862ed651b2493573e6d2192d5640bc6616f5d0affected · git
    • 8afd519c3470f685f964deebd61aa51d83cde90a and later · before 74ee3b2f5767447c57959994341e5b95f1079977affected · git
    • before 3.7not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-90429Sep 17, 2026 · iommu/tegra241-cmdqv: Synchronize the error ISR against VINTF (de)init
    31Monitor
  • ← EarlierCVE-2026-90430Sep 17, 2026 · iommu/tegra241-cmdqv: Publish an LVCMDQ only after it is fully initialized
    0Monitor
  • Later →CVE-2026-90432Sep 17, 2026 · sched_ext: Abort directly from the hardlockup handler
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux47de033918cd772146f7438aa04471c020b2dedcVendor (CNA)
Linux Linux50f232c26298923d39a48dc8e03d1732e5a5dcf1Vendor (CNA)
Linux Linux61862ed651b2493573e6d2192d5640bc6616f5d0Vendor (CNA)
Linux Linux69af36f1fb7d24d287662fef6b2093bcf847a9dbVendor (CNA)
Linux Linux74ee3b2f5767447c57959994341e5b95f1079977Vendor (CNA)
Linux Linuxa31d9562eeec5c4103c202fc87651f6e7d3d0035Vendor (CNA)
Linux Linuxa8a62cb4d2f3fd6aa06e86f1711c62d2a4cf17d5Vendor (CNA)
Linux Linuxf15cde11298402f803d5dda9cb9f95eea3d2ca40Vendor (CNA)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records