{"id":"CVE-2026-89991","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix infinite loop in pcpu_freelist push with one possible CPU\n\n__pcpu_freelist_push() can loop forever when only one CPU is possible\nand an NMI re-enters pcpu_free…","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix infinite loop in pcpu_freelist push with one possible CPU\n\n__pcpu_freelist_push() can loop forever when only one CPU is possible\nand an NMI re-enters pcpu_free…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= f2ac0e5d1c4dcc55d6510dcaefb8f45661a9a1fb < a24a146ae2cb5d9faeea96d10010fcb6579abe1f","Linux >= f2ac0e5d1c4dcc55d6510dcaefb8f45661a9a1fb < a5b5e62baceff9e252c6535cf42a027d04f226cf","Linux >= f2ac0e5d1c4dcc55d6510dcaefb8f45661a9a1fb < efebf6496685c93150df5bb0794363ae70c5f58a","Linux 6.15"],"published":"2026-09-16","updated":"2026-09-16","sourceUpdated":"2026-09-16T11:17:10.240","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-89991","references":[{"url":"https://git.kernel.org/stable/c/a24a146ae2cb5d9faeea96d10010fcb6579abe1f","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/a5b5e62baceff9e252c6535cf42a027d04f226cf","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/efebf6496685c93150df5bb0794363ae70c5f58a","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-16T10:53:53.949Z","epss":0.00198,"epssPercentile":0.09826,"slug":"CVE-2026-89991","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix infinite loop in pcpu_freelist push with one possible CPU\n\n__pcpu_freelist_push() can loop forever when only one CPU is possible\nand an NMI re-enters pcpu_freelist_push() while the interrupted context\nholds that CPU's freelist lock.\n\nAfter the current-CPU fast path fails, the fallback loop walks\ncpu_possible_mask while skipping the current CPU. With CONFIG_SMP=n, or\nwhen an SMP kernel is limited to one possible CPU with nr_cpus=1 or\npossible_cpus=1, there are no other possible CPUs to examine. The loop\ntherefore makes no lock acquisition attempt and can never make progress.\n\nThe following stack was observed on a UP system:\n\n  NMI context:\n    pcpu_freelist_push\n    free_htab_elem\n    htab_map_delete_elem\n    [perf-event BPF program]\n    __perf_event_overflow\n    perf_event_nmi_handler\n    exc_nmi\n\n  Interrupted context:\n    __pcpu_freelist_push\n    pcpu_freelist_push\n    free_htab_elem\n    htab_map_delete_elem\n    [raw_tp/sys_enter BPF program]\n    __bpf_trace_sys_enter\n    do_syscall_64\n\nraw_res_spin_lock() detects the same-CPU recursive acquisition and\nreturns -EDEADLK, but the subsequent fallback loop has no candidate head\non a system with one possible CPU.\n\nRestore the extra fallback head that existed before the rqspinlock\nconversion. Keep the current-CPU fast path, then try the other possible\nCPUs and finally the extra head. The additional head lets a push, which\ncannot fail without losing a preallocated element, make progress when the\nonly per-CPU head is held by the interrupted context.\n\nAlso check the extra head from the pop path so that nodes placed there\ncan be reused.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}