GHSA-6854-F26P-XX8R
Vulnerability from github – Published: 2026-10-18 18:32 – Updated: 2026-10-18 18:32In the Linux kernel, the following vulnerability has been resolved:
serial: core: fix NULL pointer dereference in serial_core_unregister_port()
port->port_dev is NULL when no port device is installed: it is cleared on teardown, and never set if registration failed before serial_core_port_device_add(). serial_core_unregister_port() passes it straight to serial_core_get_ctrl_dev(), which dereferences it:
KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047] RIP: serial_core_unregister_port Call Trace: serial8250_unregister_port serial8250_remove unbind_store
Return early when there is no port device, and read port->port_dev under port_mutex.
Also clear port->port_dev on the serial_core_register_port() error path, where the port device has already been removed.
{
"affected": [],
"aliases": [
"CVE-2026-98747"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:28Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nserial: core: fix NULL pointer dereference in serial_core_unregister_port()\n\nport-\u003eport_dev is NULL when no port device is installed: it is cleared\non teardown, and never set if registration failed before\nserial_core_port_device_add(). serial_core_unregister_port() passes it\nstraight to serial_core_get_ctrl_dev(), which dereferences it:\n\n KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]\n RIP: serial_core_unregister_port\n Call Trace:\n serial8250_unregister_port\n serial8250_remove\n unbind_store\n\nReturn early when there is no port device, and read port-\u003eport_dev\nunder port_mutex.\n\nAlso clear port-\u003eport_dev on the serial_core_register_port() error\npath, where the port device has already been removed.",
"id": "GHSA-6854-f26p-xx8r",
"modified": "2026-10-18T18:32:02Z",
"published": "2026-10-18T18:32:02Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98747"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/499485a67fbacf4d9afbdb43522388c64f853428"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/54abbb862366dcaf1f22f1e968358147b7d0547d"
}
],
"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.