https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 11:21:43 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-80927 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-80927 https://cve.radiocsirt.org/vuln/euvd-2026-366975 EUVD-2026-366975 https://cve.radiocsirt.org/vuln/euvd-2026-366975 https://cve.radiocsirt.org/vuln/fkie_cve-2026-80927 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>timekeeping: Check the return value of tk_get_aux_ts64 in __do_adjtimex()</p> <p>If the auxiliary clock is disabled during tk_get_aux_ts64() but is enabled before tks-&gt;clock_valid is checked, then uninitialized stackdata will be used in the calculations and indirectly leaked to userspace.</p> <p>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&#39;s responsibility to avoid this.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>timekeeping: Check the return value of tk_get_aux_ts64 in __do_adjtimex()</p> <p>If the auxiliary clock is disabled during tk_get_aux_ts64() but is enabled before tks-&gt;clock_valid is checked, then uninitialized stackdata will be used in the calculations and indirectly leaked to userspace.</p> <p>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&#39;s responsibility to avoid this.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-80927 https://cve.radiocsirt.org/vuln/ghsa-g365-rm76-m26c <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>timekeeping: Check the return value of tk_get_aux_ts64 in __do_adjtimex()</p> <p>If the auxiliary clock is disabled during tk_get_aux_ts64() but is enabled before tks-&gt;clock_valid is checked, then uninitialized stackdata will be used in the calculations and indirectly leaked to userspace.</p> <p>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&#39;s responsibility to avoid this.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>timekeeping: Check the return value of tk_get_aux_ts64 in __do_adjtimex()</p> <p>If the auxiliary clock is disabled during tk_get_aux_ts64() but is enabled before tks-&gt;clock_valid is checked, then uninitialized stackdata will be used in the calculations and indirectly leaked to userspace.</p> <p>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&#39;s responsibility to avoid this.</p> https://cve.radiocsirt.org/vuln/ghsa-g365-rm76-m26c https://cve.radiocsirt.org/vuln/opensuse-su-2026:11805-1 <p>kernel-devel-7.2.6-1.1 on GA media</p> <p>kernel-devel-7.2.6-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11805-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80927 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more</p> <p>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-&gt;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&#39;s responsibility to avoid this.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more</p> <p>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-&gt;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&#39;s responsibility to avoid this.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80927 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321