https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 24 Oct 2026 22:49:11 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-98888 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>arm64: kprobes: Allow reentering kprobes while single-stepping</p> <p>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.</p> <p>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.</p> <p>The truly unrecoverable case is hitting another kprobe while already in KPROBE_REENTER, because the reentry save area has already been consumed.</p> <p>Move KPROBE_HIT_SS to the recoverable reentry cases and leave KPROBE_REENTER as the unrecoverable nested reentry case.</p> <p>This change also requires saving saved_irqflag in struct prev_kprobe. When a nested kprobe calls kprobes_save_local_irqflag(), it overwrites kcb-&gt;saved_irqflag with the currently masked DAIF value, losing the outer kprobe&#39;s original DAIF state. Without this fix, when the outer kprobe&#39;s single-step finishes, kprobes_restore_local_irqflag() applies the wrong DAIF mask and leaves interrupts permanently disabled.</p> <p>Extend struct prev_kprobe with a saved_irqflag field and save/restore it alongside kp and status. This ens…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>arm64: kprobes: Allow reentering kprobes while single-stepping</p> <p>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.</p> <p>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.</p> <p>The truly unrecoverable case is hitting another kprobe while already in KPROBE_REENTER, because the reentry save area has already been consumed.</p> <p>Move KPROBE_HIT_SS to the recoverable reentry cases and leave KPROBE_REENTER as the unrecoverable nested reentry case.</p> <p>This change also requires saving saved_irqflag in struct prev_kprobe. When a nested kprobe calls kprobes_save_local_irqflag(), it overwrites kcb-&gt;saved_irqflag with the currently masked DAIF value, losing the outer kprobe&#39;s original DAIF state. Without this fix, when the outer kprobe&#39;s single-step finishes, kprobes_restore_local_irqflag() applies the wrong DAIF mask and leaves interrupts permanently disabled.</p> <p>Extend struct prev_kprobe with a saved_irqflag field and save/restore it alongside kp and status. This ens…</p> https://db.gcve.eu/vuln/fkie_cve-2026-98888 https://db.gcve.eu/vuln/ghsa-g4px-h95h-7mgm <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>arm64: kprobes: Allow reentering kprobes while single-stepping</p> <p>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.</p> <p>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.</p> <p>The truly unrecoverable case is hitting another kprobe while already in KPROBE_REENTER, because the reentry save area has already been consumed.</p> <p>Move KPROBE_HIT_SS to the recoverable reentry cases and leave KPROBE_REENTER as the unrecoverable nested reentry case.</p> <p>This change also requires saving saved_irqflag in struct prev_kprobe. When a nested kprobe calls kprobes_save_local_irqflag(), it overwrites kcb-&gt;saved_irqflag with the currently masked DAIF value, losing the outer kprobe&#39;s original DAIF state. Without this fix, when the outer kprobe&#39;s single-step finishes, kprobes_restore_local_irqflag() applies the wrong DAIF mask and leaves interrupts permanently disabled.</p> <p>Extend struct prev_kprobe with a saved_irqflag field and save/restore it alongside kp and status. This ens…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>arm64: kprobes: Allow reentering kprobes while single-stepping</p> <p>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.</p> <p>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.</p> <p>The truly unrecoverable case is hitting another kprobe while already in KPROBE_REENTER, because the reentry save area has already been consumed.</p> <p>Move KPROBE_HIT_SS to the recoverable reentry cases and leave KPROBE_REENTER as the unrecoverable nested reentry case.</p> <p>This change also requires saving saved_irqflag in struct prev_kprobe. When a nested kprobe calls kprobes_save_local_irqflag(), it overwrites kcb-&gt;saved_irqflag with the currently masked DAIF value, losing the outer kprobe&#39;s original DAIF state. Without this fix, when the outer kprobe&#39;s single-step finishes, kprobes_restore_local_irqflag() applies the wrong DAIF mask and leaves interrupts permanently disabled.</p> <p>Extend struct prev_kprobe with a saved_irqflag field and save/restore it alongside kp and status. This ens…</p> https://db.gcve.eu/vuln/ghsa-g4px-h95h-7mgm https://db.gcve.eu/vuln/msrc_cve-2026-98888 msrc_CVE-2026-98888 https://db.gcve.eu/vuln/msrc_cve-2026-98888