Production teams running Postgres or Redis set /proc/PID/oom_score_adj to -1000 specifically to survive the badness-score algorithm in Linux's mm/oom_kill.c that you're reading here. Misjudging how CAP_SYS_ADMIN or oom_score_adj shifts that score is exactly why the wrong process — sometimes the database instead of the runaway script — gets SIGKILLed during real production incidents.