Segmentation fault in actions-runner 2.331.0 on Rocky Linux 9.7

Describe the bug
When attempting to run ephemeral GitHub Actions runners using the ghcr.io/actions/actions-runner:2.331.0 image on Rocky Linux 9.7 hosts, the runner immediately crashes with a segmentation fault (core dumped). Reverting to 2.330.0 resolves the issue.

To Reproduce
Steps to reproduce the behavior:

1. Deploy gha-runner-scale-set-controller:0.13.1 in a Kubernetes cluster.
2. Launch ephemeral runner pods using ghcr.io/actions/actions-runner:2.331.0.
3. Observe runner pod logs:

[RUNNER 2026-01-14 16:09:02Z INFO RunnerServer] Establish connection with 100 seconds timeout.
[RUNNER 2026-01-14 16:09:02Z INFO GitHubActionsService] Starting operation Location.GetConnectionData
/home/runner/run-helper.sh: line 36:    14 Segmentation fault      (core dumped) "$DIR"/bin/Runner.Listener run $*
Exiting with unknown error code: 139
Exiting runner...

Expected behavior
Runner should start and connect to GitHub without crashing

Runner Version and Platform

2.331.0

Host OS: Rocky Linux 9.7

Kernel flags: fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx lm constant_tsc nopl xtopology cpuid tsc_known_freq pni ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes hypervisor lahf_lm cpuid_fault pti

What's not working?

dmesg from host:

[  261.559979] .NET TP Worker[46774]: segfault at 20 ip 00007f97827e5b5c sp 00007f9709294110 error 4 in libssl.so.3[7f97827cc000+62000] likely on CPU 2
[  261.585173] .NET TP Worker[46792]: segfault at 20 ip 00007f5cd640fb5c sp 00007f5c56ff9110 error 4 in libssl.so.3[7f5cd63f6000+62000] likely on CPU 0

Reproduce the failure by deploying gha-runner-scale-set-controller:0.13.1 with ghcr.io/actions/actions-runner:2.331.0 on Rocky Linux 9.7, then inspect the runner logs and host dmesg output. Start at run-helper.sh and bin/Runner.Listener, with the libssl.so.3 segfault as the key symptom. Done means the 2.331.0 runner starts and connects without exiting with code 139.