Skip to main content

Tag: Out of Memory

Errors due to Redis (or other) exhausting its configured RAM.

IDTitleDescriptionCategoryTechnologyTags
CRE-2025-0072
Critical
Impact: 10/10
Mitigation: 7/10
Redis Out-Of-Memory → Persistence Crash → Replica/ACL Write FailuresDetects a cascade of critical Redis failure modes in a single session: - Redis refuses writes when maxmemory is exceeded (OOM). - RDB snapshot (BGSAVE) fails (MISCONF) due to simulated full-disk. - Replica refuses writes (READONLY). - ACL denies a write (NOPERM).In-Memory Database ProblemsredisRedisOut of MemoryPersistenceRDBMISCONFREADONLYACLSecurity
CRE-2025-0137
High
Impact: 6/10
Mitigation: 2/10
Pod terminated with Exit Code 137 due to OOMKilled (memory limit exceeded)The container exceeded its memory limit and was killed by the kernel OOM killer. Kubernetes reports a terminated state with Reason=OOMKilled and exitCode=137. This often manifests as CrashLoopBackOff under sustained memory pressure.Memory ProblemskubernetesK8sExit CodeOut of MemoryMemoryCrash LoopReliability
CRE-2025-0162
High
Impact: 8/10
Mitigation: 7/10
Stable Diffusion WebUI CUDA Out of Memory CrashDetects critical CUDA out of memory errors in Stable Diffusion WebUI that cause image generation failures and application crashes. This occurs when GPU VRAM is exhausted during model loading or image generation, resulting in complete task failure and potential WebUI instability.Memory Problemsstable-diffusionMemoryNvidiaCrashOut of MemoryConfiguration
CRE-2025-0200
Critical
Impact: 10/10
Mitigation: 7/10
Redis Comprehensive Troubleshooting - Multiple Common Issues DetectionComprehensive detection rule for multiple common Redis troubleshooting scenarios including: 1. Out-of-Memory (OOM) errors when maxmemory limit exceeded 2. Connection timeouts and connectivity issues 3. Authentication failures and permission denials 4. Invalid commands and argument errors 5. Background save (BGSAVE) conflicts and persistence issues 6. Slow query performance problems 7. Read-only replica write attempts 8. Disk persistence failures (MISCONF errors) 9. Client connection limits exceeded 10. Memory pressure and eviction warningsIn-Memory Database ProblemsredisRedisRedis CLIRedis PyOut of MemoryConnectionAuthenticationPersistencePerformanceREADONLYMISCONFACLPublic
CRE-2025-0201
Critical
Impact: 10/10
Mitigation: 8/10
Redis Out-of-Memory Error - Maxmemory Limit ExceededDetects Redis out-of-memory errors when the maxmemory limit is reached and the configured eviction policy prevents new writes. This typically occurs when Redis is configured with 'noeviction' policy and memory usage exceeds the maxmemory setting, causing all write commands to fail.In-Memory Database ProblemsredisRedisOut of MemoryMax MemoryNo Eviction