{
  "cveId": "CVE-2026-3904",
  "url": "https://patchblox.com/security/cve/CVE-2026-3904",
  "summary": "CVE-2026-3904 is fixed in glibc on 1 platform, first by DEBIAN-CVE-2026-3904, released March 11, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "Calling NSS-backed functions that support caching via nscd may call the \nnscd client side code and in the GNU C Library version 2.36 under high \nload on x86_64 systems, the client may call memcmp on inputs that are \nconcurrently modified by other processes or threads and crash.\n\n\n\n\nThe nscd client in the GNU C Library uses the memcmp function with \ninputs that may be concurrently modified by another thread, potentially \nresulting in spurious cache misses, which in itself is not a security \nissue.\u00A0 However in the GNU C Library version 2.36 an optimized \nimplementation of memcmp was introduced for x86_64 which could crash \nwhen invoked with such undefined behaviour, turning this into a \npotential crash of the nscd client and the application that uses it. \nThis implementation was backported to the 2.35 branch, making the nscd \nclient in that branch vulnerable as well.\u00A0 Subsequently, the fix for \nthis issue was backported to all vulnerable branches in the GNU C \nLibrary repository.\n\n\nIt is",
  "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.\u00A0 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.\u00A0 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.",
  "published": "2026-03-11T14:16:30Z",
  "severity": "Moderate",
  "cvss": 6.2,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "cwe": "Race Condition within a Thread",
  "epss": 0.00164,
  "epssPercentile": 0.05669,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "vendorAdvisory": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-3904",
  "fixes": [
    {
      "platform": "linux",
      "product": "glibc",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "2.36-9",
      "fix": "DEBIAN-CVE-2026-3904",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-3904",
      "released": "2026-03-11T14:16:30Z"
    },
    {
      "platform": "linux",
      "product": "glibc",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "2.36-9",
      "fix": "DEBIAN-CVE-2026-3904",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-3904",
      "released": "2026-03-11T14:16:30Z"
    },
    {
      "platform": "linux",
      "product": "glibc",
      "release": "Debian 14",
      "fixedVersion": "2.36-9",
      "fix": "DEBIAN-CVE-2026-3904",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-3904",
      "released": "2026-03-11T14:16:30Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T06:59:42Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}