Answer in brief
CVE-2026-80927 records a Unknown severity vulnerability in timekeeping: Check the return value of tk_get_aux_ts64 in __do_adjtimex(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4eca49d0b621b314ac7c80f363932ec6f6c8abc8 <fecf1e37775269ad38c172b468ad4ecc3968aa63 || >=4eca49d0b621b314ac7c80f363932ec6f6c8abc8 <bc59dac50cb45a725f7a50760c7cc72a0964f722 || >=4eca49d0b621b314ac7c80f363932ec6f6c8abc8 <4b61084b11bcecce86d03804ff30f8d7b465593c | fecf1e37775269ad38c172b468ad4ecc3968aa63, bc59dac50cb45a725f7a50760c7cc72a0964f722, 4b61084b11bcecce86d03804ff30f8d7b465593c |
| Linux/Linuxgeneric | 6.17 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
In 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.
Quoted source text, attributed separately from HOL analysis.