27862 matches found
CVE-2026-94627
vLLM Mooncake connector (through version 0.29.0) fails to properly manage GPU KV cache block ownership when concurrent child requests share a single transfer ID in prefill/decode disaggregated deployments. An unauthenticated remote attacker can trigger GPU memory exhaustion by submitting completi...
SUSE CVE-2026-90239
In the Linux kernel, the following vulnerability has been resolved: media: amd: isp4: release partial allocations in isp4ifallocfwgpumem isp4ifallocfwgpumem allocates several GPU memory pools in sequence. If one of them fails, it jumps to errornomemory and returns -ENOMEM without releasing the...
SUSE CVE-2026-93180
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Fix NPD issue on partial unmap of an evicted BO This commit fixes the NULL pointer dereference issue that would have happened on the split of GPU mapping due to partial unmap of an evicted BO. There is a logic to...
USN-8793-1: Linux kernel (Azure CVM) vulnerabilities
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems: - Bluetooth drivers; - GPU drivers; - Hardware monitoring drivers; - SPI subsystem; - NTFS3 file system; - iouring...
PT-2026-96317
Name of the Vulnerable Software and Affected Versions vLLM versions prior to 0.29.1 Description The Mooncake connector fails to properly manage GPU KV cache block ownership during prefill/decode disaggregated deployments when concurrent child requests share a single transfer ID. An attacker can...
CVE-2026-94627: Missing Release of Memory after Effective Lifetime
vLLM Mooncake connector through 0.29.0 fails to properly manage GPU KV cache block ownership when concurrent child requests share a single transfer ID in prefill/decode disaggregated deployments. Attackers can trigger GPU memory exhaustion by submitting completion requests with multiple prompts,...
SUSE CVE-2026-89811
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Add TLB flush after MES queue eviction/suspension MES Micro Engine Scheduler does not perform heavy-weight TLB invalidation after unmapping queues, unlike HWS which does this automatically. This causes a race conditio...
CVE-2026-93840
vLLM before 0.29.0 validates allowedtokenids against tokenizer length instead of model output logits width in SamplingParams.validateallowedtokenids. Attackers can supply token IDs above the output vocabulary that pass validation, causing LogitBiasState to corrupt GPU logits state and allow...
PYSEC-2026-3998
vLLM before 0.29.0 validates allowedtokenids against tokenizer length instead of model output logits width in SamplingParams.validateallowedtokenids. Attackers can supply token IDs above the output vocabulary that pass validation, causing LogitBiasState to corrupt GPU logits state and allow...
PYSEC-0000-CVE-2026-93840
vLLM before 0.29.0 validates allowedtokenids against tokenizer length instead of model output logits width in SamplingParams.validateallowedtokenids. Attackers can supply token IDs above the output vocabulary that pass validation, causing LogitBiasState to corrupt GPU logits state and allow...
EUVD-2026-83284
vLLM before 0.29.0 validates allowedtokenids against tokenizer length instead of model output logits width in SamplingParams.validateallowedtokenids. Attackers can supply token IDs above the output vocabulary that pass validation, causing LogitBiasState to corrupt GPU logits state and allow...
CVE-2026-93840 vLLM before 0.29.0 Cross-Request Logits Corruption via allowed_token_ids
vLLM before 0.29.0 validates allowedtokenids against tokenizer length instead of model output logits width in SamplingParams.validateallowedtokenids. Attackers can supply token IDs above the output vocabulary that pass validation, causing LogitBiasState to corrupt GPU logits state and allow...
CVE-2026-93592 vLLM before 0.28.0 Denial of Service via negative token ID
vLLM versions before 0.28.0 fail to validate the lower bound of token IDs in the /v1/embeddings and /pooling endpoints, allowing unauthenticated attackers to crash the engine by submitting negative token IDs. A single request with a negative token ID triggers a CUDA device-side assertion that...
EUVD-2026-82911
vLLM versions before 0.28.0 fail to validate the lower bound of token IDs in the /v1/embeddings and /pooling endpoints, allowing unauthenticated attackers to crash the engine by submitting negative token IDs. A single request with a negative token ID triggers a CUDA device-side assertion that...
CLEANSTART-2026-EI49754 Security fix for GHSA-cx3h-4qpv-8hc9 applied in: airflow-2 2.10.3-r3, airflow-2 2.11.2-r4, airflow-3 3.1.8-r4, airflow-3 3.2.1-r4, tensorflow-gpu-jupyter 2.21.0-r7
GHSA-cx3h-4qpv-8hc9 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details...
CLEANSTART-2026-SI19530 Security fix for CVE-2026-44899 applied in: tensorflow-gpu-jupyter 2.21.0-r5
Security vulnerability affects the tensorflow-gpu-jupyter package. This issue is resolved in later releases. See references for vulnerability details...
CLEANSTART-2026-PO47077 Security fix for CVE-2026-44898 applied in: tensorflow-gpu-jupyter 2.21.0-r5
Security vulnerability affects the tensorflow-gpu-jupyter package. This issue is resolved in later releases. See references for vulnerability details...
CLEANSTART-2026-DO33300 Security fix for CVE-2026-44897 applied in: tensorflow-gpu-jupyter 2.21.0-r5
Security vulnerability affects the tensorflow-gpu-jupyter package. This issue is resolved in later releases. See references for vulnerability details...
CLEANSTART-2026-CB04703 Security fix for CVE-2026-42557 applied in: tensorflow-gpu-jupyter 2.21.0-r5
Security vulnerability affects the tensorflow-gpu-jupyter package. This issue is resolved in later releases. See references for vulnerability details...
CLEANSTART-2026-RE32707 Security fix for CVE-2026-33079 applied in: tensorflow-gpu-jupyter 2.21.0-r5
Security vulnerability affects the tensorflow-gpu-jupyter package. This issue is resolved in later releases. See references for vulnerability details...