CVE-2026-89559

libnvdimm/labels: Prevent integer overflow in __nd_label_validate()

HIGH
7.8
CVSS Score
Published: September 11, 2026 at 07:44 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

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

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: libnvdimm/labels: Prevent integer overflow in __nd_label_validate() The on-media namespace index field nslot is a u32 read from the DIMM label storage area. __nd_label_validate() bounds it against the config area size, but sizeof_namespace_label() returns unsigned, so the product nslot * label_size is evaluated in 32-bit and wraps modulo 2^32 before the comparison. A crafted nslot passes the bound and is then used as the loop trip count in nd_label_data_init(), whose memset() walks off the end of the config_size buffer: an out-of-bounds write. The field is not trusted -- it comes from the medium, or from userspace via ND_CMD_SET_CONFIG_DATA. Evaluate the product in 64-bit so the bound check is exact; conforming labels are unaffected. The check was safe when introduced by commit 4a826c83db4e ("libnvdimm: namespace indices: read and validate"): it multiplied by sizeof(struct nd_namespace_label), a size_t, so on a 64-bit build the product did not wrap. Commit 564e871aa66f ("libnvdimm, label: add v1.2 nvdimm label definitions") narrowed it to 32 bits when the label size became a runtime value read via sizeof_namespace_label().

Affected

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

4.13564e871aa66f548a947b23808d3140f326381f0c
Vendor states this is fixed in 037770686126155eafc44501312989e2837b9659 (fixed)
Vendor states this is fixed in 09e649117c54b7e1c004f22eaa19efbadd9ac856 (fixed)
Vendor states this is fixed in 1c391696d2791f82ae462e11da9a0d96f90b240c (fixed)
Vendor states this is fixed in 6030597ec683d1e5b46445f888bb5c7776b5a0c4 (fixed)
Vendor states this is fixed in 69a734359639fca16a0dd73ab17a34943e76c68b (fixed)
Vendor states this is fixed in 93967bfb17dab66642c57e609c99e1a91fe11278 (fixed)
Vendor states this is fixed in b4975f2ff6c82adc24ae547f029f82530ba43cfe (fixed)
Vendor states this is fixed in e057efcc9c71d90099d9ee00bed0748d0e9fd586 (fixed)
Vendor states this is fixed in 4.13 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

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

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

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