nday
CVE-2022-50466

fs/binfmt_elf: Fix memory leak in load_elf_binary()

Linux / Linux

Fecha de divulgación: . nday aún no tiene constancia de una corrección; eso no significa que no exista parche. Ninguna de las cuatro fuentes de PoC la recoge. No figura en el KEV de CISA.

tags weakness typeresource exhaustion accesslocalno user interaction productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

resource exhaustion
CWE-401, stated by NVD's analysts
local
AV:L in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (CVSS 3.1) from NVD's analysts
no user interaction
UI:N in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (CVSS 3.1) from NVD's analysts
Linux kernel
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernel
operating system
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernelthe product type of Linux kernel in nday's product registry
etapa
DIS
divulgación
cvss
sin puntuación aún

Ciclo de vida

Eje x en UTC; punto = minuto exacto, barra ancha = solo fecha, hueco = desconocida o inferida.
fecha desconocida
DISdivulgada
2025-10-01T11:45Z
PATparcheada
sin registro aún
ANAanalizada
sin registro aún
POCPoC
sin registro aún
ITWexplotada
sin registro aún
KEVen KEV
sin registro aún

Descripción

In the Linux kernel, the following vulnerability has been resolved:

fs/binfmt_elf: Fix memory leak in load_elf_binary()

There is a memory leak reported by kmemleak:

unreferenced object 0xffff88817104ef80 (size 224):
  comm "xfs_admin", pid 47165, jiffies 4298708825 (age 1333.476s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    60 a8 b3 00 81 88 ff ff a8 10 5a 00 81 88 ff ff  `.........Z.....
  backtrace:
    [<ffffffff819171e1>] __alloc_file+0x21/0x250
    [<ffffffff81918061>] alloc_empty_file+0x41/0xf0
    [<ffffffff81948cda>] path_openat+0xea/0x3d30
    [<ffffffff8194ec89>] do_filp_open+0x1b9/0x290
    [<ffffffff8192660e>] do_open_execat+0xce/0x5b0
    [<ffffffff81926b17>] open_exec+0x27/0x50
    [<ffffffff81a69250>] load_elf_binary+0x510/0x3ed0
    [<ffffffff81927759>] bprm_execve+0x599/0x1240
    [<ffffffff8192a997>] do_execveat_common.isra.0+0x4c7/0x680
    [<ffffffff8192b078>] __x64_sys_execve+0x88/0xb0
    [<ffffffff83bbf0a5>] do_syscall_64+0x35/0x80

If "interp_elf_ex" fails to allocate memory in load_elf_binary(), the program will take the "out_free_ph" error handing path, resulting in "interpreter" file resource is not released.

Fix it by adding an error handing path "out_free_file", which will release the file resource when "interp_elf_ex" failed to allocate memory.

Original text of the CVE record (cvelist), shown as published.

Registro de eventos

+DISdivulgación

Linux publicó el registro CVE.

fuente cvelist · nday , importación masiva · en bruto
{
  "id": 2214,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2022-50466",
  "occurred_at": "2025-10-01T11:45:37.376Z",
  "observed_at": "2026-11-12T14:10:31.286634Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "ssvc": {
      "timestamp": "2026-11-05T20:11:34.610378Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2025-10-01T11:45:37.376Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Debate de investigadores

0 investigadores lo mencionaron en los últimos 7 días

Publicaciones en X de investigadores de la lista de nday que mencionan este CVE, tal como se publicaron. nday no las verifica.

nday aún no ha recopilado publicaciones en X de investigadores de su lista sobre este CVE.

Discussion

0 comments

No comments yet.