{"id":"CVE-2025-43904","aliases":["DEBIAN-CVE-2025-43904","DSA-5961-1","EUVD-2026-2931","GHSA-2778-hrgh-cpxw","MGASA-2025-0215","SUSE-SU-2025:01751-1","SUSE-SU-2025:01752-1","SUSE-SU-2025:01753-1","SUSE-SU-2025:01755-1","SUSE-SU-2025:01756-1","SUSE-SU-2025:01757-1","SUSE-SU-2025:01758-1","SUSE-SU-2025:01759-1","SUSE-SU-2025:01760-1","SUSE-SU-2025:01761-1","SUSE-SU-2025:02779-1","UBUNTU-CVE-2025-43904","USN-8236-1","openSUSE-SU-2025:15165-1"],"status":"published","title":"In SchedMD Slurm before 24.11.5, 24.05.8, and 23.11.11, the accounting system can allow a...","description":"In SchedMD Slurm before 24.11.5, 24.05.8, and 23.11.11, the accounting system can allow a Coordinator to promote a user to Administrator.","severity":{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00254,"percentile":0.1708,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-863"],"published":"2025-05-26T00:00:00Z","modified":"2026-09-01T20:05:52Z","fixes":[{"ecosystem":"Debian:12","package":"slurm-wlm","fixed_in":["22.05.8-4+deb12u3"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"slurm-wlm","fixed_in":["24.11.5-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"slurm-wlm","fixed_in":["24.11.5-1"],"sources":["osv"]},{"ecosystem":"Mageia:9","package":"slurm","fixed_in":["23.11.11-1.mga9"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Module for HPC 15 SP7","package":"slurm","fixed_in":["24.11.5-150700.3.3.1","23.02.7-150500.5.18.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP7","package":"slurm","fixed_in":["24.11.5-150700.3.3.1","20.11.9-150400.3.6.2"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Module for HPC 12","package":"slurm_23_02","fixed_in":["23.02.7-3.19.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Module for HPC 12","package":"slurm_20_11","fixed_in":["20.11.9-3.22.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Module for HPC 12","package":"slurm_22_05","fixed_in":["22.05.11-3.12.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"slurm_22_05","fixed_in":["22.05.11-150300.7.12.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"slurm_22_05","fixed_in":["22.05.11-150300.7.12.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"slurm_22_05","fixed_in":["22.05.11-150300.7.12.1"],"sources":["osv"]},{"ecosystem":"openSUSE:Leap 15.6","package":"slurm_22_05","fixed_in":["22.05.11-150300.7.12.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Module for HPC 12","package":"slurm_24_11","fixed_in":["24.11.5-3.8.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Module for HPC 15 SP7","package":"slurm_23_02","fixed_in":["23.02.7-150300.7.20.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"slurm_23_02","fixed_in":["23.02.7-150300.7.20.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"slurm_23_02","fixed_in":["23.02.7-150300.7.20.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"slurm_23_02","fixed_in":["23.02.7-150300.7.20.1"],"sources":["osv"]},{"ecosystem":"openSUSE:Leap 15.6","package":"slurm_23_02","fixed_in":["23.02.7-150300.7.20.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Module for HPC 15 SP6","package":"slurm","fixed_in":["23.02.7-150500.5.18.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP6","package":"slurm","fixed_in":["23.02.7-150500.5.18.1","20.11.9-150400.3.6.2"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"slurm","fixed_in":["23.02.7-150500.5.18.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"slurm","fixed_in":["23.02.7-150500.5.18.1"],"sources":["osv"]},{"ecosystem":"openSUSE:Leap 15.6","package":"slurm","fixed_in":["23.02.7-150500.5.18.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"slurm","fixed_in":["20.11.9-150300.4.15.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Module for HPC 15 SP6","package":"slurm_24_11","fixed_in":["24.11.5-150300.7.8.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"slurm_24_11","fixed_in":["24.11.5-150300.7.8.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"slurm_24_11","fixed_in":["24.11.5-150300.7.8.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"slurm_24_11","fixed_in":["24.11.5-150300.7.8.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"slurm_24_11","fixed_in":["24.11.5-150300.7.8.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"slurm_24_11","fixed_in":["24.11.5-150300.7.8.1"],"sources":["osv"]},{"ecosystem":"openSUSE:Leap 15.6","package":"slurm_24_11","fixed_in":["24.11.5-150300.7.8.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"slurm","fixed_in":["20.11.9-150400.3.6.2"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"slurm","fixed_in":["20.11.9-150400.3.6.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:22.04:LTS","package":"slurm-wlm","fixed_in":["21.08.5-2ubuntu1+esm2"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:24.04:LTS","package":"slurm-wlm","fixed_in":["23.11.4-1.2ubuntu5+esm1"],"sources":["osv"]},{"ecosystem":"openSUSE:Tumbleweed","package":"slurm","fixed_in":["24.11.5-1.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"slurm-wlm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"22.05.8-4+deb12u3"}]}],"versions":["22.05.8-4","22.05.8-4+deb12u1","22.05.8-4+deb12u2"]},{"source":"osv","ecosystem":"Debian:13","package":"slurm-wlm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.11.5-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"slurm-wlm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.11.5-1"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"slurm-wlm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"22.05.8-4+deb12u3"}]}],"versions":["22.05.8-4","22.05.8-4+deb12u1","22.05.8-4+deb12u2"]},{"source":"osv","ecosystem":"Mageia:9","package":"slurm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.11.11-1.mga9"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for HPC 15 SP7","package":"slurm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.11.5-150700.3.3.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP7","package":"slurm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.11.5-150700.3.3.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for HPC 12","package":"slurm_23_02","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.02.7-3.19.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for HPC 12","package":"slurm_20_11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.11.9-3.22.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for HPC 12","package":"slurm_22_05","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"22.05.11-3.12.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"slurm_22_05","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"22.05.11-150300.7.12.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"slurm_22_05","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"22.05.11-150300.7.12.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"slurm_22_05","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"22.05.11-150300.7.12.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"slurm_22_05","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"22.05.11-150300.7.12.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for HPC 12","package":"slurm_24_11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.11.5-3.8.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for HPC 15 SP7","package":"slurm_23_02","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.02.7-150300.7.20.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"slurm_23_02","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.02.7-150300.7.20.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"slurm_23_02","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.02.7-150300.7.20.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"slurm_23_02","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.02.7-150300.7.20.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"slurm_23_02","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.02.7-150300.7.20.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for HPC 15 SP6","package":"slurm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.02.7-150500.5.18.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for HPC 15 SP7","package":"slurm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.02.7-150500.5.18.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP6","package":"slurm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.02.7-150500.5.18.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"slurm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.02.7-150500.5.18.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"slurm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.02.7-150500.5.18.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"slurm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.02.7-150500.5.18.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"slurm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.11.9-150300.4.15.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for HPC 15 SP6","package":"slurm_24_11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.11.5-150300.7.8.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"slurm_24_11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.11.5-150300.7.8.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"slurm_24_11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.11.5-150300.7.8.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"slurm_24_11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.11.5-150300.7.8.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"slurm_24_11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.11.5-150300.7.8.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"slurm_24_11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.11.5-150300.7.8.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"slurm_24_11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.11.5-150300.7.8.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP6","package":"slurm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.11.9-150400.3.6.2"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP7","package":"slurm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.11.9-150400.3.6.2"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"slurm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.11.9-150400.3.6.2"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"slurm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.11.9-150400.3.6.2"}]}]},{"source":"osv","ecosystem":"Ubuntu:Pro:22.04:LTS","package":"slurm-wlm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"21.08.5-2ubuntu1+esm2"}]}],"versions":["20.11.7+really20.11.4-2","21.08.5-1","21.08.5-1.1","21.08.5-2","21.08.5-2ubuntu1","21.08.5-2ubuntu1+esm1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:24.04:LTS","package":"slurm-wlm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.11.4-1.2ubuntu5+esm1"}]}],"versions":["23.02.3-2ubuntu1","23.02.6-1ubuntu2","23.02.6-1ubuntu3","23.11.3-1ubuntu1","23.11.3-2ubuntu1","23.11.3-2ubuntu2","23.11.4-1.2ubuntu4","23.11.4-1.2ubuntu5"]},{"source":"osv","ecosystem":"Ubuntu:Pro:22.04:LTS","package":"slurm-wlm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"21.08.5-2ubuntu1+esm2"}]}],"versions":["20.11.7+really20.11.4-2","21.08.5-1","21.08.5-1.1","21.08.5-2","21.08.5-2ubuntu1","21.08.5-2ubuntu1+esm1"],"bundled":5},{"source":"osv","ecosystem":"Ubuntu:Pro:24.04:LTS","package":"slurm-wlm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.11.4-1.2ubuntu5+esm1"}]}],"versions":["23.02.3-2ubuntu1","23.02.6-1ubuntu2","23.02.6-1ubuntu3","23.11.3-1ubuntu1","23.11.3-2ubuntu1","23.11.3-2ubuntu2","23.11.4-1.2ubuntu4","23.11.4-1.2ubuntu5"],"bundled":5},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"slurm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.11.5-1.1"}]}]}],"products":[{"vendor":"schedmd","product":"slurm"}],"references":[{"url":"https://www.schedmd.com/security-policy/"},{"url":"https://lists.schedmd.com/mailman3/hyperkitty/list/slurm-announce@lists.schedmd.com/message/B73QHKW6TKE2T5KDWVPIWNE5H4KWX667/","tags":["report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-43904"},{"url":"https://lists.schedmd.com/mailman3/hyperkitty/list/slurm-announce@lists.schedmd.com/message/B73QHKW6TKE2T5KDWVPIWNE5H4KWX667"},{"url":"https://www.schedmd.com/security-policy"},{"url":"https://github.com/advisories/GHSA-2778-hrgh-cpxw"},{"url":"https://security-tracker.debian.org/tracker/CVE-2025-43904","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2025-0215.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=34453","tags":["report"]},{"url":"https://lists.debian.org/debian-security-announce/2025/msg00125.html","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202501751-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1243666","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-43904","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202501752-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202501753-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202501755-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202501756-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202501757-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202501758-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202501759-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202501760-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202501761-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202502779-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-43904","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-43904","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8236-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2023-41914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-49933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-49937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-49938","tags":["report"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/ZM554V3RZULA7GY4OOIJD52CQG4KZ7TP/","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2025-43904","description":"In SchedMD Slurm before 24.11.5, 24.05.8, and 23.11.11, the accounting system can allow a Coordinator to promote a user to Administrator.","status":"published","published":"2026-01-16T00:00:00Z","modified":"2026-01-20T15:29:05.323Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-863"],"updated_at":"2026-11-02T14:32:26.64278Z"}],"euvd":[{"id":"EUVD-2026-2931","description":"In SchedMD Slurm before 24.11.5, 24.05.8, and 23.11.11, the accounting system can allow a Coordinator to promote a user to Administrator.","status":"published","published":"2026-01-16T00:00:00Z","modified":"2026-01-20T15:29:05Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T19:48:50.374471Z"}],"ghsa":[{"id":"GHSA-2778-hrgh-cpxw","title":"In SchedMD Slurm before 24.11.5, 24.05.8, and 23.11.11, the accounting system can allow a...","description":"In SchedMD Slurm before 24.11.5, 24.05.8, and 23.11.11, the accounting system can allow a Coordinator to promote a user to Administrator.","status":"published","published":"2026-01-16T18:31:33Z","modified":"2026-01-16T18:31:44Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"cwes":["CWE-863"],"updated_at":"2026-11-02T15:05:38.741943Z"}],"nvd":[{"id":"CVE-2025-43904","description":"In SchedMD Slurm before 24.11.5, 24.05.8, and 23.11.11, the accounting system can allow a Coordinator to promote a user to Administrator.","status":"published","published":"2026-01-16T18:16:08.197Z","modified":"2026-06-17T09:24:42.8Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-863"],"updated_at":"2026-11-02T14:11:57.915063Z"}],"osv":[{"id":"DEBIAN-CVE-2025-43904","description":"In SchedMD Slurm before 24.11.5, 24.05.8, and 23.11.11, the accounting system can allow a Coordinator to promote a user to Administrator.","status":"published","published":"2026-01-16T18:16:08.197Z","modified":"2026-09-01T20:05:52.572203332Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T15:45:47.378563Z"},{"id":"UBUNTU-CVE-2025-43904","description":"In SchedMD Slurm before 24.11.5, 24.05.8, and 23.11.11, the accounting system can allow a Coordinator to promote a user to Administrator.","status":"published","published":"2026-01-16T18:16:00Z","modified":"2026-05-07T13:41:52.979214Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T16:55:50.31802Z"},{"id":"DSA-5961-1","title":"slurm-wlm - security update","status":"published","published":"2025-07-08T00:00:00Z","modified":"2026-03-09T02:11:26.015571Z","updated_at":"2026-11-02T15:46:18.296714Z"},{"id":"MGASA-2025-0215","title":"Updated slurm packages fix security vulnerability","description":"Updated slurm packages to fix a vulnerability in the Slurm’s accounting\nsystem that would have allowed a Coordinator to promote a user to\nAdministrator (CVE-2025-43904).\n","status":"published","published":"2025-07-31T17:26:20Z","modified":"2026-04-16T04:44:38.821403258Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"openSUSE-SU-2025:15165-1","title":"libnss_slurm2-24.11.5-1.1 on GA media","description":"These are all security issues fixed in the libnss_slurm2-24.11.5-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2025-05-26T00:00:00Z","modified":"2026-03-23T04:53:25.856378Z","updated_at":"2026-11-02T16:58:37.399567Z"},{"id":"SUSE-SU-2025:01751-1","title":"Security update for slurm","description":"This update for slurm fixes the following issues:\n\nUpdate to version 24.11.5.\n\nSecurity issues fixed:\n  \n- CVE-2025-43904: an issue with permission handling for Coordinators within the accounting system allowed Coordinators\n  to promote a user to Administrator (bsc#1243666).\n\nOther changes and issues fixed:\n\n- Changes from version 24.11.5\n\n  * Return error to `scontrol` reboot on bad nodelists.\n  * `slurmrestd` - Report an error when QOS resolution fails for\n\tv0.0.40 endpoints.\n  * `slurmrestd` - Report an error when QOS resolution fails for\n\tv0.0.41 endpoints.\n  * `slurmrestd` - Report an error when QOS resolution fails for\n\tv0.0.42 endpoints.\n  * `data_parser/v0.0.42` - Added `+inline_enums` flag which\n\tmodifies the output when generating OpenAPI specification.\n\tIt causes enum arrays to not be defined in their own schema\n\twith references (`$ref`) to them. Instead they will be dumped\n\tinline.\n  * Fix binding error with `tres-bind map/mask` on partial node\n\tallocations.\n  * Fix `stepmgr` enabled steps being able to request features.\n  * Reject step creation if requested feature is not available\n\tin job.\n  * `slurmd` - Restrict listening for new incoming RPC requests\n\tfurther into startup.\n  * `slurmd` - Avoid `auth/slurm` related hangs of CLI commands\n\tduring startup and shutdown.\n  * `slurmctld` - Restrict processing new incoming RPC requests\n\tfurther into startup. Stop processing requests sooner during\n\tshutdown.\n  * `slurmcltd` - Avoid auth/slurm related hangs of CLI commands\n\tduring startup and shutdown.\n  * `slurmctld` - Avoid race condition during shutdown or\n\tereconfigure that could result in a crash due delayed\n\tprocessing of a connection while plugins are unloaded.\n  * Fix small memleak when getting the job list from the database.\n  * Fix incorrect printing of `%` escape characters when printing\n\tstdio fields for jobs.\n  * Fix padding parsing when printing stdio fields for jobs.\n  * Fix printing `%A` array job id when expanding patterns.\n  * Fix reservations causing jobs to be held for `Bad Constraints`.\n  * `switch/hpe_slingshot` - Prevent potential segfault on failed\n\tcurl request to the fabric manager.\n  * Fix printing incorrect array job id when expanding stdio file\n\tnames. The `%A` will now be substituted by the correct value.\n  * Fix printing incorrect array job id when expanding stdio file\n\tnames. The `%A` will now be substituted by the correct value.\n  * `switch/hpe_slingshot` - Fix VNI range not updating on slurmctld\n\trestart or reconfigre.\n  * Fix steps not being created when using certain combinations of\n\t`-c` and `-n` inferior to the jobs requested resources, when\n\tusing stepmgr and nodes are configured with\n\t`CPUs == Sockets*CoresPerSocket`.\n  * Permit configuring the number of retry attempts to destroy CXI\n\tservice via the new destroy_retries `SwitchParameter`.\n  * Do not reset `memory.high` and `memory.swap.max` in slurmd\n\tstartup or reconfigure as we are never really touching this\n\tin `slurmd`.\n  * Fix reconfigure failure of slurmd when it has been started\n\tmanually and the `CoreSpecLimits` have been removed from\n\t`slurm.conf`.\n  * Set or reset CoreSpec limits when slurmd is reconfigured and\n\tit was started with systemd.\n  * `switch/hpe-slingshot` - Make sure the slurmctld can free\n\tstep VNIs after the controller restarts or reconfigures while\n\tthe job is running.\n  * Fix backup `slurmctld` failure on 2nd takeover.\n  \n- Changes from version 24.11.4\n\n  * `slurmctld`,`slurmrestd` - Avoid possible race condition that\n    could have caused process to crash when listener socket was\n    closed while accepting a new connection.\n  * `slurmrestd` - Avoid race condition that could have resulted\n\tin address logged for a UNIX socket to be incorrect.\n  * `slurmrestd` - Fix parameters in OpenAPI specification for the\n    following endpoints to have `job_id` field:\n    ```\n    GET /slurm/v0.0.40/jobs/state/\n    GET /slurm/v0.0.41/jobs/state/\n    GET /slurm/v0.0.42/jobs/state/\n    GET /slurm/v0.0.43/jobs/state/\n    ```\n  * `slurmd` - Fix tracking of thread counts that could cause\n\tincoming connections to be ignored after burst of simultaneous\n\tincoming connections that trigger delayed response logic.\n  * Avoid unnecessary `SRUN_TIMEOUT` forwarding to `stepmgr`.\n  * Fix jobs being scheduled on higher weighted powered down nodes.\n  * Fix how backfill scheduler filters nodes from the available\n\tnodes based on exclusive user and `mcs_label` requirements.\n  * `acct_gather_energy/{gpu,ipmi}` - Fix potential energy\n\tconsumption adjustment calculation underflow.\n  * `acct_gather_energy/ipmi` - Fix regression introduced in 24.05.5\n\t(which introduced the new way of preserving energy measurements\n\tthrough slurmd restarts) when `EnergyIPMICalcAdjustment=yes`.\n  * Prevent `slurmctld` deadlock in the assoc mgr.\n  * Fix memory leak when `RestrictedCoresPerGPU` is enabled.\n  * Fix preemptor jobs not entering execution due to wrong\n\tcalculation of accounting policy limits.\n  * Fix certain job requests that were incorrectly denied with\n\tnode configuration unavailable error.\n  * `slurmd` - Avoid crash due when slurmd has a communications\n\tfailure with `slurmstepd`.\n  * Fix memory leak when parsing yaml input.\n  * Prevent `slurmctld` from showing error message about `PreemptMode=GANG`\n\tbeing a cluster-wide option for `scontrol update part` calls\n\tthat don't attempt to modify partition PreemptMode.\n  * Fix setting `GANG` preemption on partition when updating\n\t`PreemptMode` with `scontrol`.\n  * Fix `CoreSpec` and `MemSpec` limits not being removed\n\tfrom previously configured slurmd.\n  * Avoid race condition that could lead to a deadlock when `slurmd`,\n\t`slurmstepd`, `slurmctld`, `slurmrestd` or `sackd` have a fatal\n\tevent.\n  * Fix jobs using `--ntasks-per-node` and `--mem` keep pending\n\tforever\twhen the requested mem divided by the number of CPUs\n\twill surpass the configured `MaxMemPerCPU`.\n  * `slurmd` - Fix address logged upon new incoming RPC connection\n    from `INVALID` to IP address.\n  * Fix memory leak when retrieving reservations. This affects\n\t`scontrol`, `sinfo`, `sview`, and the following `slurmrestd`\n\tendpoints:\n    `GET /slurm/{any_data_parser}/reservation/{reservation_name}`\n    `GET /slurm/{any_data_parser}/reservations`\n  * Log warning instead of `debuflags=conmgr` gated log when\n\tdeferring new incoming connections when number of active\n\tconnections exceed `conmgr_max_connections`.\n  * Avoid race condition that could result in worker thread pool\n\tnot activating all threads at once after a reconfigure resulting\n\tin lower utilization of available CPU threads until enough\n\tinternal activity wakes up all threads in the worker pool.\n  * Avoid theoretical race condition that could result in new\n\tincoming RPC\n    socket connections being ignored after reconfigure.\n  * slurmd - Avoid race condition that could result in a state\n\twhere\tnew incoming RPC connections will always be ignored.\n  * Add ReconfigFlags=KeepNodeStateFuture to restore saved `FUTURE`\n\tnode state on restart and reconfig instead of reverting to\n\t`FUTURE` state. This will be made the default in 25.05.\n  * Fix case where hetjob submit would cause `slurmctld` to crash.\n  * Fix jobs using `--cpus-per-gpu` and `--mem` keep pending forever\n\twhen the requested mem divided by the number of CPUs will surpass\n\tthe configured `MaxMemPerCPU`.\n  * Enforce that jobs using `--mem` and several `--*-per-*` options\n\tdo not violate the `MaxMemPerCPU` in place.\n  * `slurmctld` - Fix use-cases of jobs incorrectly pending held\n\twhen `--prefer` features are not initially satisfied.\n  * `slurmctld` - Fix jobs incorrectly held when `--prefer` not\n\tsatisfied in some use-cases.\n  * Ensure `RestrictedCoresPerGPU` and `CoreSpecCount` don't overlap.\n\n- Changes from version 24.11.3\n\n  * Fix database cluster ID generation not being random.\n  * Fix a regression in which `slurmd -G` gave no output.\n  * Fix a long-standing crash in `slurmctld` after updating a\n    reservation with an empty nodelist. The crash could occur\n\tafter restarting slurmctld, or if downing/draining a node\n\tin the reservation with the `REPLACE` or `REPLACE_DOWN` flag.\n  * Avoid changing process name to '`watch`' from original daemon name.\n    This could potentially breaking some monitoring scripts.\n  * Avoid `slurmctld` being killed by `SIGALRM` due to race condition\n    at startup.\n  * Fix race condition in slurmrestd that resulted in '`Requested\n    data_parser plugin does not support OpenAPI plugin`' error being\n\treturned for valid endpoints.\n  * Fix race between `task/cgroup` CPUset and `jobacctgather/cgroup`.\n    The first was removing the pid from `task_X` cgroup directory\n\tcausing memory limits to not being applied.\n  * If multiple partitions are requested, set the `SLURM_JOB_PARTITION`\n    output environment variable to the partition in which the job is\n\trunning for `salloc` and `srun` in order to match the documentation\n\tand the behavior of `sbatch`.\n  * `srun` - Fixed wrongly constructed `SLURM_CPU_BIND` env variable\n    that could get propagated to downward srun calls in certain mpi\n    environments, causing launch failures.\n  * Don't print misleading errors for stepmgr enabled steps.\n  * `slurmrestd` - Avoid connection to slurmdbd for the following\n    endpoints:\n\t```\n    GET /slurm/v0.0.41/jobs\n    GET /slurm/v0.0.41/job/{job_id}\n\t```\n  * `slurmrestd` - Avoid connection to slurmdbd for the following\n    endpoints:\n\t```\n    GET /slurm/v0.0.40/jobs\n    GET /slurm/v0.0.40/job/{job_id}\n\t```\n  * `slurmrestd` - Fix possible memory leak when parsing arrays with\n    `data_parser/v0.0.40`.\n  * `slurmrestd` - Fix possible memory leak when parsing arrays with\n    `data_parser/v0.0.41`.\n  * `slurmrestd` - Fix possible memory leak when parsing arrays with\n    `data_parser/v0.0.42`.\n  \n- Changes from version 24.11.2\n\n  * Fix segfault when submitting `--test-only` jobs that can\n    preempt.\n  * Fix regression introduced in 23.11 that prevented the\n    following flags from being added to a reservation on an\n    update: `DAILY`, `HOURLY`, `WEEKLY`, `WEEKDAY`, and `WEEKEND`.\n  * Fix crash and issues evaluating job's suitability for running\n    in nodes with already suspended job(s) there.\n  * `slurmctld` will ensure that healthy nodes are not reported as\n    `UnavailableNodes` in job reason codes.\n  * Fix handling of jobs submitted to a current reservation with\n    flags `OVERLAP,FLEX` or `OVERLAP,ANY_NODES` when it overlaps nodes\n    with a future maintenance reservation. When a job submission\n    had a time limit that overlapped with the future maintenance\n    reservation, it was rejected. Now the job is accepted but\n    stays pending with the reason '`ReqNodeNotAvail, Reserved for\n    maintenance`'.\n  * `pam_slurm_adopt` - avoid errors when explicitly setting some\n    arguments to the default value.\n  * Fix QOS preemption with `PreemptMode=SUSPEND`.\n  * `slurmdbd` - When changing a user's name update lineage at the\n    same time.\n  * Fix regression in 24.11 in which `burst_buffer.lua` does not\n    inherit the `SLURM_CONF` environment variable from `slurmctld` and\n    fails to run if slurm.conf is in a non-standard location.\n  * Fix memory leak in slurmctld if `select/linear` and the\n    `PreemptParameters=reclaim_licenses` options are both set in\n    `slurm.conf`.  Regression in 24.11.1.\n  * Fix running jobs, that requested multiple partitions, from\n    potentially being set to the wrong partition on restart.\n  * `switch/hpe_slingshot` - Fix compatibility with newer cxi\n    drivers, specifically when specifying `disable_rdzv_get`.\n  * Add `ABORT_ON_FATAL` environment variable to capture a backtrace\n    from any `fatal()` message.\n  * Fix printing invalid address in rate limiting log statement.\n  * `sched/backfill` - Fix node state `PLANNED` not being cleared from\n    fully allocated nodes during a backfill cycle.\n  * `select/cons_tres` - Fix future planning of jobs with\n    `bf_licenses`.\n  * Prevent redundant '`on_data returned rc: Rate limit exceeded,\n    please retry momentarily`' error message from being printed in\n    slurmctld logs.\n  * Fix loading non-default QOS on pending jobs from pre-24.11\n    state.\n  * Fix pending jobs displaying `QOS=(null)` when not explicitly\n    requesting a QOS.\n  * Fix segfault issue from job record with no `job_resrcs`.\n  * Fix failing `sacctmgr delete/modify/show` account operations\n    with `where` clauses.\n  * Fix regression in 24.11 in which Slurm daemons started\n    catching several `SIGTSTP`, `SIGTTIN` and `SIGUSR1` signals and\n    ignored them, while before they were not ignoring them. This\n    also caused slurmctld to not being able to shutdown after a\n    `SIGTSTP` because slurmscriptd caught the signal and stopped\n    while slurmctld ignored it. Unify and fix these situations and\n    get back to the previous behavior for these signals.\n  * Document that `SIGQUIT` is no longer ignored by `slurmctld`,\n    `slurmdbd`, and slurmd in 24.11. As of 24.11.0rc1, `SIGQUIT` is\n    identical to `SIGINT` and `SIGTERM` for these daemons, but this\n    change was not documented.\n  * Fix not considering nodes marked for reboot without ASAP in\n    the scheduler.\n  * Remove the `boot^` state on unexpected node reboot after return\n    to service.\n  * Do not allow new jobs to start on a node which is being\n    rebooted with the flag `nextstate=resume`.\n  * Prevent lower priority job running after cancelling an ASAP\n    reboot.\n  * Fix srun jobs starting on `nextstate=resume` rebooting nodes.\n","status":"published","published":"2025-05-29T12:53:40Z","modified":"2026-02-04T02:55:20.221182Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2025:01752-1","title":"Security update for slurm_23_02","description":"This update for slurm_23_02 fixes the following issues:\n\n- CVE-2025-43904: an issue with permission handling for Coordinators within the accounting system allowed Coordinators\n  to promote a user to Administrator (bsc#1243666). \n","status":"published","published":"2025-05-29T12:54:31Z","modified":"2026-02-04T04:10:53.634462Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2025:01753-1","title":"Security update for slurm_20_11","description":"This update for slurm_20_11 fixes the following issues:\n\n- CVE-2025-43904: an issue with permission handling for Coordinators within the accounting system allowed Coordinators\n  to promote a user to Administrator (bsc#1243666).\n","status":"published","published":"2025-05-29T12:55:13Z","modified":"2026-02-04T04:07:58.792364Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2025:01755-1","title":"Security update for slurm_22_05","description":"This update for slurm_22_05 fixes the following issues:\n\n- CVE-2025-43904: an issue with permission handling for Coordinators within the accounting system allowed Coordinators\n  to promote a user to Administrator (bsc#1243666).\n","status":"published","published":"2025-05-29T14:37:35Z","modified":"2026-02-04T04:34:14.535568Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2025:01756-1","title":"Security update for slurm_22_05","description":"This update for slurm_22_05 fixes the following issues:\n\n- CVE-2025-43904: an issue with permission handling for Coordinators within the accounting system allowed Coordinators\n  to promote a user to Administrator (bsc#1243666).\n","status":"published","published":"2025-05-29T14:39:06Z","modified":"2026-02-04T03:54:37.57073Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2025:01757-1","title":"Security update for slurm_24_11","description":"This update for slurm_24_11 fixes the following issues:\n\nUpdate to version 24.11.5.\n\nSecurity issues fixed:\n  \n- CVE-2025-43904: an issue with permission handling for Coordinators within the accounting system allowed Coordinators\n  to promote a user to Administrator (bsc#1243666).\n\nOther changes and issues fixed:\n\n- Changes from version 24.11.5\n\n  * Return error to `scontrol` reboot on bad nodelists.\n  * `slurmrestd` - Report an error when QOS resolution fails for\n\tv0.0.40 endpoints.\n  * `slurmrestd` - Report an error when QOS resolution fails for\n\tv0.0.41 endpoints.\n  * `slurmrestd` - Report an error when QOS resolution fails for\n\tv0.0.42 endpoints.\n  * `data_parser/v0.0.42` - Added `+inline_enums` flag which\n\tmodifies the output when generating OpenAPI specification.\n\tIt causes enum arrays to not be defined in their own schema\n\twith references (`$ref`) to them. Instead they will be dumped\n\tinline.\n  * Fix binding error with `tres-bind map/mask` on partial node\n\tallocations.\n  * Fix `stepmgr` enabled steps being able to request features.\n  * Reject step creation if requested feature is not available\n\tin job.\n  * `slurmd` - Restrict listening for new incoming RPC requests\n\tfurther into startup.\n  * `slurmd` - Avoid `auth/slurm` related hangs of CLI commands\n\tduring startup and shutdown.\n  * `slurmctld` - Restrict processing new incoming RPC requests\n\tfurther into startup. Stop processing requests sooner during\n\tshutdown.\n  * `slurmcltd` - Avoid auth/slurm related hangs of CLI commands\n\tduring startup and shutdown.\n  * `slurmctld` - Avoid race condition during shutdown or\n\tereconfigure that could result in a crash due delayed\n\tprocessing of a connection while plugins are unloaded.\n  * Fix small memleak when getting the job list from the database.\n  * Fix incorrect printing of `%` escape characters when printing\n\tstdio fields for jobs.\n  * Fix padding parsing when printing stdio fields for jobs.\n  * Fix printing `%A` array job id when expanding patterns.\n  * Fix reservations causing jobs to be held for `Bad Constraints`.\n  * `switch/hpe_slingshot` - Prevent potential segfault on failed\n\tcurl request to the fabric manager.\n  * Fix printing incorrect array job id when expanding stdio file\n\tnames. The `%A` will now be substituted by the correct value.\n  * Fix printing incorrect array job id when expanding stdio file\n\tnames. The `%A` will now be substituted by the correct value.\n  * `switch/hpe_slingshot` - Fix VNI range not updating on slurmctld\n\trestart or reconfigre.\n  * Fix steps not being created when using certain combinations of\n\t`-c` and `-n` inferior to the jobs requested resources, when\n\tusing stepmgr and nodes are configured with\n\t`CPUs == Sockets*CoresPerSocket`.\n  * Permit configuring the number of retry attempts to destroy CXI\n\tservice via the new destroy_retries `SwitchParameter`.\n  * Do not reset `memory.high` and `memory.swap.max` in slurmd\n\tstartup or reconfigure as we are never really touching this\n\tin `slurmd`.\n  * Fix reconfigure failure of slurmd when it has been started\n\tmanually and the `CoreSpecLimits` have been removed from\n\t`slurm.conf`.\n  * Set or reset CoreSpec limits when slurmd is reconfigured and\n\tit was started with systemd.\n  * `switch/hpe-slingshot` - Make sure the slurmctld can free\n\tstep VNIs after the controller restarts or reconfigures while\n\tthe job is running.\n  * Fix backup `slurmctld` failure on 2nd takeover.\n  \n- Changes from version 24.11.4\n\n  * `slurmctld`,`slurmrestd` - Avoid possible race condition that\n    could have caused process to crash when listener socket was\n    closed while accepting a new connection.\n  * `slurmrestd` - Avoid race condition that could have resulted\n\tin address logged for a UNIX socket to be incorrect.\n  * `slurmrestd` - Fix parameters in OpenAPI specification for the\n    following endpoints to have `job_id` field:\n    ```\n    GET /slurm/v0.0.40/jobs/state/\n    GET /slurm/v0.0.41/jobs/state/\n    GET /slurm/v0.0.42/jobs/state/\n    GET /slurm/v0.0.43/jobs/state/\n    ```\n  * `slurmd` - Fix tracking of thread counts that could cause\n\tincoming connections to be ignored after burst of simultaneous\n\tincoming connections that trigger delayed response logic.\n  * Avoid unnecessary `SRUN_TIMEOUT` forwarding to `stepmgr`.\n  * Fix jobs being scheduled on higher weighted powered down nodes.\n  * Fix how backfill scheduler filters nodes from the available\n\tnodes based on exclusive user and `mcs_label` requirements.\n  * `acct_gather_energy/{gpu,ipmi}` - Fix potential energy\n\tconsumption adjustment calculation underflow.\n  * `acct_gather_energy/ipmi` - Fix regression introduced in 24.05.5\n\t(which introduced the new way of preserving energy measurements\n\tthrough slurmd restarts) when `EnergyIPMICalcAdjustment=yes`.\n  * Prevent `slurmctld` deadlock in the assoc mgr.\n  * Fix memory leak when `RestrictedCoresPerGPU` is enabled.\n  * Fix preemptor jobs not entering execution due to wrong\n\tcalculation of accounting policy limits.\n  * Fix certain job requests that were incorrectly denied with\n\tnode configuration unavailable error.\n  * `slurmd` - Avoid crash due when slurmd has a communications\n\tfailure with `slurmstepd`.\n  * Fix memory leak when parsing yaml input.\n  * Prevent `slurmctld` from showing error message about `PreemptMode=GANG`\n\tbeing a cluster-wide option for `scontrol update part` calls\n\tthat don't attempt to modify partition PreemptMode.\n  * Fix setting `GANG` preemption on partition when updating\n\t`PreemptMode` with `scontrol`.\n  * Fix `CoreSpec` and `MemSpec` limits not being removed\n\tfrom previously configured slurmd.\n  * Avoid race condition that could lead to a deadlock when `slurmd`,\n\t`slurmstepd`, `slurmctld`, `slurmrestd` or `sackd` have a fatal\n\tevent.\n  * Fix jobs using `--ntasks-per-node` and `--mem` keep pending\n\tforever\twhen the requested mem divided by the number of CPUs\n\twill surpass the configured `MaxMemPerCPU`.\n  * `slurmd` - Fix address logged upon new incoming RPC connection\n    from `INVALID` to IP address.\n  * Fix memory leak when retrieving reservations. This affects\n\t`scontrol`, `sinfo`, `sview`, and the following `slurmrestd`\n\tendpoints:\n    `GET /slurm/{any_data_parser}/reservation/{reservation_name}`\n    `GET /slurm/{any_data_parser}/reservations`\n  * Log warning instead of `debuflags=conmgr` gated log when\n\tdeferring new incoming connections when number of active\n\tconnections exceed `conmgr_max_connections`.\n  * Avoid race condition that could result in worker thread pool\n\tnot activating all threads at once after a reconfigure resulting\n\tin lower utilization of available CPU threads until enough\n\tinternal activity wakes up all threads in the worker pool.\n  * Avoid theoretical race condition that could result in new\n\tincoming RPC\n    socket connections being ignored after reconfigure.\n  * slurmd - Avoid race condition that could result in a state\n\twhere\tnew incoming RPC connections will always be ignored.\n  * Add ReconfigFlags=KeepNodeStateFuture to restore saved `FUTURE`\n\tnode state on restart and reconfig instead of reverting to\n\t`FUTURE` state. This will be made the default in 25.05.\n  * Fix case where hetjob submit would cause `slurmctld` to crash.\n  * Fix jobs using `--cpus-per-gpu` and `--mem` keep pending forever\n\twhen the requested mem divided by the number of CPUs will surpass\n\tthe configured `MaxMemPerCPU`.\n  * Enforce that jobs using `--mem` and several `--*-per-*` options\n\tdo not violate the `MaxMemPerCPU` in place.\n  * `slurmctld` - Fix use-cases of jobs incorrectly pending held\n\twhen `--prefer` features are not initially satisfied.\n  * `slurmctld` - Fix jobs incorrectly held when `--prefer` not\n\tsatisfied in some use-cases.\n  * Ensure `RestrictedCoresPerGPU` and `CoreSpecCount` don't overlap.\n\n- Changes from version 24.11.3\n\n  * Fix database cluster ID generation not being random.\n  * Fix a regression in which `slurmd -G` gave no output.\n  * Fix a long-standing crash in `slurmctld` after updating a\n    reservation with an empty nodelist. The crash could occur\n\tafter restarting slurmctld, or if downing/draining a node\n\tin the reservation with the `REPLACE` or `REPLACE_DOWN` flag.\n  * Avoid changing process name to '`watch`' from original daemon name.\n    This could potentially breaking some monitoring scripts.\n  * Avoid `slurmctld` being killed by `SIGALRM` due to race condition\n    at startup.\n  * Fix race condition in slurmrestd that resulted in '`Requested\n    data_parser plugin does not support OpenAPI plugin`' error being\n\treturned for valid endpoints.\n  * Fix race between `task/cgroup` CPUset and `jobacctgather/cgroup`.\n    The first was removing the pid from `task_X` cgroup directory\n\tcausing memory limits to not being applied.\n  * If multiple partitions are requested, set the `SLURM_JOB_PARTITION`\n    output environment variable to the partition in which the job is\n\trunning for `salloc` and `srun` in order to match the documentation\n\tand the behavior of `sbatch`.\n  * `srun` - Fixed wrongly constructed `SLURM_CPU_BIND` env variable\n    that could get propagated to downward srun calls in certain mpi\n    environments, causing launch failures.\n  * Don't print misleading errors for stepmgr enabled steps.\n  * `slurmrestd` - Avoid connection to slurmdbd for the following\n    endpoints:\n\t```\n    GET /slurm/v0.0.41/jobs\n    GET /slurm/v0.0.41/job/{job_id}\n\t```\n  * `slurmrestd` - Avoid connection to slurmdbd for the following\n    endpoints:\n\t```\n    GET /slurm/v0.0.40/jobs\n    GET /slurm/v0.0.40/job/{job_id}\n\t```\n  * `slurmrestd` - Fix possible memory leak when parsing arrays with\n    `data_parser/v0.0.40`.\n  * `slurmrestd` - Fix possible memory leak when parsing arrays with\n    `data_parser/v0.0.41`.\n  * `slurmrestd` - Fix possible memory leak when parsing arrays with\n    `data_parser/v0.0.42`.\n  \n- Changes from version 24.11.2\n\n  * Fix segfault when submitting `--test-only` jobs that can\n    preempt.\n  * Fix regression introduced in 23.11 that prevented the\n    following flags from being added to a reservation on an\n    update: `DAILY`, `HOURLY`, `WEEKLY`, `WEEKDAY`, and `WEEKEND`.\n  * Fix crash and issues evaluating job's suitability for running\n    in nodes with already suspended job(s) there.\n  * `slurmctld` will ensure that healthy nodes are not reported as\n    `UnavailableNodes` in job reason codes.\n  * Fix handling of jobs submitted to a current reservation with\n    flags `OVERLAP,FLEX` or `OVERLAP,ANY_NODES` when it overlaps nodes\n    with a future maintenance reservation. When a job submission\n    had a time limit that overlapped with the future maintenance\n    reservation, it was rejected. Now the job is accepted but\n    stays pending with the reason '`ReqNodeNotAvail, Reserved for\n    maintenance`'.\n  * `pam_slurm_adopt` - avoid errors when explicitly setting some\n    arguments to the default value.\n  * Fix QOS preemption with `PreemptMode=SUSPEND`.\n  * `slurmdbd` - When changing a user's name update lineage at the\n    same time.\n  * Fix regression in 24.11 in which `burst_buffer.lua` does not\n    inherit the `SLURM_CONF` environment variable from `slurmctld` and\n    fails to run if slurm.conf is in a non-standard location.\n  * Fix memory leak in slurmctld if `select/linear` and the\n    `PreemptParameters=reclaim_licenses` options are both set in\n    `slurm.conf`.  Regression in 24.11.1.\n  * Fix running jobs, that requested multiple partitions, from\n    potentially being set to the wrong partition on restart.\n  * `switch/hpe_slingshot` - Fix compatibility with newer cxi\n    drivers, specifically when specifying `disable_rdzv_get`.\n  * Add `ABORT_ON_FATAL` environment variable to capture a backtrace\n    from any `fatal()` message.\n  * Fix printing invalid address in rate limiting log statement.\n  * `sched/backfill` - Fix node state `PLANNED` not being cleared from\n    fully allocated nodes during a backfill cycle.\n  * `select/cons_tres` - Fix future planning of jobs with\n    `bf_licenses`.\n  * Prevent redundant '`on_data returned rc: Rate limit exceeded,\n    please retry momentarily`' error message from being printed in\n    slurmctld logs.\n  * Fix loading non-default QOS on pending jobs from pre-24.11\n    state.\n  * Fix pending jobs displaying `QOS=(null)` when not explicitly\n    requesting a QOS.\n  * Fix segfault issue from job record with no `job_resrcs`.\n  * Fix failing `sacctmgr delete/modify/show` account operations\n    with `where` clauses.\n  * Fix regression in 24.11 in which Slurm daemons started\n    catching several `SIGTSTP`, `SIGTTIN` and `SIGUSR1` signals and\n    ignored them, while before they were not ignoring them. This\n    also caused slurmctld to not being able to shutdown after a\n    `SIGTSTP` because slurmscriptd caught the signal and stopped\n    while slurmctld ignored it. Unify and fix these situations and\n    get back to the previous behavior for these signals.\n  * Document that `SIGQUIT` is no longer ignored by `slurmctld`,\n    `slurmdbd`, and slurmd in 24.11. As of 24.11.0rc1, `SIGQUIT` is\n    identical to `SIGINT` and `SIGTERM` for these daemons, but this\n    change was not documented.\n  * Fix not considering nodes marked for reboot without ASAP in\n    the scheduler.\n  * Remove the `boot^` state on unexpected node reboot after return\n    to service.\n  * Do not allow new jobs to start on a node which is being\n    rebooted with the flag `nextstate=resume`.\n  * Prevent lower priority job running after cancelling an ASAP\n    reboot.\n  * Fix srun jobs starting on `nextstate=resume` rebooting nodes.\n","status":"published","published":"2025-05-29T14:47:58Z","modified":"2026-02-04T02:21:03.488452Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2025:01758-1","title":"Security update for slurm_23_02","description":"This update for slurm_23_02 fixes the following issues:\n\n- CVE-2025-43904: an issue with permission handling for Coordinators within the accounting system allowed Coordinators\n  to promote a user to Administrator (bsc#1243666).\n","status":"published","published":"2025-05-29T14:48:59Z","modified":"2026-02-04T02:49:06.047544Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2025:01759-1","title":"Security update for slurm","description":"This update for slurm fixes the following issues:\n\n- CVE-2025-43904: an issue with permission handling for Coordinators within the accounting system allowed Coordinators\n  to promote a user to Administrator (bsc#1243666).\n","status":"published","published":"2025-05-29T14:53:55Z","modified":"2026-02-04T02:35:21.625854Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2025:01760-1","title":"Security update for slurm","description":"This update for slurm fixes the following issues:\n\n- CVE-2025-43904: an issue with permission handling for Coordinators within the accounting system allowed Coordinators\n  to promote a user to Administrator (bsc#1243666).\n","status":"published","published":"2025-05-29T14:54:19Z","modified":"2025-05-30T11:59:34.234624Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2025:01761-1","title":"Security update for slurm_24_11","description":"This update for slurm_24_11 fixes the following issues:\n\nUpdate to version 24.11.5.\n\nSecurity issues fixed:\n\n- CVE-2025-43904: an issue with permission handling for Coordinators within the accounting system allowed Coordinators\n  to promote a user to Administrator (bsc#1243666).\n\nOther changes and issues fixed:\n\n- Changes from version 24.11.5\n\n  * Return error to `scontrol` reboot on bad nodelists.\n  * `slurmrestd` - Report an error when QOS resolution fails for\n\tv0.0.40 endpoints.\n  * `slurmrestd` - Report an error when QOS resolution fails for\n\tv0.0.41 endpoints.\n  * `slurmrestd` - Report an error when QOS resolution fails for\n\tv0.0.42 endpoints.\n  * `data_parser/v0.0.42` - Added `+inline_enums` flag which\n\tmodifies the output when generating OpenAPI specification.\n\tIt causes enum arrays to not be defined in their own schema\n\twith references (`$ref`) to them. Instead they will be dumped\n\tinline.\n  * Fix binding error with `tres-bind map/mask` on partial node\n\tallocations.\n  * Fix `stepmgr` enabled steps being able to request features.\n  * Reject step creation if requested feature is not available\n\tin job.\n  * `slurmd` - Restrict listening for new incoming RPC requests\n\tfurther into startup.\n  * `slurmd` - Avoid `auth/slurm` related hangs of CLI commands\n\tduring startup and shutdown.\n  * `slurmctld` - Restrict processing new incoming RPC requests\n\tfurther into startup. Stop processing requests sooner during\n\tshutdown.\n  * `slurmcltd` - Avoid auth/slurm related hangs of CLI commands\n\tduring startup and shutdown.\n  * `slurmctld` - Avoid race condition during shutdown or\n\tereconfigure that could result in a crash due delayed\n\tprocessing of a connection while plugins are unloaded.\n  * Fix small memleak when getting the job list from the database.\n  * Fix incorrect printing of `%` escape characters when printing\n\tstdio fields for jobs.\n  * Fix padding parsing when printing stdio fields for jobs.\n  * Fix printing `%A` array job id when expanding patterns.\n  * Fix reservations causing jobs to be held for `Bad Constraints`.\n  * `switch/hpe_slingshot` - Prevent potential segfault on failed\n\tcurl request to the fabric manager.\n  * Fix printing incorrect array job id when expanding stdio file\n\tnames. The `%A` will now be substituted by the correct value.\n  * Fix printing incorrect array job id when expanding stdio file\n\tnames. The `%A` will now be substituted by the correct value.\n  * `switch/hpe_slingshot` - Fix VNI range not updating on slurmctld\n\trestart or reconfigre.\n  * Fix steps not being created when using certain combinations of\n\t`-c` and `-n` inferior to the jobs requested resources, when\n\tusing stepmgr and nodes are configured with\n\t`CPUs == Sockets*CoresPerSocket`.\n  * Permit configuring the number of retry attempts to destroy CXI\n\tservice via the new destroy_retries `SwitchParameter`.\n  * Do not reset `memory.high` and `memory.swap.max` in slurmd\n\tstartup or reconfigure as we are never really touching this\n\tin `slurmd`.\n  * Fix reconfigure failure of slurmd when it has been started\n\tmanually and the `CoreSpecLimits` have been removed from\n\t`slurm.conf`.\n  * Set or reset CoreSpec limits when slurmd is reconfigured and\n\tit was started with systemd.\n  * `switch/hpe-slingshot` - Make sure the slurmctld can free\n\tstep VNIs after the controller restarts or reconfigures while\n\tthe job is running.\n  * Fix backup `slurmctld` failure on 2nd takeover.\n  \n- Changes from version 24.11.4\n\n  * `slurmctld`,`slurmrestd` - Avoid possible race condition that\n    could have caused process to crash when listener socket was\n    closed while accepting a new connection.\n  * `slurmrestd` - Avoid race condition that could have resulted\n\tin address logged for a UNIX socket to be incorrect.\n  * `slurmrestd` - Fix parameters in OpenAPI specification for the\n    following endpoints to have `job_id` field:\n    ```\n    GET /slurm/v0.0.40/jobs/state/\n    GET /slurm/v0.0.41/jobs/state/\n    GET /slurm/v0.0.42/jobs/state/\n    GET /slurm/v0.0.43/jobs/state/\n    ```\n  * `slurmd` - Fix tracking of thread counts that could cause\n\tincoming connections to be ignored after burst of simultaneous\n\tincoming connections that trigger delayed response logic.\n  * Avoid unnecessary `SRUN_TIMEOUT` forwarding to `stepmgr`.\n  * Fix jobs being scheduled on higher weighted powered down nodes.\n  * Fix how backfill scheduler filters nodes from the available\n\tnodes based on exclusive user and `mcs_label` requirements.\n  * `acct_gather_energy/{gpu,ipmi}` - Fix potential energy\n\tconsumption adjustment calculation underflow.\n  * `acct_gather_energy/ipmi` - Fix regression introduced in 24.05.5\n\t(which introduced the new way of preserving energy measurements\n\tthrough slurmd restarts) when `EnergyIPMICalcAdjustment=yes`.\n  * Prevent `slurmctld` deadlock in the assoc mgr.\n  * Fix memory leak when `RestrictedCoresPerGPU` is enabled.\n  * Fix preemptor jobs not entering execution due to wrong\n\tcalculation of accounting policy limits.\n  * Fix certain job requests that were incorrectly denied with\n\tnode configuration unavailable error.\n  * `slurmd` - Avoid crash due when slurmd has a communications\n\tfailure with `slurmstepd`.\n  * Fix memory leak when parsing yaml input.\n  * Prevent `slurmctld` from showing error message about `PreemptMode=GANG`\n\tbeing a cluster-wide option for `scontrol update part` calls\n\tthat don't attempt to modify partition PreemptMode.\n  * Fix setting `GANG` preemption on partition when updating\n\t`PreemptMode` with `scontrol`.\n  * Fix `CoreSpec` and `MemSpec` limits not being removed\n\tfrom previously configured slurmd.\n  * Avoid race condition that could lead to a deadlock when `slurmd`,\n\t`slurmstepd`, `slurmctld`, `slurmrestd` or `sackd` have a fatal\n\tevent.\n  * Fix jobs using `--ntasks-per-node` and `--mem` keep pending\n\tforever\twhen the requested mem divided by the number of CPUs\n\twill surpass the configured `MaxMemPerCPU`.\n  * `slurmd` - Fix address logged upon new incoming RPC connection\n    from `INVALID` to IP address.\n  * Fix memory leak when retrieving reservations. This affects\n\t`scontrol`, `sinfo`, `sview`, and the following `slurmrestd`\n\tendpoints:\n    `GET /slurm/{any_data_parser}/reservation/{reservation_name}`\n    `GET /slurm/{any_data_parser}/reservations`\n  * Log warning instead of `debuflags=conmgr` gated log when\n\tdeferring new incoming connections when number of active\n\tconnections exceed `conmgr_max_connections`.\n  * Avoid race condition that could result in worker thread pool\n\tnot activating all threads at once after a reconfigure resulting\n\tin lower utilization of available CPU threads until enough\n\tinternal activity wakes up all threads in the worker pool.\n  * Avoid theoretical race condition that could result in new\n\tincoming RPC\n    socket connections being ignored after reconfigure.\n  * slurmd - Avoid race condition that could result in a state\n\twhere\tnew incoming RPC connections will always be ignored.\n  * Add ReconfigFlags=KeepNodeStateFuture to restore saved `FUTURE`\n\tnode state on restart and reconfig instead of reverting to\n\t`FUTURE` state. This will be made the default in 25.05.\n  * Fix case where hetjob submit would cause `slurmctld` to crash.\n  * Fix jobs using `--cpus-per-gpu` and `--mem` keep pending forever\n\twhen the requested mem divided by the number of CPUs will surpass\n\tthe configured `MaxMemPerCPU`.\n  * Enforce that jobs using `--mem` and several `--*-per-*` options\n\tdo not violate the `MaxMemPerCPU` in place.\n  * `slurmctld` - Fix use-cases of jobs incorrectly pending held\n\twhen `--prefer` features are not initially satisfied.\n  * `slurmctld` - Fix jobs incorrectly held when `--prefer` not\n\tsatisfied in some use-cases.\n  * Ensure `RestrictedCoresPerGPU` and `CoreSpecCount` don't overlap.\n\n- Changes from version 24.11.3\n\n  * Fix database cluster ID generation not being random.\n  * Fix a regression in which `slurmd -G` gave no output.\n  * Fix a long-standing crash in `slurmctld` after updating a\n    reservation with an empty nodelist. The crash could occur\n\tafter restarting slurmctld, or if downing/draining a node\n\tin the reservation with the `REPLACE` or `REPLACE_DOWN` flag.\n  * Avoid changing process name to '`watch`' from original daemon name.\n    This could potentially breaking some monitoring scripts.\n  * Avoid `slurmctld` being killed by `SIGALRM` due to race condition\n    at startup.\n  * Fix race condition in slurmrestd that resulted in '`Requested\n    data_parser plugin does not support OpenAPI plugin`' error being\n\treturned for valid endpoints.\n  * Fix race between `task/cgroup` CPUset and `jobacctgather/cgroup`.\n    The first was removing the pid from `task_X` cgroup directory\n\tcausing memory limits to not being applied.\n  * If multiple partitions are requested, set the `SLURM_JOB_PARTITION`\n    output environment variable to the partition in which the job is\n\trunning for `salloc` and `srun` in order to match the documentation\n\tand the behavior of `sbatch`.\n  * `srun` - Fixed wrongly constructed `SLURM_CPU_BIND` env variable\n    that could get propagated to downward srun calls in certain mpi\n    environments, causing launch failures.\n  * Don't print misleading errors for stepmgr enabled steps.\n  * `slurmrestd` - Avoid connection to slurmdbd for the following\n    endpoints:\n\t```\n    GET /slurm/v0.0.41/jobs\n    GET /slurm/v0.0.41/job/{job_id}\n\t```\n  * `slurmrestd` - Avoid connection to slurmdbd for the following\n    endpoints:\n\t```\n    GET /slurm/v0.0.40/jobs\n    GET /slurm/v0.0.40/job/{job_id}\n\t```\n  * `slurmrestd` - Fix possible memory leak when parsing arrays with\n    `data_parser/v0.0.40`.\n  * `slurmrestd` - Fix possible memory leak when parsing arrays with\n    `data_parser/v0.0.41`.\n  * `slurmrestd` - Fix possible memory leak when parsing arrays with\n    `data_parser/v0.0.42`.\n  \n- Changes from version 24.11.2\n  \n  * Fix segfault when submitting `--test-only` jobs that can\n    preempt.\n  * Fix regression introduced in 23.11 that prevented the\n    following flags from being added to a reservation on an\n    update: `DAILY`, `HOURLY`, `WEEKLY`, `WEEKDAY`, and `WEEKEND`.\n  * Fix crash and issues evaluating job's suitability for running\n    in nodes with already suspended job(s) there.\n  * `slurmctld` will ensure that healthy nodes are not reported as\n    `UnavailableNodes` in job reason codes.\n  * Fix handling of jobs submitted to a current reservation with\n    flags `OVERLAP,FLEX` or `OVERLAP,ANY_NODES` when it overlaps nodes\n    with a future maintenance reservation. When a job submission\n    had a time limit that overlapped with the future maintenance\n    reservation, it was rejected. Now the job is accepted but\n    stays pending with the reason '`ReqNodeNotAvail, Reserved for\n    maintenance`'.\n  * `pam_slurm_adopt` - avoid errors when explicitly setting some\n    arguments to the default value.\n  * Fix QOS preemption with `PreemptMode=SUSPEND`.\n  * `slurmdbd` - When changing a user's name update lineage at the\n    same time.\n  * Fix regression in 24.11 in which `burst_buffer.lua` does not\n    inherit the `SLURM_CONF` environment variable from `slurmctld` and\n    fails to run if slurm.conf is in a non-standard location.\n  * Fix memory leak in slurmctld if `select/linear` and the\n    `PreemptParameters=reclaim_licenses` options are both set in\n    `slurm.conf`.  Regression in 24.11.1.\n  * Fix running jobs, that requested multiple partitions, from\n    potentially being set to the wrong partition on restart.\n  * `switch/hpe_slingshot` - Fix compatibility with newer cxi\n    drivers, specifically when specifying `disable_rdzv_get`.\n  * Add `ABORT_ON_FATAL` environment variable to capture a backtrace\n    from any `fatal()` message.\n  * Fix printing invalid address in rate limiting log statement.\n  * `sched/backfill` - Fix node state `PLANNED` not being cleared from\n    fully allocated nodes during a backfill cycle.\n  * `select/cons_tres` - Fix future planning of jobs with\n    `bf_licenses`.\n  * Prevent redundant '`on_data returned rc: Rate limit exceeded,\n    please retry momentarily`' error message from being printed in\n    slurmctld logs.\n  * Fix loading non-default QOS on pending jobs from pre-24.11\n    state.\n  * Fix pending jobs displaying `QOS=(null)` when not explicitly\n    requesting a QOS.\n  * Fix segfault issue from job record with no `job_resrcs`.\n  * Fix failing `sacctmgr delete/modify/show` account operations\n    with `where` clauses.\n  * Fix regression in 24.11 in which Slurm daemons started\n    catching several `SIGTSTP`, `SIGTTIN` and `SIGUSR1` signals and\n    ignored them, while before they were not ignoring them. This\n    also caused slurmctld to not being able to shutdown after a\n    `SIGTSTP` because slurmscriptd caught the signal and stopped\n    while slurmctld ignored it. Unify and fix these situations and\n    get back to the previous behavior for these signals.\n  * Document that `SIGQUIT` is no longer ignored by `slurmctld`,\n    `slurmdbd`, and slurmd in 24.11. As of 24.11.0rc1, `SIGQUIT` is\n    identical to `SIGINT` and `SIGTERM` for these daemons, but this\n    change was not documented.\n  * Fix not considering nodes marked for reboot without ASAP in\n    the scheduler.\n  * Remove the `boot^` state on unexpected node reboot after return\n    to service.\n  * Do not allow new jobs to start on a node which is being\n    rebooted with the flag `nextstate=resume`.\n  * Prevent lower priority job running after cancelling an ASAP\n    reboot.\n  * Fix srun jobs starting on `nextstate=resume` rebooting nodes.\n","status":"published","published":"2025-05-29T16:08:32Z","modified":"2026-02-04T03:06:12.302291Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2025:02779-1","title":"Security update for slurm","description":"This update for slurm fixes the following issues:\n\n- CVE-2025-43904: an issue with permission handling for Coordinators within the accounting system allowed Coordinators\n  to promote a user to Administrator (bsc#1243666).\n","status":"published","published":"2025-08-13T06:57:34Z","modified":"2026-02-04T03:37:41.276655Z","updated_at":"2026-11-02T15:53:57.111474Z"},{"id":"USN-8236-1","title":"slurm-wlm vulnerabilities","description":"It was discovered that Slurm did not correctly handle certain file system\noperations. An attacker could possibly use this issue to modify files or\nleak sensitive information. This issue only affected Ubuntu 22.04 LTS.\n(CVE-2023-41914)\n\nRyan Hall discovered that Slurm did not correctly enforce certain message\nintegrity checks. An attacker could possibly use this issue to bypass\nintegrity checks. This issue only affected Ubuntu 22.04 LTS.\n(CVE-2023-49933)\n\nRyan Hall discovered that Slurm did not correctly handle certain memory\noperations. An attacker could possibly use this issue to cause a denial of\nservice or execute arbitrary code. This issue only affected Ubuntu 22.04\nLTS. (CVE-2023-49937)\n\nRyan Hall discovered that Slurm did not correctly handle certain access\ncontrol mechanisms. An attacker could possibly use this issue to modify\nfiles or leak sensitive information. This issue only affected Ubuntu 22.04\nLTS. (CVE-2023-49938)\n\nIt was discovered that Slurm did not correctly handle user promotion. An\nattacker could possibly use this issue to promote themselves to an\nadministrator. (CVE-2025-43904)","status":"published","published":"2026-05-06T05:43:00Z","modified":"2026-05-08T12:33:13.607305049Z","updated_at":"2026-11-02T16:58:22.951676Z"}]}}