CVE-2023-49936
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in SchedMD Slurm 22.05.x, 23.02.x, and 23.11.x. A NULL pointer dereference leads to denial of service. The fixed versions are 22.05.11, 23.02.7, and 23.11.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA NULL pointer dereference vulnerability exists in SchedMD Slurm job scheduler versions 22.05.x through 23.11.x. An attacker can trigger this vulnerability to cause a denial of service, likely through crafted requests to the Slurm controller that cause a function to dereference a NULL pointer.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 22.05, < 22.05.12>= 23.02, < 23.02.7= 23.11CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine Slurm controller versionRun `slurmctld --version` or check the installed package version via package manager (e.g., `rpm -q slurm` or `dpkg -l slurm`)Affected if The version returned is >= 22.05 but < 22.05.12, OR >= 23.02 but < 23.02.7, OR equals 23.11 exactly
-
Confirm Slurm controller daemon is runningRun `systemctl status slurmctld` or check for the slurmctld process with `ps aux | grep slurmctld`Affected if The slurmctld daemon is active and exposed to network requests, making it reachable for crafted requests
-
Verify exposed control planeCheck slurm.conf for `ControlMachine` and listen configuration, or review firewall/network ACLs allowing access to Slurm controller ports (typically 6817/TCP)Affected if The Slurm controller port is accessible from network segments where untrusted users or attackers could send crafted requests
You are affected if the Slurm controller (slurmctld) version falls within the vulnerable ranges (22.05.x before 22.05.12, 23.02.x before 23.02.7, or exactly 23.11) and the controller is running and network-accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped22.05.1223.02.7
Upgrade Slurm installations to the fixed versions (22.05.11, 23.02.7, or 23.11.1) or later releases to remediate this vulnerability.
Slurm 22.05.11, 23.02.7, or 23.11.1 (depending on your current branch)
- 1. Identify the currently installed Slurm version using 'slurmctld -V' or 'scontrol version'
- 2. For Slurm 22.05.x: Upgrade to version 22.05.11 or later
- 3. For Slurm 23.02.x: Upgrade to version 23.02.7 or later
- 4. For Slurm 23.11.x: Upgrade to version 23.11.1 or later
- 5. Download the appropriate release from the SchedMD download page (www.schedmd.com/downloads) or your distribution's package repository
- 6. Upgrade the slurm-server and slurm-client packages on all nodes in the cluster
- 7. Restart the slurmctld daemon on the controller node and slurmd on all compute nodes
- 8. Verify the upgrade was successful by running 'scontrol version' and confirming the fixed version is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49936 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-49936 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data