Skip to content
Fencer Intel
critical 9.8

CVE-2019-6438 json

SchedMD Slurm before 17.11.13 and 18.x before 18.08.5 mishandles 32-bit systems.

published 7y ago modified 4mo ago also EUVD-2019-15999

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

SchedMD Slurm before 17.11.13 and 18.x before 18.08.5 mishandles 32-bit systems.

Patch / fix

  • schedmd slurm 17.11.13, 18.08.5
  • slurm-llnl Ubuntu Pro 14.04 LTS 2.6.5-1ubuntu0.1~esm4
  • slurm-llnl Ubuntu Pro 16.04 LTS 15.08.7-1ubuntu0.1~esm3
  • slurm-llnl Ubuntu Pro 18.04 LTS 17.11.2-1ubuntu0.1~esm3

ubuntu advisories UBUNTU-CVE-2019-6438

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • pdsh SLE Module for HPC 12 2.34-7.32.1
  • slurm_20_11 SLE Module for HPC 12 20.11.4-3.5.1
  • pdsh_slurm_18_08 SLE Module for HPC 12 2.34-7.32.1
  • pdsh_slurm_20_02 SLE Module for HPC 12 2.34-7.32.1
  • pdsh_slurm_20_11 SLE Module for HPC 12 2.34-7.32.1
  • slurm_20_02 SLE Module for HPC 12 20.02.3-3.5.1
  • pdsh_slurm_18_08 SLE Module for HPC 12 2.34-7.26.2
  • pdsh_slurm_20_02 SLE Module for HPC 12 2.34-7.26.2

suse advisories SUSE-SU-2021:0773-1SUSE-SU-2020:2607-1SUSE-SU-2020:0443-1SUSE-SU-2020:0434-1SUSE-SU-2019:3385-1SUSE-SU-2019:3080-1

  • slurm openSUSE Tumbleweed 21.08.1-1.1
  • slurm openSUSE Leap 15.0 17.11.13-lp150.5.20.1

opensuse advisories openSUSE-SU-2024:11389-1openSUSE-SU-2019:1264-1

Is CVE-2019-6438 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.33% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.