https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T23:20:15.262434+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2025-06265 bdu:2025-06265 2026-10-03T23:20:16.050558+00:00 bdu:2025-06265 https://cve.radiocsirt.org/vuln/bell-cve-2023-52993 BELL-CVE-2023-52993 2026-10-03T23:20:16.050671+00:00

Affected: Alpaquita:stream: linux-lts

 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0307 certfr-2025-avi-0307 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at… 2026-10-03T23:20:16.050704+00:00 certfr-2025-avi-0307 https://cve.radiocsirt.org/vuln/euvd-2026-311775 EUVD-2026-311775 2026-10-03T23:20:16.050722+00:00 EUVD-2026-311775 https://cve.radiocsirt.org/vuln/fkie_cve-2023-52993 fkie_cve-2023-52993 2026-10-03T23:20:16.050733+00:00

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

x86/i8259: Mark legacy PIC interrupts with IRQ_LEVEL

Baoquan reported that after triggering a crash the subsequent crash-kernel fails to boot about half of the time. It triggers a NULL pointer dereference in the periodic tick code.

This happens because the legacy timer interrupt (IRQ0) is resent in software which happens in soft interrupt (tasklet) context. In this context get_irq_regs() returns NULL which leads to the NULL pointer dereference.

The reason for the resend is a spurious APIC interrupt on the IRQ0 vector which is captured and leads to a resend when the legacy timer interrupt is enabled. This is wrong because the legacy PIC interrupts are level triggered and therefore should never be resent in software, but nothing ever sets the IRQ_LEVEL flag on those interrupts, so the core code does not know about their trigger type.

Ensure that IRQ_LEVEL is set when the legacy PCI interrupts are set up.

 https://cve.radiocsirt.org/vuln/ghsa-g7hp-hfwm-x3rp GHSA-g7hp-hfwm-x3rp 2026-10-03T23:20:16.050768+00:00

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

x86/i8259: Mark legacy PIC interrupts with IRQ_LEVEL

Baoquan reported that after triggering a crash the subsequent crash-kernel fails to boot about half of the time. It triggers a NULL pointer dereference in the periodic tick code.

This happens because the legacy timer interrupt (IRQ0) is resent in software which happens in soft interrupt (tasklet) context. In this context get_irq_regs() returns NULL which leads to the NULL pointer dereference.

The reason for the resend is a spurious APIC interrupt on the IRQ0 vector which is captured and leads to a resend when the legacy timer interrupt is enabled. This is wrong because the legacy PIC interrupts are level triggered and therefore should never be resent in software, but nothing ever sets the IRQ_LEVEL flag on those interrupts, so the core code does not know about their trigger type.

Ensure that IRQ_LEVEL is set when the legacy PCI interrupts are set up.

 https://cve.radiocsirt.org/vuln/rhsa-2023:6583 RHSA-2023:6583 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update 2026-10-03T23:20:16.050792+00:00

kernel: seg6: fix the iif in the IPv6 socket control block Kernel: race when faulting a device private page in memory manager kernel: use-after-free in l1oip timer handlers kernel: Rate limit overflow messages in r8152 in intr_callback kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c kernel: perf: Fix perf_pending_task() UaF kernel: gpiolib: fix memory leak in gpiochip_setup_dev() kernel: memcg: fix possible use-after-free in memcg_write_event_control() kernel: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths kernel: char: tpm: Protect tpm_pm_suspend with locks kernel: ixgbevf: Fix resource leak in ixgbevf_init_module() kernel: dax: make sure inodes are flushed before destroy cache kernel: watch_queue: Actually free the watch kernel: watch_queue: Fix NULL dereference in error cleanup kernel: rtc: pl031: fix rtc features null pointer dereference kernel: tpm: fix reference counting for struct tpm_chip kernel: NFSv4: Don't hold the layoutget locks across multiple RPC calls kernel: xprtrdma: treat all calls not a bcall when bc_serv is NULL kernel: net: ipv6: unexport __init-annotated seg6_hmac_init() kernel: af_unix: Fix a data-race in unix_dgram_peer_wake_me(). kernel: regulator: scmi: Fix refcount leak in scmi_regulator_probe kernel: mm/mempolicy: fix uninit-v…

 https://cve.radiocsirt.org/vuln/rhsa-2024:3421 RHSA-2024:3421 — Red Hat Security Advisory: kernel security and bug fix update 2026-10-03T23:20:16.051530+00:00

kernel: netfilter: nf_tables: netlink notifier might race to release objects kernel: netfilter: nf_tables: possible module reference underflow in error path kernel: netfilter: nf_tables: do not allow SET_ID to refer to another table kernel: Use-after-free in nft_verdict_dump due to a race between set GC and transaction kernel: Marvin vulnerability side-channel leakage in the RSA decryption operation kernel: inactive elements in nft_pipapo_walk kernel: netfilter: nftables: exthdr: fix 4-byte stack OOB write kernel: netfilter: nf_tables: don't skip expired elements during walk kernel: x86/i8259: Mark legacy PIC interrupts with IRQ_LEVEL kernel: Linux kernel: Denial of Service in netfilter due to improper garbage collection kernel: netfilter: nft_set_rbtree: fix null deref on element insertion kernel: netfilter: nf_tables: fix underflow in chain reference counter kernel: nf_tables: use-after-free vulnerability in the nft_verdict_init() function hw: amd: Instruction raise #VC exception at exit hw: amd: Instruction raise #VC exception at exit kernel: mlxsw: spectrum_acl_tcam: Fix stack corruption

 https://cve.radiocsirt.org/vuln/suse-su-2025:01983-1 SUSE-SU-2025:01983-1 — Security update for the Linux Kernel 2026-10-03T23:20:16.051582+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52993 UBUNTU-CVE-2023-52993 2026-10-03T23:20:16.051699+00:00

Affected: Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 148 more

In the Linux kernel, the following vulnerability has been resolved: x86/i8259: Mark legacy PIC interrupts with IRQ_LEVEL Baoquan reported that after triggering a crash the subsequent crash-kernel fails to boot about half of the time. It triggers a NULL pointer dereference in the periodic tick code. This happens because the legacy timer interrupt (IRQ0) is resent in software which happens in soft interrupt (tasklet) context. In this context get_irq_regs() returns NULL which leads to the NULL pointer dereference. The reason for the resend is a spurious APIC interrupt on the IRQ0 vector which is captured and leads to a resend when the legacy timer interrupt is enabled. This is wrong because the legacy PIC interrupts are level triggered and therefore should never be resent in software, but nothing ever sets the IRQ_LEVEL flag on those interrupts, so the core code does not know about their trigger type. Ensure that IRQ_LEVEL is set when the legacy PCI interrupts are set up.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0649 WID-SEC-W-2025-0649 — Linux Kernel: Mehrere Schwachstellen 2026-10-03T23:20:16.051912+00:00

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Effekte zu erzielen.