libnvdimm/labels: Prevent integer overflow in __nd_label_validate()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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().
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 564e871aa66f548a947b23808d3140f326381f0c · fixed in b4975f2ff6c82adc24ae547f029f82530ba43cfe; From 564e871aa66f548a947b23808d3140f326381f0c · fixed in 6030597ec683d1e5b46445f888bb5c7776b5a0c4; From 564e871aa66f548a947b23808d3140f326381f0c · fixed in 1c391696d2791f82ae462e11da9a0d96f90b240c; From 564e871aa66f548a947b23808d3140f326381f0c · fixed in 93967bfb17dab66642c57e609c99e1a91fe11278; From 564e871aa66f548a947b23808d3140f326381f0c · fixed in e057efcc9c71d90099d9ee00bed0748d0e9fd586; From 564e871aa66f548a947b23808d3140f326381f0c · fixed in 09e649117c54b7e1c004f22eaa19efbadd9ac856; From 564e871aa66f548a947b23808d3140f326381f0c · fixed in 69a734359639fca16a0dd73ab17a34943e76c68b; From 564e871aa66f548a947b23808d3140f326381f0c · fixed in 037770686126155eafc44501312989e2837b9659
- Linux Linux
4.13
- KernelLinux
From 4.13.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4
References 8
git.kernel.org
- stable/c/b4975f2ff6c82adc24ae547f029f82530ba43cfe
- stable/c/6030597ec683d1e5b46445f888bb5c7776b5a0c4
- stable/c/1c391696d2791f82ae462e11da9a0d96f90b240c
- stable/c/93967bfb17dab66642c57e609c99e1a91fe11278
- stable/c/e057efcc9c71d90099d9ee00bed0748d0e9fd586
- stable/c/09e649117c54b7e1c004f22eaa19efbadd9ac856
- stable/c/69a734359639fca16a0dd73ab17a34943e76c68b
- stable/c/037770686126155eafc44501312989e2837b9659