# tracing: Fix crash on synthetic stacktrace field usage

CVE record · `CVE-2026-23088`

- **Identifiers:** `CVE-2026-23088`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 4 Feb 2026
- **Updated:** 23 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 4 Feb 2026, 16:08 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `00cf3d672a9dd409418647e9f98784c339c3ff63 to before 98ecbfb2598c9c7ca755a29f402da9d36c057077` (git)
  - affected: `00cf3d672a9dd409418647e9f98784c339c3ff63 to before 327af07dff6ab5650b21491eb4f69694999ff3d1` (git)
  - affected: `00cf3d672a9dd409418647e9f98784c339c3ff63 to before 3b90d099efa2b67239bd3b3dc3521ec584261748` (git)
  - affected: `00cf3d672a9dd409418647e9f98784c339c3ff63 to before 90f9f5d64cae4e72defd96a2a22760173cb3c9ec` (git)
  - affected: `b9453380c1c542fd095a4dbe9251eeba4022bbce` (git)
  - affected: `5f52389bdd9eafb63b3a2f804e02aeb17b6a5f55` (git)
  - affected: `f3baa42afeea0d5f04ad31525e861199d02210cc` (git)
  - affected: `5.10.237 to before 5.11` (semver)
  - affected: `5.15.124 to before 5.16` (semver)
  - affected: `6.1.43 to before 6.2` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.3`
  - unaffected: `before 6.3` (semver)
  - unaffected: `6.6.122 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.68 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.8 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0015, the 3rd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 4 Feb 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2026-23088](https://www.cve.org/CVERecord?id=CVE-2026-23088)
- [NVD: CVE-2026-23088](https://nvd.nist.gov/vuln/detail/CVE-2026-23088)

### References from the CNA

- <https://git.kernel.org/stable/c/98ecbfb2598c9c7ca755a29f402da9d36c057077>
- <https://git.kernel.org/stable/c/327af07dff6ab5650b21491eb4f69694999ff3d1>
- <https://git.kernel.org/stable/c/3b90d099efa2b67239bd3b3dc3521ec584261748>
- <https://git.kernel.org/stable/c/90f9f5d64cae4e72defd96a2a22760173cb3c9ec>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-23088>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-23088/>. Everything for agents: <https://agentprime.io/llms.txt>.
