CVE-2019-20426

Exp

In the Lustre file system before 2.12.3, the ptlrpc module has an out-of-bounds access and panic due to the lack of validation for specific fields of packets sent by a client. In the function ldlm_cancel_hpreq_check, there is no lock_count bounds check.

Published: 2020-01-27 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-20426 is rated High Exploit Risk (69.5/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.66%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2019-20426

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2019-20426

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.77% 0.66% -0.11%
2 2025-11-18 0.66% 0.77% +0.11%
3 2025-03-30 — 0.66% —

Full EPSS history (13 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-20426

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]
7.8 2.0 HIGH
AV:N/AC:L/Au:N/C:N/I:N/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:C)
Complete availability impact.
 10.0 6.9 [email protected]

Weakness enumeration for CVE-2019-20426

OS Trackers for CVE-2019-20426

vendor priority summary link
ubuntu low CVE-2019-20426 low priority: Ubuntu including 107 source packages (linux, linux-aws, …), 1056 status rows across 11 suites (bionic, eoan, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 743, needed 168, ignored 74, not-affected 71. https://ubuntu.com/security/CVE-2019-20426

Affected software / configurations for CVE-2019-20426

Vendor Product Version Raw CPE
lustre lustre < 2.12.3 cpe:2.3:a:lustre:lustre:*:*:*:*:*:*:*:*

References for CVE-2019-20426

URL Tags
http://lustre.org/ Product Vendor Advisory
http://wiki.lustre.org/Lustre_2.12.3_Changelog Release Notes Vendor Advisory
https://jira.whamcloud.com/browse/LU-12614 Exploit Third Party Advisory
https://review.whamcloud.com/#/c/36107/ Third Party Advisory
cvelogic Threat Intelligence