GHSA-G365-RM76-M26C
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-11 21:31In the Linux kernel, the following vulnerability has been resolved:
timekeeping: Check the return value of tk_get_aux_ts64 in __do_adjtimex()
If the auxiliary clock is disabled during tk_get_aux_ts64() but is enabled before tks->clock_valid is checked, then uninitialized stackdata will be used in the calculations and indirectly leaked to userspace.
The same race window also exists after this change and also for the core timekeeper. But in these cases the only effect would be incorrect adjustments and this is userspace's responsibility to avoid this.
{
"affected": [],
"aliases": [
"CVE-2026-80927"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:18:56Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ntimekeeping: Check the return value of tk_get_aux_ts64 in __do_adjtimex()\n\nIf the auxiliary clock is disabled during tk_get_aux_ts64() but is enabled\nbefore tks-\u003eclock_valid is checked, then uninitialized stackdata will be\nused in the calculations and indirectly leaked to userspace.\n\nThe same race window also exists after this change and also for the core\ntimekeeper. But in these cases the only effect would be incorrect\nadjustments and this is userspace\u0027s responsibility to avoid this.",
"id": "GHSA-g365-rm76-m26c",
"modified": "2026-09-11T21:31:19Z",
"published": "2026-09-11T21:31:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80927"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4b61084b11bcecce86d03804ff30f8d7b465593c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bc59dac50cb45a725f7a50760c7cc72a0964f722"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fecf1e37775269ad38c172b468ad4ecc3968aa63"
}
],
"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.