FedoraOperating system · Fedoraproject
CVE-2023-41914
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 · uneditedSchedMD Slurm 23.02.x before 23.02.6 and 22.05.x before 22.05.10 allows filesystem race conditions for gaining ownership of a file, overwriting a file, or deleting files.
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 confidenceSchedMD Slurm contains a time-of-check to time-of-use (TOCTOU) race condition in its filesystem operations. Local attackers can exploit this to gain ownership of files, overwrite arbitrary files, or delete files by racing between the check and use operations in the affected code paths.
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
FedoraOperating system
= 39>= 22.05, < 22.05.10>= 23.02, < 23.02.6CVSS 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
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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.
-
Confirm Slurm is installedRun 'which slurmctld' or check for slurm packages using your package manager (e.g., 'rpm -qa | grep slurm' or 'dpkg -l | grep slurm')Affected if Slurm is not found on the system - the vulnerability does not apply
-
Identify installed Slurm versionRun 'slurmctld --version' or query your package manager (e.g., 'rpm -q slurm' or 'dpkg -s slurm') to obtain the exact version numberAffected if The version falls within 22.05.0 to 22.05.9, or 23.02.0 to 23.02.5 - these are the vulnerable versions
-
Verify underlying OS distributionCheck if the system runs Fedora 39 by running 'cat /etc/fedora-release' or 'hostnamectl'Affected if The system is Fedora 39 and has Slurm installed, regardless of Slurm version, as Fedora 39 is explicitly affected
-
Assess multi-user environment exposureCheck for multiple local user accounts with 'ls -la /home' or 'getent passwd' to determine if untrusted local users could exploit this TOCTOU vulnerabilityAffected if The system has multiple local user accounts and runs a vulnerable Slurm version - these conditions together create the exposure window for a local attacker to race file operations
A user is affected if Slurm is installed AND the version is either 22.05.0-22.05.9 or 23.02.0-23.02.5 (or if running Fedora 39 with any Slurm version), and the system has multiple local users who could exploit the TOCTOU race condition in file handling operations.
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.1023.02.6
Upgrade to Slurm version 23.02.6 or 22.05.10 or later to patch the race conditions in file handling operations.
Slurm 22.05.10+ or 23.02.6+ (depending on your branch)
- Identify the currently installed Slurm version using 'slurmctld --version' or 'scontrol version'
- For Slurm 22.05.x: Upgrade to version 22.05.10 or later
- For Slurm 23.02.x: Upgrade to version 23.02.6 or later
- On Fedora 39: Run 'dnf update slurm' or 'dnf upgrade slurm' to obtain the patched package
- After upgrade, restart the slurmctld daemon on the control node: 'systemctl restart slurmctld'
- Restart slurmd daemons on compute nodes as needed: 'systemctl restart slurmd'
- Verify the new version is running: 'scontrol version'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fedora
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41914 — 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-41914 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