Daemon crash or code execution via double-free
Published Dec 14, 2023 · Updated Nov 4, 2025
Double free in Slurm 22.05.x, 23.02.x, and 23.11.x allows remote attackers to crash a daemon or execute arbitrary code via protocol messages. The _unpack_node_reg_resp() error path frees the same allocation twice while unpacking a node-registration response. A crafted unauthenticated RPC must reach an affected Slurm daemon; exploitation can interrupt scheduling or run code in the daemon context.
Summary
What happened
Double free in Slurm 22.05.x, 23.02.x, and 23.11.x allows remote attackers to crash a daemon or execute arbitrary code via protocol messages. The _unpack_node_reg_resp() error path frees the same allocation twice while unpacking a node-registration response. A crafted unauthenticated RPC must reach an affected Slurm daemon; exploitation can interrupt scheduling or run code in the daemon context.
The record
- CVE
- CVE-2023-49937
- Published
- Dec 14, 2023
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 14, 2023CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo