LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50631: RISC-V: kexec: Fix memory leak of fdt buffer

In the Linux kernel, the following vulnerability has been resolved: RISC-V: kexec: Fix memory leak of fdt buffer This is reported by kmemleak detector: unreferenced object 0xff60000082864000 (size 9588): comm "kexec", pid 146, jiffies 4294900634 (age 64.788s) hex dump (first 32 bytes): d0 0d fe ed 00 00 12 ed 00 00 00 48 00 00 11 40 ...........H...@ 00 00 00 28 00 00 00 11 00 00 00 02 00 00 00 00 ...(............ backtrace: [<00000000f95b17c4>] kmemleak_alloc+0x34/0x3e [<00000000b9ec8e3e>] kmalloc_order+0x9c/0xc4 [<00000000a95cf02e>] kmalloc_order_trace+0x34/0xb6 [<00000000f01e68b4>] __kmalloc+0x5c2/0x62a [<000000002bd497b2>] kvmalloc_node+0x66/0xd6 [<00000000906542fa>] of_kexec_alloc_and_setup_fdt+0xa6/0x6ea [<00000000e1166bde>] elf_kexec_load+0x206/0x4ec [<0000000036548e09>] kexec_image_load_default+0x40/0x4c [<0000000079fbe1b4>] sys_kexec_file_load+0x1c4/0x322 [<0000000040c62c03>] ret_from_syscall+0x0/0x2 In elf_kexec_load(), a buffer is allocated via kvmalloc() to store fdt. While it's not freed back to system when kexec kernel is reloaded or unloaded. Then memory leak is caused. Fix it by introducing riscv specific function arch_kimage_file_post_load_cleanup(), and freeing the buffer there.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel memory leak in the RISC-V kexec path. When a replacement kernel is loaded, reloaded, or unloaded, a device-tree buffer may not be freed. The sources do not report remote attack, data theft, or active exploitation. Business urgency depends on whether you run RISC-V Linux systems using kexec.

Executive priority

Treat as a targeted kernel maintenance item, not an emergency internet-facing threat based on current sources. Prioritize if your organization operates RISC-V Linux platforms or depends on kexec-based reboot, crash, or upgrade processes.

Technical view

In RISC-V Linux, elf_kexec_load() allocates an FDT buffer via kvmalloc() through of_kexec_alloc_and_setup_fdt(). The buffer was not released during kexec reload or unload. The kernel fix adds a RISC-V arch_kimage_file_post_load_cleanup() path to free the buffer.

Likely exposure

Exposure appears limited to Linux on RISC-V systems where kexec file loading is used. The CVE record lists Linux kernel versions including 5.19, 6.0.18, 6.1.4, and 6.2 as affected, but distribution backport status must be verified with vendor advisories.

Exploitation context

No source in the bundle reports active exploitation, public weaponization, or KEV listing. The described impact is memory leakage during kexec kernel load, reload, or unload operations. Practical impact is most relevant where those operations occur repeatedly or are part of operational workflows.

Researcher notes

The record is narrow and source evidence is concise. It identifies a kmemleak-reported FDT buffer leak and three upstream stable commit references. No CVSS, CWE, exploitability assessment, or downstream distro status is provided in the bundle.

Mitigation direction

  • Check your Linux vendor advisory for CVE-2022-50631 package status.
  • Apply kernel updates containing the referenced upstream stable fixes.
  • Prioritize RISC-V systems that use kexec for boot, crash, or upgrade workflows.
  • If unpatched, reduce unnecessary repeated kexec load/reload/unload operations where operationally feasible.

Validation and detection

  • Inventory RISC-V Linux hosts and running kernel versions.
  • Determine whether kexec file loading is enabled or operationally used.
  • Compare installed kernel changelogs against the referenced stable commits.
  • Review kernel memory-leak diagnostics after approved kexec workflows.
  • Confirm distribution packages include the RISC-V FDT cleanup fix.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50631 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6261586e0c91db14c34f894f4bc48f2300cff1d4, 6261586e0c91db14c34f894f4bc48f2300cff1d4, 6261586e0c91db14c34f894f4bc48f2300cff1d4unaffected
LinuxLinux5.19, 0, 6.0.18, 6.1.4, 6.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.