GHSA-HF69-JX63-P85X
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
printk: Fix possible console use-after-free
When emitting a record via legacy printing, it is possible that a handover to another legacy printing context occurs. When a context has performed a handover, the console SRCU read lock is released and the pointer to the console struct might now be invalid. Therefore, after calling nbcon_legacy_emit_next_record() or console_emit_next_record(), it is necessary to check if a handover occurred before further @con usage.
Sashiko pointed out that console_flush_one_record() was not doing this.
In console_flush_one_record(), after emitting a record, move the further usage of @con after the handover check.
{
"affected": [],
"aliases": [
"CVE-2026-93134"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:18:08Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nprintk: Fix possible console use-after-free\n\nWhen emitting a record via legacy printing, it is possible that a handover\nto another legacy printing context occurs. When a context has performed a\nhandover, the console SRCU read lock is released and the pointer to the\nconsole struct might now be invalid. Therefore, after calling\nnbcon_legacy_emit_next_record() or console_emit_next_record(), it is\nnecessary to check if a handover occurred _before_ further @con usage.\n\nSashiko pointed out that console_flush_one_record() was not doing this.\n\nIn console_flush_one_record(), after emitting a record, move the further\nusage of @con after the handover check.",
"id": "GHSA-hf69-jx63-p85x",
"modified": "2026-09-17T18:32:11Z",
"published": "2026-09-17T18:32:11Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93134"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/36630cafbeede0b64c370edb2f7b4094327ee1e0"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8f194dee0c0d1223255bae1429e1939882f540fc"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f0104a7b730de32eefb3d4a27279592b5504ad59"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fbf9bb81b21537ede387a31cc586f1d2ce66a74e"
}
],
"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.