CRIU is a checkpoint and restore tool for Linux. Prior to 4.2.1, CRIU injects a syscall;int3 sequence at the start of the first executable virtual memory area and resumes the target process to execute parasite code. Malicious code in the target process can keep an rseq critical section armed over that injection point so the kernel's restartable-sequence abort redirects execution to an attacker-controlled callback when CRIU resumes the process. In container snapshot environments, the hijacked parasite runs with seccomp disabled and a relaxed AppArmor profile and supplies trusted data to the privileged CRIU process, which can enable higher-privilege code execution. This issue is fixed in version 4.2.1.
This CVE has been withdrawn by MITRE
MITRE marked CVE-2026-73860 as REJECTED on . It is no longer considered a valid vulnerability record. The original content below is preserved for historical reference only.
Reason given by MITRE
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-18107. Reason: This candidate is a duplicate of CVE-2026-18107. Notes: All CVE users should reference CVE-2026-18107 instead of this candidate.
CVE-2026-73860
✕ Withdrawn — historical dataMEDIUMPre-NVD 5.4
5.4CVSS
- CVSS
- 5.4
- EchelonGraph score
- Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
- EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- —Not applicable: this CVE ID was withdrawn
Published
November 6, 2026
Last Modified
November 9, 2026
References (5)
- https://github.com/checkpoint-restore/criu/security/advisories/GHSA-fvqj-jvxf-x3wp
- https://github.com/checkpoint-restore/criu/pull/3098
- https://github.com/checkpoint-restore/criu/commit/c34355a7c31494a8be65b32b4410a7539f6c2442
- https://github.com/checkpoint-restore/criu/commit/f7dafedda5075fd6509bda67fbce1622e0c87a27
- https://github.com/checkpoint-restore/criu/releases/tag/v4.2.1
Frequently asked(4)
What is CVE-2026-73860?
CVE-2026-73860 is a rejected CVE ID: its record was withdrawn on November 9, 2026 and no longer describes a vulnerability. Reason given: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-18107. Reason: This candidate is a duplicate of CVE-2026-18107. Notes: All CVE users should reference CVE-2026-18107 instead of this candidate. Its record names CVE-2026-18107 as the replacement.
When was the CVE record for CVE-2026-73860 published?
The CVE record for CVE-2026-73860 was published on November 6, 2026. EchelonGraph's copy of the record carries a last-modified date of November 9, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-73860?
CVE-2026-73860 has a CVSS base score of 5.4 (the CNA's own assessment, by github_m; NVD's own analysis pending).
How do I remediate CVE-2026-73860?
There is nothing to remediate under CVE-2026-73860: it is a rejected (withdrawn) CVE ID and no longer describes a vulnerability. Its record names CVE-2026-18107 as the replacement; act on that CVE instead.