CVE-2026-89559
CVE CVE-2026-89559EUVD EUVD-2026-76470Published 2026-09-11T19:44:31.000ZLast changed 2026-09-14T12:01:00.000ZCVSS 7.8
What the advisory describes
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().
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.6.157; patch: 6.18.50; patch: 0; 564e871aa66f548a947b23808d3140f326381f0c <037770686126155eafc44501312989e2837b9659; patch: 7.3-rc1; patch: 6.12.109; 4.13; 564e871aa66f548a947b23808d3140f326381f0c <09e649117c54b7e1c004f22eaa19efbadd9ac856; 564e871aa66f548a947b23808d3140f326381f0c <1c391696d2791f82ae462e11da9a0d96f90b240c; 564e871aa66f548a947b23808d3140f326381f0c <e057efcc9c71d90099d9ee00bed0748d0e9fd586; patch: 7.2.4; 564e871aa66f548a947b23808d3140f326381f0c <b4975f2ff6c82adc24ae547f029f82530ba43cfe; patch: 6.1.188; 564e871aa66f548a947b23808d3140f326381f0c <93967bfb17dab66642c57e609c99e1a91fe11278; patch: 5.10.270; 564e871aa66f548a947b23808d3140f326381f0c <69a734359639fca16a0dd73ab17a34943e76c68b; 564e871aa66f548a947b23808d3140f326381f0c <6030597ec683d1e5b46445f888bb5c7776b5a0c4; patch: 5.15.221
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.