# Remote SSH: Segmentation fault (SEGV\_PKUERR) on CPUs without PKU support

**URL:** <https://forum.cursor.com/t/remote-ssh-segmentation-fault-segv-pkuerr-on-cpus-without-pku-support/154123>\
**Category:** Bug Reports\
**Tags:** crashes, linux, ssh\
**Created:** [March 9, 2026, 9:16am UTC](https://forum.cursor.com/t/remote-ssh-segmentation-fault-segv-pkuerr-on-cpus-without-pku-support/154123 "2026-03-09T09:16:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![xnkl-ck](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/xnkl-ck/32/100995_2.png) [@xnkl-ck](https://forum.cursor.com/u/xnkl-ck)\
**Post date:** [March 9, 2026, 9:16am UTC](https://forum.cursor.com/t/remote-ssh-segmentation-fault-segv-pkuerr-on-cpus-without-pku-support/154123/1 "2026-03-09T09:16:23Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

## Bug Description

Cursor Server crashes with SIGSEGV (SEGV\_PKUERR) immediately after startup when connecting to a remote Linux host via SSH. The crash occurs when the V8 JIT compiler loads the `@vscode/spdlog` native module on a CPU that does not support Intel Memory Protection Keys (PKU/MPK).

## Environment

- **Cursor CLI Version** : 2026.01.17-d239e66
- **Local OS** : Windows 10 (10.0.19045)
- **Remote OS** : Ubuntu 22.04.5 LTS (kernel 5.15.0-143-generic)
- **Remote glibc** : 2.35 (fully compatible)
- **Remote arch** : x86\_64
- **Cursor Server commit** : eb1c4e0702d201d1226d2a7afb25c501c2e56080
- **Bundled Node.js** : v20.18.2
- **CPU PKU support** : No (`grep pku /proc/cpuinfo` returns empty)
- **Remote SSH extension** : anysphere.remote-ssh-1.0.46

## Crash Log (strace)

The crash happens right after loading `@vscode/spdlog`:

### Steps to Reproduce

1. Set up SSH config for a remote Linux host (Ubuntu 22.04, x86\_64, CPU without PKU support)
2. In Cursor, connect to this remote host via Remote SSH
3. Wait for Cursor Server to download and install (~89MB)
4. Cursor Server starts, binds to a port, then immediately crashes with “Segmentation fault (core dumped)”
5. Cursor shows error: “Couldn’t install Cursor Server, install script returned non-zero exit status: Code server did not start successfully”

Workaround: Adding `export NODE_OPTIONS="--no-node-snapshot --jitless"` to the cursor-server startup script (~/.cursor-server/bin/linux-x64//bin/cursor-server) before the last line resolves the crash.

Note: Setting NODE\_OPTIONS in ~/.bashrc does NOT work because cursor-server is launched as a background process and does not inherit the shell environment.

### Expected Behavior

Cursor Server should start normally and establish Remote SSH connection without crashing. The V8 engine should detect CPU capabilities and gracefully fall back when PKU (Memory Protection Keys) is not supported by the CPU.

### Screenshots / Screen Recordings

 ![cursor.jpg](https://us1.discourse-cdn.com/cursor1/original/3X/6/c/6c4e73917e2210e17088f83b5c062c52df651e10.jpeg)

### Operating System

Windows 10/11

### Version Information

CLI Version 2026.01.17-d239e66

### For AI issues: which model did you use?

N/A - This is not an AI issue

### For AI issues: add Request ID with privacy disabled

N/A

### Additional Information

Root cause confirmed via strace: V8 JIT compiler triggers SEGV\_PKUERR when loading @vscode/spdlog native module on a CPU without Intel PKU support.

Key evidence:

- strace shows: SIGSEGV {si\_code=SEGV\_PKUERR} right after loading spdlog
- grep pku /proc/cpuinfo returns empty (CPU has no PKU)
- –jitless flag completely fixes the crash (confirms V8 JIT is the cause)
- –no-node-snapshot alone does NOT fix it
- All libraries are present (ldd shows no missing deps)
- No LD\_PRELOAD, no GPU drivers, glibc 2.35 is compatible
- Multiple users on the same server are affected (found another user’s core dump from Dec 2025)

Suggested fix: Detect PKU support at runtime and disable PKU code paths when unsupported, or provide a way to pass NODE\_OPTIONS to the remote cursor-server process via settings.

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [March 9, 2026, 10:19am UTC](https://forum.cursor.com/t/remote-ssh-segmentation-fault-segv-pkuerr-on-cpus-without-pku-support/154123/3 "2026-03-09T10:19:58Z")

</div>

Hey, this is a really helpful bug report.

This is a confirmed issue on our side. The startup script for the remote `cursor-server` should detect the CPU features and handle missing PKU support correctly. I’ve shared this with the team.

One note about the current workaround: `--jitless` fully disables the V8 JIT compiler, which can noticeably slow down `cursor-server` since it runs in interpreter-only mode. It works, but you might see higher latency.

In the end we need a proper fix, either runtime PKU detection in the startup script, or a way to pass environment variables into the remote server process. I’ve flagged both options internally.

Let me know if you run into anything else.

---

<div class="post-metadata">

**Author:** ![xnkl-ck](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/xnkl-ck/32/100995_2.png) [@xnkl-ck](https://forum.cursor.com/u/xnkl-ck)\
**Post date:** [March 10, 2026, 6:07am UTC](https://forum.cursor.com/t/remote-ssh-segmentation-fault-segv-pkuerr-on-cpus-without-pku-support/154123/6 "2026-03-10T06:07:44Z")

</div>

Hi Dean,

Thanks for the quick response and confirmation! Really glad to hear this has been flagged internally.

A few additional data points that might help:

1. **Multiple users affected** : At least 2 users on the same server (found another user’s core dump from December 2025), so this has been a long-standing issue.

2. **CPU info** : The server CPU does not have PKU in its feature flags (`grep pku /proc/cpuinfo` returns empty). I can provide the full `cat /proc/cpuinfo | grep "model name"` output if that helps narrow down affected CPU models.

3. **Regarding the workaround** : Yes, `--jitless` does add noticeable latency, especially during extension loading. It would be great if the fix could either:

4. **Current pain point** : Every time Cursor updates and re-downloads the server, the manual fix is overwritten. A settings-based approach would survive updates.

In the meantime, I’ve documented the workaround for our team. Happy to test any pre-release fix if you need feedback from an affected environment.

Thanks again for looking into this!

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [April 1, 2026, 6:08am UTC](https://forum.cursor.com/t/remote-ssh-segmentation-fault-segv-pkuerr-on-cpus-without-pku-support/154123/7 "2026-04-01T06:08:26Z")

</div>

Closed on April 1, 2026, 6:08am UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [August 20, 2026, 8:11pm UTC](https://forum.cursor.com/t/remote-ssh-segmentation-fault-segv-pkuerr-on-cpus-without-pku-support/154123/10 "2026-08-20T20:11:39Z")

</div>

Hey @xnkl-ck,

Thanks again for the detailed report and the workaround you shared. We’ve since upgraded the runtime the remote server uses, which should resolve the segmentation fault on CPUs without PKU support. Could you give it another try on the latest version? Quick check:

1. Update Cursor to the latest version
2. Connect to your remote host via Remote SSH (no need to re-apply the NODE\_OPTIONS edit, a fresh server build will be downloaded)
3. Confirm the connection succeeds without the crash

Let me know if the crash still happens.
