# x86/shstk: Prevent deadlock during shstk sigreturn

CVE record · `CVE-2026-46063`

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

Published by the CVE Program (CNA: Linux) at 27 May 2026, 12:57 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: `7fad2a432cd35bbf104d2d9d426e74902f22aa95 to before e2c2b044458cbf22da05264fa707308e8d4f86f9` (git)
  - affected: `7fad2a432cd35bbf104d2d9d426e74902f22aa95 to before d042d69b417515959e49021fef008c9b04a99bd5` (git)
  - affected: `7fad2a432cd35bbf104d2d9d426e74902f22aa95 to before 4f3374c990fb2adec06d20fd6d780927811c9aa0` (git)
  - affected: `7fad2a432cd35bbf104d2d9d426e74902f22aa95 to before 3d29db827502067626062f5c74dd502d14ab15bc` (git)
  - affected: `7fad2a432cd35bbf104d2d9d426e74902f22aa95 to before 9874b2917b9fbc30956fee209d3c4aa47201c64e` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.6`
  - unaffected: `before 6.6` (semver)
  - unaffected: `6.6.140 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.88 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.27 to 6.18.*, inclusive` (semver)
  - unaffected: `7.0.4 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 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.0009, the 1st percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 27 May 2026, 12:57 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-46063)
- 27 May 2026, 14:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-46063)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/e2c2b044458cbf22da05264fa707308e8d4f86f9>
- <https://git.kernel.org/stable/c/d042d69b417515959e49021fef008c9b04a99bd5>
- <https://git.kernel.org/stable/c/4f3374c990fb2adec06d20fd6d780927811c9aa0>
- <https://git.kernel.org/stable/c/3d29db827502067626062f5c74dd502d14ab15bc>
- <https://git.kernel.org/stable/c/9874b2917b9fbc30956fee209d3c4aa47201c64e>

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-46063>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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