How severe is CVE-2019-7309?

CVE-2019-7309 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2019-7309 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (45th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-7309?

CVE-2019-7309 affects Gnu Glibc. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2019-7309?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2019-7309 published?

CVE-2019-7309 was published on 2019-02-03 and last updated on 2026-06-17.

CVE-2019-7309

CVE-2019-7309 is a medium-severity vulnerability in Gnu Glibc with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 5.5)
CVSS v2: 2.1
EPSS exploit prediction: 1% (45th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Gnu Glibc
Published: 2019-02-03
Last modified: 2026-06-17

Description

In the GNU C Library (aka glibc or libc6) through 2.29, the memcmp function for the x32 architecture can incorrectly return zero (indicating that the inputs are equal) because the RDX most significant bit is mishandled.

Frequently asked questions

What is CVE-2019-7309?: In the GNU C Library (aka glibc or libc6) through 2.29, the memcmp function for the x32 architecture can incorrectly return zero (indicating that the inputs are equal) because the RDX most significant bit is mishandled.
How severe is CVE-2019-7309?: CVE-2019-7309 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2019-7309 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (45th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-7309?: CVE-2019-7309 affects Gnu Glibc. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-7309?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2019-7309 published?: CVE-2019-7309 was published on 2019-02-03 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:x86:*

More vulnerabilities in Gnu Glibc

CVE-2015-0235 — Critical (CVSS 10.0): Heap-based buffer overflow in the __nss_hostname_digits_dots function in glibc 2.2, and other 2.x versions before 2.18,…
CVE-2026-5450 — Critical (CVSS 9.8): Calling the scanf family of functions with a %mc (malloc'd character match) in the GNU C Library version 2.7 to version…
CVE-2023-25139 — Critical (CVSS 9.8): sprintf in the GNU C Library (glibc) 2.37 has a buffer overflow (out-of-bounds write) in some situations with a correct…
CVE-2022-23219 — Critical (CVSS 9.8): The deprecated compatibility function clnt_create in the sunrpc module of the GNU C Library (aka glibc) through 2.34…
CVE-2022-23218 — Critical (CVSS 9.8): The deprecated compatibility function svcunix_create in the sunrpc module of the GNU C Library (aka glibc) through 2.34…
CVE-2021-33574 — Critical (CVSS 9.8): The mq_notify function in the GNU C Library (aka glibc) versions 2.32 and 2.33 has a use-after-free. It may use the…

All CVEs affecting Gnu Glibc →