# CVE-2024-42511: pdsh: This update for slurm and pdsh fixes the following issues:  slurm was updated to version 24.11.1 using package slurm_...

CVE-2024-42511 is fixed in 5 products on 1 platform, first by SUSE-FU-2025:0660-1, released February 24, 2025. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2024-42511
- Priority: Routine
- CVSS: n/a
- EPSS: n/a
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Feb 24, 2025

## Description

This update for slurm and pdsh fixes the following issues:  slurm was updated to version 24.11.1 using package slurm_24_11:  - Security issues fixed:   * CVE-2024-48936: Fixed authentication handling in stepmgr that could permit an attacker      to execute processes under other users' jobs (bsc#1236722)   * CVE-2024-42511: Fixed vulnerability with switch plugins where a user could override the      isolation between Slingshot VNIs or IMEX channels (bsc#1236726)  - Important remarks:   * Slurm can be upgraded from version 23.02, 23.11 or 24.05 to version     24.11 without loss of jobs or other state information. Upgrading directly from     an earlier version of Slurm will result in loss of state information.   * If using the `slurmdbd` (Slurm DataBase Daemon) you must update this first.   * The 24.11 `slurmdbd` will work with Slurm daemons of version 23.02 and above.     You will not need to update all clusters at the same time, but it is very     important to update `slurmdbd` first and having it running before updating     any other clusters making use of it.   * If using a backup DBD you must start the primary first to do any     database conversion, the backup will not start until this has happened.   * All SPANK plugins must be recompiled when upgrading from any Slurm version     prior to 24.11.  - Highlights of changes:   * Fixed issues related to the modified startup handling for slurmdbd:      moved PID file to `/run/slurmdbd` (bsc#1236928)   * Create slurm-owned log file on behalf of slurmdbd (bsc#1236929)   * Added report AccountUtilizationByQOS to sreport.   * `AccountUtilizationByUser` is able to be filtered by QOS.   * Added autodetected gpus to the output of `slurmd -C`   * Added ability to submit jobs with multiple QOS. These are sorted by priority    highest being the first.   * Removed the instant on feature from `switch/hpe_slingshot`.   * `slurmctld` : Changed incoming RPC handling to dedicated thread pool with     asynchronous handling of I/O that can be configured via `conmgr_*` entries     under `SlurmctldParameters` in `slurm.conf`.  - Configuration File Changes (see appropriate man page for details)   * Added `SchedulerParameters=bf_allow_magnetic_slot` option. It allows jobs in     magnetic reservations to be planned by backfill scheduler.   * Added `TopologyParam=TopoMaxSizeUnroll=#` to allow `--nodes=<min>-<max>` for     `topology/block`.   * Added `DataParserParameters` `slurm.conf` parameter to allow setting default     value for CLI `--json` and `--yaml` arguments.   * Hardware collectives in `switch/hpe_slingshot` now requires `enable_stepmgr`.   * Added connection related parameters to `slurm.conf` under     `SlurmctldParameters`:       `conmgr_max_connections`: Defaults to 150 connections.       `conmgr_threads`: Defaults to 64 threads for slurmctld.       `conmgr_use_poll`: Defaults is to use epoll in Linux.       `conmgr_connect_timeout`: Defaults to `MessageTimeout`.       `conmgr_read_timeout`: Defaults to `MessageTimeout`.       `conmgr_wait_write_delay`: Defaults to `MessageTimeout`.       `conmgr_write_timeout`: Defaults to MessageTimeout.     * Added `SlurmctldParamters=ignore_constraint_validation` to ignore     `constraint/feature` validation at submission.   * Added `SchedulerParameters=bf_topopt_enable` option to enable experimental hook     to control backfill.  - Command Changes (see man pages for details):   * Remove srun `--cpu-bind=rank`.   * Add `'%b'` as a file name pattern for the array task id modulo 10.   * `sacct` : Respect `--noheader` for `--batch-script` and `--env-vars`.   * Add `sacctmgr ping` command to query status of `slurmdbd`.   * `sbcast` : Add `--nodelist` option to specify where files are transmitted to   * `sbcast` : Add `--no-allocation` option to transmit files to nodes outside     of a  job allocation.   * `slurmdbd` : Add `-u` option. This is used to determine if restarting the DBD     will result in database conversion.   * Remove `salloc --get-user-env`.   * `scontrol` : Add `--json`/`--yaml` support to `listpids`.   * `scontrol` : Add `liststeps`.   * `scontrol` : Add `listjobs`.   * `scontrol show topo` : Show aggregated block sizes when using topology/block.  - API Changes:   * Remove `burst_buffer/lua` call `slurm.job_info_to_string()`.   * `job_submit/lua` : Add `assoc_qos` attribute to `job_desc` to display all     potential QOS's for a job's association.   * `job_submit/lua` : Add `slurm.get_qos_priority()` function to retrieve the     given QOS's priority.  - SLURMRESTD Changes:  * Removed fields deprecated in the Slurm-23.11 release from v0.0.42 endpoints.  * Removed v0.0.39 plugins.  * Set `data_parser/v0.0.42+prefer_refs` flag to default.  * Add `data_parser/v0.0.42+minimize_refs` flag to inline single referenced    schemas in the OpenAPI schema to get default behavior of   `data_parser/v0.0.41`.  * Rename v0.0.42 `JOB_INFO` field `minimum_switches` to `required_switches`    to reflect the actual behavior.  * Rename v0.0.42 `ACCOUNT_CONDITION` field `assocation` to `association`    (typo).  * Tag `slurmdb/v0.0.42/jobs pid` field deprecated.  - For details on the changes in this version update, consult Slurm 24.11 changelog  pdsh:      - Fix version test for munge build (bsc#1236156) - Dropped Slurm support for s390x and i586: Slurm no longer   builds for s390x or 32bit - Implementation of package `pdsh-slurm_24_11` compatible with Slurm 24.11

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | pdsh opensuse-leap 15.6 | 2.35-150500.46.6.3 | [SUSE-FU-2025:0660-1](https://patchblox.com/security/data/fix/linux/suse-fu-2025-0660-1.md) | Feb 24, 2025 |
| Linux | pdsh sles 15.6 | 2.35-150500.46.6.3 | [SUSE-FU-2025:0660-1](https://patchblox.com/security/data/fix/linux/suse-fu-2025-0660-1.md) | Feb 24, 2025 |
| Linux | pdsh_slurm_22_05 opensuse-leap 15.6 | 2.35-150300.54.3 | [SUSE-FU-2025:0660-1](https://patchblox.com/security/data/fix/linux/suse-fu-2025-0660-1.md) | Feb 24, 2025 |
| Linux | pdsh_slurm_23_02 opensuse-leap 15.6 | 2.35-150300.54.3 | [SUSE-FU-2025:0660-1](https://patchblox.com/security/data/fix/linux/suse-fu-2025-0660-1.md) | Feb 24, 2025 |
| Linux | pdsh_slurm_24_11 opensuse-leap 15.6 | 2.35-150500.46.6.2 | [SUSE-FU-2025:0660-1](https://patchblox.com/security/data/fix/linux/suse-fu-2025-0660-1.md) | Feb 24, 2025 |
| Linux | pdsh_slurm_24_11 sles 15.6 | 2.35-150500.46.6.2 | [SUSE-FU-2025:0660-1](https://patchblox.com/security/data/fix/linux/suse-fu-2025-0660-1.md) | Feb 24, 2025 |
| Linux | slurm_24_11 opensuse-leap 15.6 | 24.11.1-150300.7.5.1 | [SUSE-FU-2025:0660-1](https://patchblox.com/security/data/fix/linux/suse-fu-2025-0660-1.md) | Feb 24, 2025 |
| Linux | slurm_24_11 sles 15.6 | 24.11.1-150300.7.5.1 | [SUSE-FU-2025:0660-1](https://patchblox.com/security/data/fix/linux/suse-fu-2025-0660-1.md) | Feb 24, 2025 |

---

Data as of 2026-11-10T20:03:11Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.
