CVE-2026-98881

The Linux kernel contains a vulnerability in the bridge component where a stale rcu_barrier() in br_multicast_dev_del() causes extreme RTNL pressure . This issue originated from historical call_rcu() usage in net/bridge/br_multicast.c . The vulnerability has been resolved by removing the problema...

EUVD-2026-108675

In the Linux kernel, the following vulnerability has been resolved: net: bridge: remove stale rcubarrier in brmulticastdevdel This rcubarrier came from a time callrcu calls were used in net/bridge/brmulticast.c. Now kfreercu is there, we can remove this problematic rcubarrier which causes extreme...

CVE-2026-98880 ntfs3: handle set_blocksize failures

In the Linux kernel, the following vulnerability has been resolved: ntfs3: handle setblocksize failures ntfs3 uses bufferheads, which don't handle block size PAGESIZE well. Without this, mounting we will hit the BUGONoffset = foliosizefolio; in foliosetbh on the first breadgfp call...

EUVD-2026-108674

In the Linux kernel, the following vulnerability has been resolved: ntfs3: handle setblocksize failures ntfs3 uses bufferheads, which don't handle block size PAGESIZE well. Without this, mounting we will hit the BUGONoffset = foliosizefolio; in foliosetbh on the first breadgfp call...

CVE-2026-98880 ntfs3: handle set_blocksize failures

In the Linux kernel, the following vulnerability has been resolved: ntfs3: handle setblocksize failures ntfs3 uses bufferheads, which don't handle block size PAGESIZE well. Without this, mounting we will hit the BUGONoffset = foliosizefolio; in foliosetbh on the first breadgfp call...

CVE-2026-98880

The Linux kernel contains a vulnerability in the ntfs3 filesystem module regarding how it handles set_blocksize failures. The issue stems from ntfs3 using buffer_heads , which do not correctly manage block sizes exceeding PAGE_SIZE . This failure can trigger a BUG_ON(offset >= folio_size(folio...

CVE-2026-98880

In the Linux kernel, the following vulnerability has been resolved: ntfs3: handle setblocksize failures ntfs3 uses bufferheads, which don't handle block size PAGESIZE well. Without this, mounting we will hit the BUGONoffset = foliosizefolio; in foliosetbh on the first breadgfp call...

EUVD-2026-108673

In the Linux kernel, the following vulnerability has been resolved: isofs: handle setblocksize failures isofs uses bufferheads, which don't handle block size PAGESIZE well. Without this, mounting we will hit the BUGONoffset = foliosizefolio; in foliosetbh on the first breadgfp call...

CVE-2026-98879 isofs: handle set_blocksize failures

In the Linux kernel, the following vulnerability has been resolved: isofs: handle setblocksize failures isofs uses bufferheads, which don't handle block size PAGESIZE well. Without this, mounting we will hit the BUGONoffset = foliosizefolio; in foliosetbh on the first breadgfp call...

CVE-2026-98879

The Linux kernel contains a vulnerability in the isofs component where buffer_heads do not properly handle block sizes greater than PAGE_SIZE . This issue can lead to a BUG_ON(offset >= folio_size(folio)) error during the first __bread_gfp call in folio_set_bh when mounting. The provided docum...

CVE-2026-98879 isofs: handle set_blocksize failures

In the Linux kernel, the following vulnerability has been resolved: isofs: handle setblocksize failures isofs uses bufferheads, which don't handle block size PAGESIZE well. Without this, mounting we will hit the BUGONoffset = foliosizefolio; in foliosetbh on the first breadgfp call...

CVE-2026-98879

In the Linux kernel, the following vulnerability has been resolved: isofs: handle setblocksize failures isofs uses bufferheads, which don't handle block size PAGESIZE well. Without this, mounting we will hit the BUGONoffset = foliosizefolio; in foliosetbh on the first breadgfp call...

CVE-2026-98878 irqchip/gic-v5: Immediately exec priority drop following activate

In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v5: Immediately exec priority drop following activate With GICv5 an interrupt of equal or lower priority cannot be signalled until there has been a priority drop. This is done via the GIC CDEOI system instruction. Onc...

EUVD-2026-108672

In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v5: Immediately exec priority drop following activate With GICv5 an interrupt of equal or lower priority cannot be signalled until there has been a priority drop. This is done via the GIC CDEOI system instruction. Onc...

CVE-2026-98878 irqchip/gic-v5: Immediately exec priority drop following activate

In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v5: Immediately exec priority drop following activate With GICv5 an interrupt of equal or lower priority cannot be signalled until there has been a priority drop. This is done via the GIC CDEOI system instruction. Onc...

CVE-2026-98878

The Linux kernel 's GICv5 driver contains a vulnerability where the priority drop (via the GIC CDEOI system instruction) was incorrectly performed as part of irq_eoi(). Because all interrupts are programmed with the same priority, a long-running process—such as software-injected interrupts for a ...

CVE-2026-98877 irqchip/gic-v4: Don't advertise VLPIs if no ITS is probed

In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v4: Don't advertise VLPIs if no ITS is probed When accidentally setting “kvm-arm.vgicv4enable=1” on a system that has no MSI controller device tree node and GICv4, it results a panic as “gicdomain” is NULL and the...

CVE-2026-98877 irqchip/gic-v4: Don't advertise VLPIs if no ITS is probed

In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v4: Don't advertise VLPIs if no ITS is probed When accidentally setting “kvm-arm.vgicv4enable=1” on a system that has no MSI controller device tree node and GICv4, it results a panic as “gicdomain” is NULL and the...

EUVD-2026-108723

In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v4: Don't advertise VLPIs if no ITS is probed When accidentally setting “kvm-arm.vgicv4enable=1” on a system that has no MSI controller device tree node and GICv4, it results a panic as “gicdomain” is NULL and the...

CVE-2026-98877

The Linux kernel contains a vulnerability where setting kvm-arm.vgic_v4_enable=1 on a system with GICv4 but no MSI controller device tree node causes a kernel panic . The root cause is a NULL pointer dereference because the kernel attempts to access gic_domain when it is NULL. The fix involves se...