unexpected restart of tidb-server

## Bug Report

Please answer these questions before submitting your issue. Thanks!

### 1. Minimal reproduce step (Required)
No reproduce step

### 2. What did you expect to see? (Required)
No restart

### 3. What did you see instead (Required)
On March 19 and June 3, there were abnormal restarts of a tidb-server on different physical machines within the same user cluster. The business load was normal, and there were no anomalies in the tidb.log file. However, some abnormal information can be seen in the tidb_err.log file. A portion of the tidb_err.log is provided below, with the full file available in the [attached document](https://github.com/user-attachments/files/15799370/tidb_stderr.log). This cluster uses ARM architecture machines, but out of the hundreds of ARM-based TiDB clusters the user has, only this particular cluster has experienced restarts.

``` log
runtime: traceback stuck. pc=0x3973c50 sp=0x426e7d9fb0
stack: frame={sp:0x426e7d9fb0, fp:0x426e7d9fb0} stack=[0x426e7d6000,0x426e7da000)
0x000000426e7d9eb0: 0x0001000000000001 0x000000419b6fefb0
0x000000426e7d9ec0: 0x00000042931231b8 0x0000000004c76e60
0x000000426e7d9ed0: 0x000000419b6fefb0 0x000000410b379f18
0x000000426e7d9ee0: 0x0000000001d1d0f0 0x00000041d76d6540
0x000000426e7d9ef0: 0x0000000000000000 0x00000041d76d6720
0x000000426e7d9f00: 0x0000000000000000 0x0000000000000001
0x000000426e7d9f10: 0x0000000001d261d4 0x000000419b6fefa0
0x000000426e7d9f20: 0x0000000003f7cc01 0x00000042931231b8
0x000000426e7d9f30: 0x0000000003973c1c 0x010000415dc8ebd0
0x000000426e7d9f40: 0x0000000000000000 0x0000000000000000
0x000000426e7d9f50: 0x0000000001d1d330 0x000000426e7d9f40
0x000000426e7d9f60: 0x000000426e7d9f50 0x0000000000000000
0x000000426e7d9f70: 0x000000000187de34 0x000000422bf8ad80
0x000000426e7d9f80: 0x000000415dc8eb80 0x000000419b6fefa0
0x000000426e7d9f90: 0x0000000000000000 0x0000004027712000
0x000000426e7d9fa0: 0x00000041904ec4c0 0x000000402efd8460
0x000000426e7d9fb0: >0x0000000003973c50 0x00000042482f6000
0x000000426e7d9fc0: 0x000000405ad3afb0 0x0000000000000000
0x000000426e7d9fd0: 0x0000000000000000 0x0000000000000000
0x000000426e7d9fe0: 0x0000000000000000 0x0000000000000000
0x000000426e7d9ff0: 0x0000000000000000 0x0000000000000000
fatal error: traceback stuck

goroutine 0 [idle]:
runtime.throw({0x453213d?, 0x6ab0800?})
/usr/local/go/src/runtime/panic.go:1047 +0x40 fp=0x400062c5e0 sp=0x400062c5b0 pc=0x1847df0
runtime.gentraceback(0x71b3f20?, 0x0?, 0x400062c9a8?, 0x40000ccea0, 0x0, 0x400062c9a8, 0x40, 0x0, 0x0?, 0x6)
/usr/local/go/src/runtime/traceback.go:499 +0xeb4 fp=0x400062c940 sp=0x400062c5e0 pc=0x1870004
runtime.sigprof(0x182eaec, 0x400062cc48?, 0x0?, 0x40000ccea0, 0x4000100c00)
/usr/local/go/src/runtime/proc.go:4577 +0xe8 fp=0x400062cbb0 sp=0x400062c940 pc=0x1854608
runtime.sighandler(0x1b?, 0x4000100c00?, 0x400062cc98?, 0x40000ccea0?)
/usr/local/go/src/runtime/signal_unix.go:629 +0x590 fp=0x400062cc60 sp=0x400062cbb0 pc=0x185fb70
runtime.sigtrampgo(0x1b, 0x400062cda0, 0x400062ce20)
/usr/local/go/src/runtime/signal_unix.go:479 +0x164 fp=0x400062cce0 sp=0x400062cc60 pc=0x185f1e4
runtime.sigtramp()
/usr/local/go/src/runtime/sys_linux_arm64.s:471 +0x58 fp=0x400062cda0 sp=0x400062cce0 pc=0x187f098
```

### 4. What is your TiDB version? (Required)
v6.5.2