GHSA-G9XP-WHRX-5GJH
Vulnerability from github – Published: 2026-10-23 12:31 – Updated: 2026-10-23 12:31In the Linux kernel, the following vulnerability has been resolved:
serial: 8250_port: recognize UPIO_AU
My MIPS Alchemy systems generate the following warning during probe of the 8250 driver:
WARNING: drivers/tty/serial/8250/8250_port.c:462 at set_io_from_upio+0xfc/0x124, CPU#0: swapper/0/1 Unsupported UART type 4 [...] [<80521d40>] set_io_from_upio+0xfc/0x124 [<80521dfc>] serial8250_set_defaults+0x94/0xe0 [<80520fb4>] serial8250_register_8250_port+0x288/0x51c [<805214ec>] serial8250_probe+0x160/0x1e8 [<8053b5f0>] platform_probe+0x64/0x90
The least invasive fix is to recognize UPIO_AU (type 4) in set_io_from_upio() and do nothing, since all parameters have already been set up in 8250_rt288x.c::au_platform_setup().
Run-tested on Alchemy Au1300 platform.
{
"affected": [],
"aliases": [
"CVE-2026-98883"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-23T12:18:21Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nserial: 8250_port: recognize UPIO_AU\n\nMy MIPS Alchemy systems generate the following warning during\nprobe of the 8250 driver:\n\nWARNING: drivers/tty/serial/8250/8250_port.c:462 at set_io_from_upio+0xfc/0x124, CPU#0: swapper/0/1\nUnsupported UART type 4\n[...]\n[\u003c80521d40\u003e] set_io_from_upio+0xfc/0x124\n[\u003c80521dfc\u003e] serial8250_set_defaults+0x94/0xe0\n[\u003c80520fb4\u003e] serial8250_register_8250_port+0x288/0x51c\n[\u003c805214ec\u003e] serial8250_probe+0x160/0x1e8\n[\u003c8053b5f0\u003e] platform_probe+0x64/0x90\n\nThe least invasive fix is to recognize UPIO_AU (type 4) in set_io_from_upio()\nand do nothing, since all parameters have already been set up in\n8250_rt288x.c::au_platform_setup().\n\nRun-tested on Alchemy Au1300 platform.",
"id": "GHSA-g9xp-whrx-5gjh",
"modified": "2026-10-23T12:31:36Z",
"published": "2026-10-23T12:31:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98883"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/49fa670efdfdd27e29145cbd2beef065c08717ef"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9f67997353caa29c6a080789a1fb6e01fb50c118"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
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.