FKIE_CVE-2026-90431
Vulnerability from fkie_nvd - Published: 2026-09-17 17:17 - Updated: 2026-09-17 17:17
Severity
Summary
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.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/remoteproc/remoteproc_core.c",
"drivers/remoteproc/remoteproc_sysfs.c",
"include/linux/remoteproc.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "50f232c26298923d39a48dc8e03d1732e5a5dcf1",
"status": "affected",
"version": "8afd519c3470f685f964deebd61aa51d83cde90a",
"versionType": "git"
},
{
"lessThan": "69af36f1fb7d24d287662fef6b2093bcf847a9db",
"status": "affected",
"version": "8afd519c3470f685f964deebd61aa51d83cde90a",
"versionType": "git"
},
{
"lessThan": "a8a62cb4d2f3fd6aa06e86f1711c62d2a4cf17d5",
"status": "affected",
"version": "8afd519c3470f685f964deebd61aa51d83cde90a",
"versionType": "git"
},
{
"lessThan": "47de033918cd772146f7438aa04471c020b2dedc",
"status": "affected",
"version": "8afd519c3470f685f964deebd61aa51d83cde90a",
"versionType": "git"
},
{
"lessThan": "a31d9562eeec5c4103c202fc87651f6e7d3d0035",
"status": "affected",
"version": "8afd519c3470f685f964deebd61aa51d83cde90a",
"versionType": "git"
},
{
"lessThan": "f15cde11298402f803d5dda9cb9f95eea3d2ca40",
"status": "affected",
"version": "8afd519c3470f685f964deebd61aa51d83cde90a",
"versionType": "git"
},
{
"lessThan": "61862ed651b2493573e6d2192d5640bc6616f5d0",
"status": "affected",
"version": "8afd519c3470f685f964deebd61aa51d83cde90a",
"versionType": "git"
},
{
"lessThan": "74ee3b2f5767447c57959994341e5b95f1079977",
"status": "affected",
"version": "8afd519c3470f685f964deebd61aa51d83cde90a",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/remoteproc/remoteproc_core.c",
"drivers/remoteproc/remoteproc_sysfs.c",
"include/linux/remoteproc.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "3.7"
},
{
"lessThan": "3.7",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.270",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.221",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.188",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.157",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.110",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.52",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.6",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nremoteproc: Prevent crash handling to race with rproc_del()\n\nThere\u0027s no synchronization between rproc_crash_handler_work() and\nrproc_del(), as such it\u0027s possible for a driver to be removed while\ncrash-handler work is scheduled, or even executing - resulting in\nuse-after-free issues.\n\nTo avoid this the scheduled work need to be cancelled and synchronized\nagainst before the removal proceeds.\n\nIn order to ensure that this doesn\u0027t race with the reporting, and\nthereby scheduling new work, a \"deleting\" flag is introduced. This is\nsimilar to the RPROC_DELETE state that was introduced to ensure that\n\"start\" didn\u0027t race with rproc_del(), but the existing mechanism can not\nbe used as it\u0027s valid to call rproc_report_crash() in atomic context -\nand the \"state\" is protected by a mutex.\n\nIn the event that work is cancelled the pm_stay_awake() is left\nunbalanced and need to be unrolled.\n\nThe blocking and cancelling of crash-handler work prior to the actual\nrproc_shutdown() call does have the explicit side-effect that crashes\nresulting from the shutdown process will not enter the crash-handling\npath, and as such will not generate devcoredumps etc. Due to the\nexisting mutual exclusion between these code paths there\u0027s no concrete\nreduction in functionality, but further work would be needed to handle\nthis case."
}
],
"id": "CVE-2026-90431",
"lastModified": "2026-09-17T17:17:48.110",
"metrics": {},
"published": "2026-09-17T17:17:48.110",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/47de033918cd772146f7438aa04471c020b2dedc"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/50f232c26298923d39a48dc8e03d1732e5a5dcf1"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/61862ed651b2493573e6d2192d5640bc6616f5d0"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/69af36f1fb7d24d287662fef6b2093bcf847a9db"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/74ee3b2f5767447c57959994341e5b95f1079977"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/a31d9562eeec5c4103c202fc87651f6e7d3d0035"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/a8a62cb4d2f3fd6aa06e86f1711c62d2a4cf17d5"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/f15cde11298402f803d5dda9cb9f95eea3d2ca40"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…