🛡️ SUSE-SU-2025:01757-1 — slurm-24-11 (CVE-2025-43904)

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Security update for slurm_24_11

This update for slurm_24_11 fixes the following issues:

Update to version 24.11.5.

Security issues fixed:

  • CVE-2025-43904: an issue with permission handling for Coordinators within the accounting system allowed Coordinators

to promote a user to Administrator (bsc#1243666).

Other changes and issues fixed:

  • Changes from version 24.11.5
  • Return error to scontrol reboot on bad nodelists.
  • slurmrestd - Report an error when QOS resolution fails for

v0.0.40 endpoints.

  • slurmrestd - Report an error when QOS resolution fails for

v0.0.41 endpoints.

  • slurmrestd - Report an error when QOS resolution fails for

v0.0.42 endpoints.

  • data_parser/v0.0.42 - Added +inline_enums flag which

modifies the output when generating OpenAPI specification.

It causes enum arrays to not be defined in their own schema

with references ($ref) to them. Instead they will be dumped

inline.

  • Fix binding error with tres-bind map/mask on partial node

allocations.

  • Fix stepmgr enabled steps being able to request features.
  • Reject step creation if requested feature is not available

in job.

  • slurmd - Restrict listening for new incoming RPC requests

further into startup.

  • slurmd - Avoid auth/slurm related hangs of CLI commands

during startup and shutdown.

  • slurmctld - Restrict processing new incoming RPC requests

further into startup. Stop processing requests sooner during

shutdown.

  • slurmcltd - Avoid auth/slurm related hangs of CLI commands

during startup and shutdown.

  • slurmctld - Avoid race condition during shutdown or

ereconfigure that could result in a crash due delayed

processing of a connection while plugins are unloaded.

  • Fix small memleak when getting the job list from the database.
  • Fix incorrect printing of % escape characters when printing

stdio fields for jobs.

  • Fix padding parsing when printing stdio fields for jobs.
  • Fix printing %A array job id when expanding patterns.
  • Fix reservations causing jobs to be held for Bad Constraints.
  • switch/hpe_slingshot - Prevent potential segfault on failed

curl request to the fabric manager.

  • Fix printing incorrect array job id when expanding stdio file

names. The %A will now be substituted by the correct value.

  • Fix printing incorrect array job id when expanding stdio file

names. The %A will now be substituted by the correct value.

  • switch/hpe_slingshot - Fix VNI range not updating on slurmctld

restart or reconfigre.

  • Fix steps not being created when using certain combinations of

-c and -n inferior to the jobs requested resources, when

using stepmgr and nodes are configured with

CPUs == Sockets*CoresPerSocket.

  • Permit configuring the number of retry attempts to destroy CXI

service via the new destroy_retries SwitchParameter.

  • Do not reset memory.high and memory.swap.max in slurmd

startup or reconfigure as we are never really touching this

in slurmd.

  • Fix reconfigure failure of slurmd when it has been started

manually and the CoreSpecLimits have been removed from

slurm.conf.

  • Set or reset CoreSpec limits when slurmd is reconfigured and

it was started with systemd.

  • switch/hpe-slingshot - Make sure the slurmctld can free

step VNIs after the controller restarts or reconfigures while

the job is running.

  • Fix backup slurmctld failure on 2nd takeover.
  • Changes from version 24.11.4
  • slurmctld,slurmrestd - Avoid possible race condition that

could have caused process to crash when listener socket was

closed while accepting a new connection.

  • slurmrestd - Avoid race condition that could have resulted

in address logged for a UNIX socket to be incorrect.

  • slurmrestd - Fix parameters in OpenAPI specification for the

following endpoints to have job_id field:

```

GET /slurm/v0.0.40/jobs/state/

GET /slurm/v0.0.41/jobs/state/

GET /slurm/v0.0.42/jobs/state/

GET /slurm/v0.0.43/jobs/state/

```

  • slurmd - Fix tracking of thread counts that could cause

incoming connections to be ignored after burst of simultaneous

incoming connections that trigger delayed response logic.

  • Avoid unnecessary SRUN_TIMEOUT forwarding to stepmgr.
  • Fix jobs being scheduled on higher weighted powered down nodes.
  • Fix how backfill scheduler filters nodes from the available

nodes based on exclusive user and mcs_label requirements.

  • acct_gather_energy/{gpu,ipmi} - Fix potential energy

consumption adjustment calculation underflow.

  • acct_gather_energy/ipmi - Fix regression introduced in 24.05.5

(which introduced the new way of preserving energy measurements

through slurmd restarts) when EnergyIPMICalcAdjustment=yes.

  • Prevent slurmctld deadlock in the assoc mgr.
  • Fix memory leak when RestrictedCoresPerGPU is enabled.
  • Fix preemptor jobs not entering execution due to wrong

calculation of accounting policy limits.

*

Affected software

SUSE-SU-2025:01757-1 is recorded against 1 package.

  • slurm-24-11 (fixed in 24.11.5-3.8.1)

Timeline and source

Published on 29 May 2025 and last revised on 4 February 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

www.suse.com (Advisory)
bugzilla.suse.com (Report)
www.suse.com (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2025-05-29
Updated 2026-08-20
Modified 2026-02-04
Fix URL N/A

Affected Packages

Software From version Fixed in
slurm-24-11 24.11.5-3.8.1

Similar Threats

Free Vulnerability Check

Is your site affected by SUSE-SU-2025:01757-1?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against SUSE-SU-2025:01757-1 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesSUSESUSE 2025