Skip to content
Fencer Intel
low 3.7

CVE-2026-97399 json

One-byte overread in strncasecmp on Power8

published last mo. modified last mo. also EUVD-2026-88320

cvss
3.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 20%
public exploits
0
none known

Summary

The strncasecmp function in the GNU C Library 2.24 and later optimized for the Power8 architecture may read one byte beyond the input size limit, which may crash a program when that byte is not readable.

This condition may happen when the input strings to the strncasecmp function are attacker controlled in an application and they match all the way up to the edge of their page and the neighbouring page is either not mapped or is not readable.

Patch / fix

  • The GNU C Library glibc 2.45
  • glibc Debian 14 2.43-7

debian advisories DEBIAN-CVE-2026-97399

  • glibc Linux Micro 6.1 2.38-slfo.1.1_11.1
  • glibc Linux Micro 6.0 2.38-159998.1.1
  • glibc SLES for SAP 15 SP6, SLES 15 SP6-LTSS, SLE Module for Development Tools 15 SP7 +1 more 2.38-150600.14.61.1
  • glibc SLES for SAP 15 SP5, SLES for SAP 15 SP4, SLES 15 SP5-LTSS +8 more 2.31-150300.109.1

suse advisories SUSE-SU-2026:24281-1SUSE-SU-2026:24326-1SUSE-SU-2026:4656-1SUSE-SU-2026:4591-1

  • glibc openSUSE Tumbleweed 2.44-3.1

opensuse advisories openSUSE-SU-2026:12072-1

Is CVE-2026-97399 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-97399 updated cvss 3.7

glibc: glibc: Denial of Service via out-of-bounds read in strncasecmp

  • Red Hat Enterprise Linux 6 nscd, glibc, glibc-utils, glibc-common, compat-glibc 2.5-46.2, glibc 2.39-128.el10_2
    affected: workaround, no fix planned “To mitigate this implement process-level supervision (such as systemd automatic restarts) to minimize the impact of potential service crashes.”
  • Red Hat Enterprise Linux 7 nscd, glibc, glibc-utils, compat-glibc, glibc-common, compat-glibc 2.5-46.2, +1 more Red Hat Enterprise Linux 8 nscd, glibc, libnsl, nss_db, nss_hesiod, glibc-utils, +8 more Red Hat Enterprise Linux 9 nscd, glibc, libnsl, nss_db, nss_hesiod, glibc-utils, +7 more Red Hat Enterprise Linux 10 glibc 2.39-128.el10_2 Red Hat OpenShift AI (RHOAI) rhoai/odh-core-bff-rhel9, rhoai/odh-dashboard-rhel9, rhoai/odh-mod-arch-maas-rhel9, rhoai/odh-mod-arch-automl-rhel9, rhoai/odh-mod-arch-gen-ai-rhel9, rhoai/odh-mod-arch-mlflow-rhel9, +6 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9
    +1 more products
    Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
    affected: workaround, no fix available “To mitigate this implement process-level supervision (such as systemd automatic restarts) to minimize the impact of potential service crashes.”
  • Red Hat Hardened Images glibc 2.39-128.el10_2 Red Hat OpenShift AI (RHOAI) rhoai/odh-mlflow-rhel9, rhoai/odh-kube-rbac-proxy-rhel9, rhoai/odh-maas-controller-rhel9, rhoai/odh-mlflow-operator-rhel9, rhoai/odh-model-controller-rhel9, rhoai/odh-ogx-k8s-operator-rhel9, +14 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected products

  • The GNU C Library glibc

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.