GHSA-3M6C-788W-H698
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
serial: core: do fallible allocations before the console can be registered
serial_core_add_one_port() allocates uport->tty_groups after uart_configure_port(), which may register the console. If the allocation fails, the driver unwinds the port while its console remains registered. The earlier uport->name allocation has a related failure path that leaves state->uart_port linked to a port being freed.
Failslab reproduced a NULL dereference in PL011 console output and a KASAN use-after-free in i.MX console output after failed binds.
Allocate the name and tty_groups before linking the port and configuring it. Reserve space for the optional driver attribute group because config_port() may populate uport->attr_group during configuration.
{
"affected": [],
"aliases": [
"CVE-2026-90337"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:32Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nserial: core: do fallible allocations before the console can be registered\n\nserial_core_add_one_port() allocates uport-\u003etty_groups after\nuart_configure_port(), which may register the console. If the allocation\nfails, the driver unwinds the port while its console remains registered.\nThe earlier uport-\u003ename allocation has a related failure path that leaves\nstate-\u003euart_port linked to a port being freed.\n\nFailslab reproduced a NULL dereference in PL011 console output and a KASAN\nuse-after-free in i.MX console output after failed binds.\n\nAllocate the name and tty_groups before linking the port and configuring\nit. Reserve space for the optional driver attribute group because\nconfig_port() may populate uport-\u003eattr_group during configuration.",
"id": "GHSA-3m6c-788w-h698",
"modified": "2026-09-17T18:32:01Z",
"published": "2026-09-17T18:32:01Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90337"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1a0e4fbce5d9c1bc179a35a2fd9ed142664299e3"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c2aec15f78b2e6ccd9b94216a901248511355982"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.