PULSE
FEED
ransomdeadlock reclama a Hensel Elektrik · DE · Manufacturingransomrhysida reclama a Sanders Law Group · Professional Servicesransomqilin reclama a Miljaus Producciones S.L (www.miljaus.com) · ES · Otherransomqilin reclama a von Schaewen · DE · Otherransomn0n reclama a Company #110 · ES · Not Foundransomchaos reclama a mickeybody.com · US · Retail & E-Commerceransomaurora reclama a ARX Group SA · CH · Otherransomwhitearmor reclama a whitearmor.cc · Technologyransomlockbit5 reclama a dorsiacademy.it · IT · Educationransomlockbit5 reclama a mlh.com.lb · LB · Professional Servicesransomlockbit5 reclama a lidoway.com · LI · Not Foundransomlockbit5 reclama a zelsior.es · ES · Not Foundransomemperador reclama a JS Constructor, INC · US · Manufacturingransomwhitearmor reclama a Whirlpool · US · Manufacturingransomdeadlock reclama a Hensel Elektrik · DE · Manufacturingransomrhysida reclama a Sanders Law Group · Professional Servicesransomqilin reclama a Miljaus Producciones S.L (www.miljaus.com) · ES · Otherransomqilin reclama a von Schaewen · DE · Otherransomn0n reclama a Company #110 · ES · Not Foundransomchaos reclama a mickeybody.com · US · Retail & E-Commerceransomaurora reclama a ARX Group SA · CH · Otherransomwhitearmor reclama a whitearmor.cc · Technologyransomlockbit5 reclama a dorsiacademy.it · IT · Educationransomlockbit5 reclama a mlh.com.lb · LB · Professional Servicesransomlockbit5 reclama a lidoway.com · LI · Not Foundransomlockbit5 reclama a zelsior.es · ES · Not Foundransomemperador reclama a JS Constructor, INC · US · Manufacturingransomwhitearmor reclama a Whirlpool · US · Manufacturing
← Todos los CVEs
CVE Watch23 oct 2026

CVE-2026-98888

In the Linux kernel, the following vulnerability has been resolved: arm64: kprobes: Allow reentering kprobes while single-stepping A kprob

CVSS

—

Sin CVSS

EPSS

—

KEV

—

Exploit Today

—

0-100

Publicado: 23 oct 2026 · Última mod.: 23 oct 2026

EPSS · 30d

Sin historial EPSS suficiente todavía.

Descripción técnica

In the Linux kernel, the following vulnerability has been resolved: arm64: kprobes: Allow reentering kprobes while single-stepping A kprobe can be hit while another kprobe is in KPROBE_HIT_SS state. This can happen when tracing or perf code runs from the debug exception path while the first kprobe is preparing or executing its out-of-line single-step instruction. Currently arm64 treats a kprobe hit in KPROBE_HIT_SS as unrecoverable, the same as a hit in KPROBE_REENTER. This is too strict. A hit in KPROBE_HIT_SS is still a one-level reentry and can be handled by saving the current kprobe state and setting up single-step for the new probe, just like reentry from KPROBE_HIT_ACTIVE or KPROBE_HIT_SSDONE. The truly unrecoverable case is hitting another kprobe while already in KPROBE_REENTER, because the reentry save area has already been consumed. Move KPROBE_HIT_SS to the recoverable reentry cases and leave KPROBE_REENTER as the unrecoverable nested reentry case. This change also requires saving saved_irqflag in struct prev_kprobe. When a nested kprobe calls kprobes_save_local_irqflag(), it overwrites kcb->saved_irqflag with the currently masked DAIF value, losing the outer kprobe's original DAIF state. Without this fix, when the outer kprobe's single-step finishes, kprobes_restore_local_irqflag() applies the wrong DAIF mask and leaves interrupts permanently disabled. Extend struct prev_kprobe with a saved_irqflag field and save/restore it alongside kp and status. This ensures the outer kprobe's original interrupt state is preserved across reentry. This mirrors the x86 fix in commit 6a5022a56ac3 ("kprobes/x86: Allow to handle reentered kprobe on single-stepping").

Referencias oficiales
CVEs relacionados

Sin CVEs relacionados por CWE o producto.