GHSA-2HX9-3CQH-FCJJ
Vulnerability from github – Published: 2026-09-16 12:30 – Updated: 2026-09-16 15:31In the Linux kernel, the following vulnerability has been resolved:
dmaengine: fsl-edma: tracing: no ptr dereference during log output
The fsl edma events store a pointer to a struct fsl_edma_engine in the ringbuffer and dereference it when a log entry is printed. At this time, the pointer may no longer be valid.
Event injection can be used to trigger a crash:
$ cd /sys/kernel/tracing $ echo 'value = 0' > events/fsl_edma/edma_writeb/inject $ cat trace
The log output needs only edma->membase. Add a membase field at the end of the event and use the new field for log output. Keep the existing fields for backward compatibility.
{
"affected": [],
"aliases": [
"CVE-2026-89994"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-16T11:17:10Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: fsl-edma: tracing: no ptr dereference during log output\n\nThe fsl edma events store a pointer to a struct fsl_edma_engine in the\nringbuffer and dereference it when a log entry is printed. At this time,\nthe pointer may no longer be valid.\n\nEvent injection can be used to trigger a crash:\n\n$ cd /sys/kernel/tracing\n$ echo \u0027value = 0\u0027 \u003e events/fsl_edma/edma_writeb/inject\n$ cat trace\n\nThe log output needs only edma-\u003emembase. Add a membase field at the end\nof the event and use the new field for log output. Keep the existing\nfields for backward compatibility.",
"id": "GHSA-2hx9-3cqh-fcjj",
"modified": "2026-09-16T15:31:04Z",
"published": "2026-09-16T12:30:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89994"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2a3801ae5c344473e648006c5b03a9216ac54a6a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2ea04dca8e627f722caa7a2037cfbae0257f3501"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d382aaf5fed38c6dd2e0cc710d97cb81d660ffa7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ef02cd3807f39ae1dbc924788d8fa6a85334c435"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
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.
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.
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.