CVE-2026-3904

MEDIUM
6.2
CVSS Score
Published: March 11, 2026 at 01:19 PM UTC
Updated: October 15, 2026 at 01:12 AM UTC
5 products affected across 3 vendorsGlibcSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP FirmwareSiplus S7-1500 CPU 1518-4 Pn /dp MFP Firmware

Using glibc by The GNU C Library?

Get instant alerts when new vulnerabilities affect glibc - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.2
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

Calling NSS-backed functions that support caching via nscd may call the nscd client side code and in the GNU C Library version 2.36 under high load on x86_64 systems, the client may call memcmp on inputs that are concurrently modified by other processes or threads and crash. The nscd client in the GNU C Library uses the memcmp function with inputs that may be concurrently modified by another thread, potentially resulting in spurious cache misses, which in itself is not a security issue.  However in the GNU C Library version 2.36 an optimized implementation of memcmp was introduced for x86_64 which could crash when invoked with such undefined behaviour, turning this into a potential crash of the nscd client and the application that uses it. This implementation was backported to the 2.35 branch, making the nscd client in that branch vulnerable as well.  Subsequently, the fix for this issue was backported to all vulnerable branches in the GNU C Library repository. It is advised that distributions that may have cherry-picked the memcpy SSE2 optimization in their copy of the GNU C Library, also apply the fix to avoid the potential crash in the nscd client.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.35 ≤ v < 2.37
Affected range stops below 2.37, so it looks safe — our inference, not a vendor statement
2.35 ≤ v < 2.372.35
Affected range stops below 2.37, so it looks safe — our inference, not a vendor statement
V3.1.5 ≤ v < V3.1.63.1.5
Affected range stops below V3.1.6, so it looks safe — our inference, not a vendor statement
V3.1.5 ≤ v < V3.1.63.1.5
Affected range stops below V3.1.6, so it looks safe — our inference, not a vendor statement
V3.1.5 ≤ v < V3.1.63.1.5
Affected range stops below V3.1.6, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.2MEDIUM134c704f-9b21-4f2e-91b3-4a467353bcc0
Attack Vector
LOCAL
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-366

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card