How severe is CVE-2016-6264?

CVE-2016-6264 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2016-6264 being actively exploited?

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

What products are affected by CVE-2016-6264?

CVE-2016-6264 primarily affects Uclibc. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2016-6264?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2016-6264 published?

CVE-2016-6264 was published on 2017-01-27 and last updated on 2026-06-17.

CVE-2016-6264

CVE-2016-6264 is a high-severity vulnerability in Uclibc with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 3% (84th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Uclibc
Published: 2017-01-27
Last modified: 2026-06-17

Description

Integer signedness error in libc/string/arm/memset.S in uClibc and uClibc-ng before 1.0.16 allows context-dependent attackers to cause a denial of service (crash) via a negative length value to the memset function.

Frequently asked questions

What is CVE-2016-6264?: Integer signedness error in libc/string/arm/memset.S in uClibc and uClibc-ng before 1.0.16 allows context-dependent attackers to cause a denial of service (crash) via a negative length value to the memset function.
How severe is CVE-2016-6264?: CVE-2016-6264 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2016-6264 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (84th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-6264?: CVE-2016-6264 primarily affects Uclibc. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2016-6264?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2016-6264 published?: CVE-2016-6264 was published on 2017-01-27 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:a:uclibc:uclibc:-:*:*:*:*:*:*:*
cpe:2.3:a:uclibc-ng_project:uclibc-ng:*:*:*:*:*:*:*:*

More vulnerabilities in Uclibc

CVE-2022-29503 — Critical (CVSS 9.8): A memory corruption vulnerability exists in the libpthread linuxthreads functionality of uClibC 0.9.33.2 and uClibC-ng…
CVE-2017-9728 — Critical (CVSS 9.8): In uClibc 0.9.33.2, there is an out-of-bounds read in the get_subexp function in misc/regex/regexec.c when processing a…
CVE-2021-43523 — Critical (CVSS 9.6): In uClibc and uClibc-ng before 1.0.39, incorrect handling of special characters in domain names returned by DNS servers…
CVE-2017-9729 — High (CVSS 7.5): In uClibc 0.9.33.2, there is stack exhaustion (uncontrolled recursion) in the check_dst_limits_calc_pos_1 function in…
CVE-2022-30295 — Medium (CVSS 6.5): uClibc-ng through 1.0.40 and uClibc through 0.9.33.2 use predictable DNS transaction IDs that may lead to DNS cache…

All CVEs affecting Uclibc →