https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T04:52:47.920387+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2025-15084 bdu:2025-15084 2026-10-04T04:52:48.048840+00:00 bdu:2025-15084 https://cve.radiocsirt.org/vuln/bell-cve-2023-52633 BELL-CVE-2023-52633 2026-10-04T04:52:48.048878+00:00

Affected: Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts

 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0334 certfr-2024-avi-0334 — De multiples vulnérabilités ont été découvertes dans <span class="textit">le noyau Linux de Debian</span>. Elles permet… 2026-10-04T04:52:48.048909+00:00 certfr-2024-avi-0334 https://cve.radiocsirt.org/vuln/euvd-2026-311596 EUVD-2026-311596 2026-10-04T04:52:48.048927+00:00 EUVD-2026-311596 https://cve.radiocsirt.org/vuln/fkie_cve-2023-52633 fkie_cve-2023-52633 2026-10-04T04:52:48.048939+00:00

In the Linux kernel, the following vulnerability has been resolved:

um: time-travel: fix time corruption

In 'basic' time-travel mode (without =inf-cpu or =ext), we still get timer interrupts. These can happen at arbitrary points in time, i.e. while in timer_read(), which pushes time forward just a little bit. Then, if we happen to get the interrupt after calculating the new time to push to, but before actually finishing that, the interrupt will set the time to a value that's incompatible with the forward, and we'll crash because time goes backwards when we do the forwarding.

Fix this by reading the time_travel_time, calculating the adjustment, and doing the adjustment all with interrupts disabled.

 https://cve.radiocsirt.org/vuln/ghsa-c7h5-f667-cvc5 GHSA-c7h5-f667-cvc5 2026-10-04T04:52:48.048970+00:00

In the Linux kernel, the following vulnerability has been resolved:

um: time-travel: fix time corruption

In 'basic' time-travel mode (without =inf-cpu or =ext), we still get timer interrupts. These can happen at arbitrary points in time, i.e. while in timer_read(), which pushes time forward just a little bit. Then, if we happen to get the interrupt after calculating the new time to push to, but before actually finishing that, the interrupt will set the time to a value that's incompatible with the forward, and we'll crash because time goes backwards when we do the forwarding.

Fix this by reading the time_travel_time, calculating the adjustment, and doing the adjustment all with interrupts disabled.

 https://cve.radiocsirt.org/vuln/gsd-2023-52633 gsd-2023-52633 2026-10-04T04:52:48.048991+00:00 gsd-2023-52633 https://cve.radiocsirt.org/vuln/oesa-2024-1622 OESA-2024-1622 — kernel security update 2026-10-04T04:52:48.049002+00:00

Affected: openEuler:22.03-LTS-SP3: kernel

The Linux Kernel, the operating system core itself. Security Fix(es): In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Harden accesses to the reset domains Accessing reset domains descriptors by the index upon the SCMI drivers requests through the SCMI reset operations interface can potentially lead to out-of-bound violations if the SCMI driver misbehave. Add an internal consistency check before any such domains descriptors accesses.(CVE-2022-48655) In the Linux kernel, the following vulnerability has been resolved: erofs: fix pcluster use-after-free on UP platforms During stress testing with CONFIG_SMP disabled, KASAN reports as below: ================================================================== BUG: KASAN: use-after-free in __mutex_lock+0xe5/0xc30 Read of size 8 at addr ffff8881094223f8 by task stress/7789 CPU: 0 PID: 7789 Comm: stress Not tainted 6.0.0-rc1-00002-g0d53d2e882f9 #3 Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 Call Trace: &lt;TASK&gt; .. __mutex_lock+0xe5/0xc30 .. z_erofs_do_read_page+0x8ce/0x1560 .. z_erofs_readahead+0x31c/0x580 .. Freed by task 7787 kasan_save_stack+0x1e/0x40 kasan_set_track+0x20/0x30 kasan_set_free_info+0x20/0x40 __kasan_slab_free+0x10c/0x190 kmem_cache_free+0xed/0x380 rcu_core+0x3d5/0xc90 __do_softirq+0x12d/0x389 Last potentially related work creation: kasan_save_stack+0x1e/0x40 __kasan_record_aux_stack+0x97/0xb0 call_rcu+0x3d/0x3f0 erofs_shr…

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52633 UBUNTU-CVE-2023-52633 2026-10-04T04:52:48.049428+00:00

Affected: Ubuntu:20.04:LTS: linux-aws-5.15, Ubuntu:20.04:LTS: linux-azure-5.15, Ubuntu:20.04:LTS: linux-gcp-5.15, Ubuntu:20.04:LTS: linux-gkeop-5.15, Ubuntu:20.04:LTS: linux-hwe-5.15, Ubuntu:20.04:LTS: linux-ibm-5.15, Ubuntu:20.04:LTS: linux-intel-iotg-5.15, Ubuntu:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:20.04:LTS: linux-nvidia-tegra-5.15, Ubuntu:20.04:LTS: linux-oracle-5.15 and 36 more

In the Linux kernel, the following vulnerability has been resolved: um: time-travel: fix time corruption In 'basic' time-travel mode (without =inf-cpu or =ext), we still get timer interrupts. These can happen at arbitrary points in time, i.e. while in timer_read(), which pushes time forward just a little bit. Then, if we happen to get the interrupt after calculating the new time to push to, but before actually finishing that, the interrupt will set the time to a value that's incompatible with the forward, and we'll crash because time goes backwards when we do the forwarding. Fix this by reading the time_travel_time, calculating the adjustment, and doing the adjustment all with interrupts disabled.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0749 WID-SEC-W-2024-0749 — Linux Kernel: Mehrere Schwachstellen 2026-10-04T04:52:48.049517+00:00

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service oder einen nicht näher spezifizierten Angriff durchzuführen.