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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 5.5 · gnuNVD modified 2026-10-14 07:16
Affected (CPE criteria) 1
cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:x86:*
References 9
- http://www.securityfocus.com/bid/106835 Third Party Advisory, VDB Entry
- https://security.gentoo.org/glsa/202006-04
- https://sourceware.org/bugzilla/show_bug.cgi?id=24155 Exploit, Issue Tracking, Third Party Advisory
- https://sourceware.org/ml/libc-alpha/2019-02/msg00041.html Mailing List, Third Party Advisory
- http://www.securityfocus.com/bid/106835 Third Party Advisory, VDB Entry
- https://security.gentoo.org/glsa/202006-04
- https://sourceware.org/bugzilla/show_bug.cgi?id=24155 Exploit, Issue Tracking, Third Party Advisory
- https://sourceware.org/ml/libc-alpha/2019-02/msg00041.html Mailing List, Third Party Advisory
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html