Service crash via size_valp NULL dereference
Published Dec 14, 2023 · Updated Nov 4, 2025
NULL pointer dereference in SchedMD Slurm 22.05.x, 23.02.x, and 23.11.x allows remote attackers to crash an affected daemon. Slurm fails to reject an overflowing size_valp value and dereferences the resulting NULL pointer. No authentication or user interaction is required, and successful exploitation interrupts the affected Slurm service without disclosed data access or modification.
Summary
What happened
NULL pointer dereference in SchedMD Slurm 22.05.x, 23.02.x, and 23.11.x allows remote attackers to crash an affected daemon. Slurm fails to reject an overflowing size_valp value and dereferences the resulting NULL pointer. No authentication or user interaction is required, and successful exploitation interrupts the affected Slurm service without disclosed data access or modification.
The record
- CVE
- CVE-2023-49936
- Published
- Dec 14, 2023
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- 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.
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