CVE-2026-72013 json
riscv: Prevent NULL pointer dereference in machine_kexec_prepare()
published 2026-08-15 2 mo ago modified 2026-08-17 2 mo ago also EUVD-2026-59112
- 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 11%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
riscv: Prevent NULL pointer dereference in machine_kexec_prepare()
A NULL pointer dereference issue is noticed in riscv's machine_kexec_prepare(), where image->segment[i].buf might be NULL and copied unchecked.
The NULL buf comes from ima_add_kexec_buffer(), where kbuf is added by kexec_add_buffer(), but kbuf.buffer is NULL, then it is copied without a check in machine_kexec_prepare():
kexec_file_load -> kimage_file_alloc_init() -> kimage_file_prepare_segments() -> ima_add_kexec_buffer() -> kexec_add_buffer() -> machine_kexec_prepare() -> memcpy()
Address this by adding a check before the data copy attempt.
Patch / fix
- Linux Linux 5.15.212, 5.18, 5.19, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5, 7.2
- linux Debian 12 6.1.180-1
- linux Debian 13 6.12.100-1
- linux Debian 14 7.1.5-1
debian advisories DEBIAN-CVE-2026-72013
- linux Ubuntu 22.04 LTS 5.15.0-198.208
- linux Ubuntu 24.04 LTS 6.8.0-147.147
- linux Ubuntu 26.04 LTS 7.0.0-38.38
- linux-aws Ubuntu 22.04 LTS 5.15.0-1117.124
- linux-aws Ubuntu 24.04 LTS 6.8.0-1067.70
- linux-aws Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1118.128
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1071.79
ubuntu advisories UBUNTU-CVE-2026-72013
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
- git.kernel.org/stable/c/606cc45e871e34b80a2f63874f069387a5b44176 commit
- git.kernel.org/stable/c/c462e15497dc40abe369b3be7a2c91ac5d1be6f9 commit
- git.kernel.org/stable/c/b5f92cc4e24a298bf390b0b189a4b888c0900161 commit
- git.kernel.org/stable/c/6ad6954492697681ebcfc1beb0eb384406cd4b65 commit
- git.kernel.org/stable/c/eadd0c2c76aee6a738f17f251434c77db3c606c8 commit
- git.kernel.org/stable/c/d5b2752a17efc165793ae38f2c24b5ed9c04ffde commit
- git.kernel.org/stable/c/81bbcff0c053c4f5c711c31a9b72fc492bd96c3f 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-72013 updated cvss 5.5
kernel: riscv: Prevent NULL pointer dereference in machine_kexec_prepare()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more 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 kernelnot 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
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/606cc45e871e34b80a2f63874f069387a5b44176
- git.kernel.org /stable/c/c462e15497dc40abe369b3be7a2c91ac5d1be6f9
- git.kernel.org /stable/c/b5f92cc4e24a298bf390b0b189a4b888c0900161
- git.kernel.org /stable/c/6ad6954492697681ebcfc1beb0eb384406cd4b65
- git.kernel.org /stable/c/eadd0c2c76aee6a738f17f251434c77db3c606c8
- git.kernel.org /stable/c/d5b2752a17efc165793ae38f2c24b5ed9c04ffde
- git.kernel.org /stable/c/81bbcff0c053c4f5c711c31a9b72fc492bd96c3f
Sources
- CVE List CVE-2026-72013
- NVD CVE-2026-72013
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.