CVE-2026-89575 json
dm raid1: reserve space for NUL-terminator in build_constructor_string()
published 2026-09-11 58 d ago modified 2026-10-19 21 d ago also EUVD-2026-76487
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
dm raid1: reserve space for NUL-terminator in build_constructor_string()
Reserve space for the termination NUL after the maximum 20 decimal digits of a long long value to avoid buffer overflow in sprintf().
Patch / fix
- Linux Linux 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, 6.18.50, 7.2.4, 7.3
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.111-1
- linux Debian 14 7.2.6-1
- linux-6.12 Debian 12 6.12.111-1~deb12u1
debian advisories DEBIAN-CVE-2026-89575
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-gke Ubuntu 22.04 LTS 5.15.0-1115.121
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1113.117
ubuntu advisories UBUNTU-CVE-2026-89575
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.2.6-1.1
opensuse advisories openSUSE-SU-2026:11805-1
- git.kernel.org/stable/c/35ba81c93fe7392c973af9881640180490e76f34 commit
- git.kernel.org/stable/c/1fcc9f9f35653c5ee1a8b144ec96ff3fc48532f7 commit
- git.kernel.org/stable/c/7b035983b895db3ae01d9855963d42541db42125 commit
- git.kernel.org/stable/c/01a0276706c7b6fb758a8e2ff9cf221a3dfcae97 commit
- git.kernel.org/stable/c/0a3657ebd6b517b60cdc5123894047616974e25b commit
- git.kernel.org/stable/c/644140527ae494cedf3b5c0ecd16287deaea7a66 commit
- git.kernel.org/stable/c/f79b53ca3a68a46c6fc3b30b148d1dfb1b33ea8b commit
- git.kernel.org/stable/c/73c37fe54cd056d07461b142ab0b8b81e1ef6ad8 commit
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-89575 updated cvss 5.5
kernel: dm raid1: reserve space for NUL-terminator in build_constructor_string()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: workaround, no fix available “Fix deferred”
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
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/35ba81c93fe7392c973af9881640180490e76f34
- git.kernel.org /stable/c/1fcc9f9f35653c5ee1a8b144ec96ff3fc48532f7
- git.kernel.org /stable/c/7b035983b895db3ae01d9855963d42541db42125
- git.kernel.org /stable/c/01a0276706c7b6fb758a8e2ff9cf221a3dfcae97
- git.kernel.org /stable/c/0a3657ebd6b517b60cdc5123894047616974e25b
- git.kernel.org /stable/c/644140527ae494cedf3b5c0ecd16287deaea7a66
- git.kernel.org /stable/c/f79b53ca3a68a46c6fc3b30b148d1dfb1b33ea8b
- git.kernel.org /stable/c/73c37fe54cd056d07461b142ab0b8b81e1ef6ad8
Sources
- CVE List CVE-2026-89575
- NVD CVE-2026-89575
Fencer Vulns 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.