EUVD-2025-203841

On affected platforms running Arista EOS with OSPFv3 configured, a specially crafted packet can cause the OSFPv3 process to have high CPU utilization which may result in the OSFPv3 process being restarted. This may cause disruption in the OSFPv3 routes on the switch. This issue was discovered...

CVE-2025-8872

On affected platforms running Arista EOS with OSPFv3 configured, a specially crafted packet can cause the OSFPv3 process to have high CPU utilization which may result in the OSFPv3 process being restarted. This may cause disruption in the OSFPv3 routes on the switch. This issue was discovered...

CVE-2025-8872

This CVE affects Arista EOS with OSPFv3 configured. A specially crafted IPv6 OSPFv3 packet can cause the ospfv3 process to have high CPU utilization, potentially restarting the process and disrupting OSPFv3 routes. The Arista advisory lists affected EOS trains: 4.34.x (4.34.1F and below), 4.33.x ...

CVE-2025-68313

CVE-2025-68313 refers to a Linux kernel issue in x86/CPU/AMD: Zen5 RDSEED output variants (16-/32-bit) that could return 0 with CF=1. The advisory states a fix was added: a glue layer that checks microcode revisions, preventing inconsistent randomness and signaling. The CVE’s CVSS v3.1 metrics fr...

EUVD-2025-203748

In the Linux kernel, the following vulnerability has been resolved: crypto: zstd - fix double-free in per-CPU stream cleanup The crypto/zstd module has a double-free bug that occurs when multiple tfms are allocated and freed. The issue happens because zstdstreams per-CPU contexts are freed in...

EUVD-2025-203701

In the Linux kernel, the following vulnerability has been resolved: x86/CPU/AMD: Add missing terminator for zen5rdseedmicrocode Running x86matchminmicrocoderev on a Zen5 CPU trips up KASAN for an out of bounds access...

EUVD-2025-203719

In the Linux kernel, the following vulnerability has been resolved: cpufreq/longhaul: handle NULL policy in longhaulexit longhaulexit was calling cpufreqcpuget0 without checking for a NULL policy pointer. On some systems, this could lead to a NULL dereference and a kernel warning or panic. This...

EUVD-2025-203641

In the Linux kernel, the following vulnerability has been resolved: archtopology: Fix incorrect error check in topologyparsecpucapacity Fix incorrect use of PTRERRORZERO in topologyparsecpucapacity which causes the code to proceed with NULL clock pointers. The current logic uses !PTRERRORZEROcpuc...

UBUNTU-CVE-2025-68262

In the Linux kernel, the following vulnerability has been resolved: crypto: zstd - fix double-free in per-CPU stream cleanup The crypto/zstd module has a double-free bug that occurs when multiple tfms are allocated and freed. The issue happens because zstdstreams per-CPU contexts are freed in...

UBUNTU-CVE-2025-68244

In the Linux kernel, the following vulnerability has been resolved: drm/i915: Avoid lock inversion when pinning to GGTT on CHV/BXT+VTD On completion of i915vmapinww, a synchronous variant of dmafenceworkcommit is called. When pinning a VMA to GGTT address space on a Cherry View family processor, ...

CVE-2025-68262 crypto: zstd - fix double-free in per-CPU stream cleanup

In the Linux kernel, the following vulnerability has been resolved: crypto: zstd - fix double-free in per-CPU stream cleanup The crypto/zstd module has a double-free bug that occurs when multiple tfms are allocated and freed. The issue happens because zstdstreams per-CPU contexts are freed in...

CVE-2025-68244

Technical details for CVE-2025-68244 are not publicly available in the provided documents; monitor for updates.

AZL-72419 CVE-2025-68211 affecting package kernel for versions less than 6.6.121.1-1

In the Linux kernel, the following vulnerability has been resolved: ksm: use range-walk function to jump over holes in scangetnextrmapitem Currently, scangetnextrmapitem walks every page address in a VMA to locate mergeable pages. This becomes highly inefficient when scanning large virtual memory...

CVE-2025-68195

In the Linux kernel, the following vulnerability has been resolved: x86/CPU/AMD: Add missing terminator for zen5rdseedmicrocode Running x86matchminmicrocoderev on a Zen5 CPU trips up KASAN for an out of bounds access...

CVE-2025-40346

In the Linux kernel, the following vulnerability has been resolved: archtopology: Fix incorrect error check in topologyparsecpucapacity Fix incorrect use of PTRERRORZERO in topologyparsecpucapacity which causes the code to proceed with NULL clock pointers. The current logic uses !PTRERRORZEROcpuc...

CVE-2025-40346

In the Linux kernel, the following vulnerability has been resolved: archtopology: Fix incorrect error check in topologyparsecpucapacity Fix incorrect use of PTRERRORZERO in topologyparsecpucapacity which causes the code to proceed with NULL clock pointers. The current logic uses !PTRERRORZEROcpuc...

UBUNTU-CVE-2025-40346

In the Linux kernel, the following vulnerability has been resolved: archtopology: Fix incorrect error check in topologyparsecpucapacity Fix incorrect use of PTRERRORZERO in topologyparsecpucapacity which causes the code to proceed with NULL clock pointers. The current logic uses !PTRERRORZEROcpuc...

CVE-2025-68177

CVE-2025-68177: In Linux kernel, cpufreq/longhaul: longhaul_exit improperly dereferenced a NULL policy pointer. The fix adds an unlikely() guard and early return when policy is NULL, with upstream patchset released in kernel 6.6.120. Mageia OSVs indicate updated kernel packages (6.6.120) addressi...

CVE-2025-40346 arch_topology: Fix incorrect error check in topology_parse_cpu_capacity()

In the Linux kernel, the following vulnerability has been resolved: archtopology: Fix incorrect error check in topologyparsecpucapacity Fix incorrect use of PTRERRORZERO in topologyparsecpucapacity which causes the code to proceed with NULL clock pointers. The current logic uses !PTRERRORZEROcpuc...

CVE-2025-40346

The connected sources confirm CVE-2025-40346 affects the Linux kernel and describe the root cause as an incorrect error check in topology_parse_cpu_capacity that used PTR_ERR_OR_ZERO, causing clk_get_rate() to be called with NULL. The recommended fix is to use IS_ERR_OR_NULL instead of PTR_ERR_OR...