VDB

CVE-2022-49648

CVE-2022-49648 PUBLISHED CVSS 5.5 MEDIUM

tracing/histograms: Fix memory leak problem

Reported by linux · Published February 26, 2025

In the Linux kernel, the following vulnerability has been resolved: tracing/histograms: Fix memory leak problem This reverts commit 46bbe5c671e06f070428b9be142cc4ee5cedebac. As commit 46bbe5c671e0 ("tracing: fix double free") said, the "double free" problem reported by clang static analyzer is: > In parse_var_defs() if there is a problem allocating > var_defs.expr, the earlier var_defs.name is freed. > This free is duplicated by free_var_defs() which frees > the rest of the list. However, if there is a problem allocating N-th var_defs.expr: + in parse_var_defs(), the freed 'earlier var_defs.name' is actually the N-th var_defs.name; + then in free_var_defs(), the names from 0th to (N-1)-th are freed; IF ALLOCATING PROBLEM HAPPENED HERE!!! -+ \ | 0th 1th (N-1)-th N-th V +-------------+-------------+-----+-------------+----------- var_defs: | name | expr | name | expr | ... | name | expr | name | /// +-------------+-------------+-----+-------------+----------- These two frees don't act on same name, so there was no "double free" problem before. Conversely, after that commit, we get a "memory leak" problem because the above "N-th var_defs.name" is not freed. If enable CONFIG_DEBUG_KMEMLEAK and inject a fault at where the N-th var_defs.expr allocated, then execute on shell like: $ echo 'hist:key=call_site:val=$v1,$v2:v1=bytes_req,v2=bytes_alloc' > \ /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger Then kmemleak reports: unreferenced object 0xffff8fb100ef3518 (size 8): comm "bash", pid 196, jiffies 4295681690 (age 28.538s) hex dump (first 8 bytes): 76 31 00 00 b1 8f ff ff v1...... backtrace: [<0000000038fe4895>] kstrdup+0x2d/0x60 [<00000000c99c049a>] event_hist_trigger_parse+0x206f/0x20e0 [<00000000ae70d2cc>] trigger_process_regex+0xc0/0x110 [<0000000066737a4c>] event_trigger_write+0x75/0xd0 [<000000007341e40c>] vfs_write+0xbb/0x2a0 [<0000000087fde4c2>] ksys_write+0x59/0xd0 [<00000000581e9cdf>] do_syscall_64+0x3a/0x80 [<00000000cf3b065c>] entry_SYSCALL_64_after_hwframe+0x46/0xb0

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
linux_kernellinux5.18.13, 5.15.56, 5.10.132, 5.4.207, 4.19.253
LinuxLinuxecc6dec12c33aa92c086cd702af9f544ddaf3c75, eb622d5580b9e2ff694f62da6410618bd73853cb, 7edc3945bdce9c39198a10d6129377a5c53559c2, 78a1400c42ee11197eb1f0f85ba51df9a4fdfff0, 5.9, 5.4.207, 4d453eb5e1eec89971aa5b3262857ee26cfdffd3, 4.19.253, 22eeff55679d9e7c0f768c79bfbd83e2f8142d89

Risk scores

CVSS 3.1
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

VendorProductVersions
LinuxLinux240dd5118a9e0454f280ffeae63f22bd14735733, e92c490f104993cea35e5f5d5108ac12df1850ac, 46bbe5c671e06f070428b9be142cc4ee5cedebac
LinuxLinux5.9, 0, 4.19.253
LinuxLinux5.8.13, 5.10.132, 5.15.56
linuxlinux_kernel5.4.69, 5.9, 5.9

Timeline

  • Feb 26, 2025 CVE Published
  • Feb 27, 2025 EPSS Score (30 in total, the first dated here)
  • May 23, 2026 Coalition ESS Score
  • Jun 2, 2026 Security Advisory (3 in total, the first dated here)
  • Aug 12, 2026 Distribution Patch (2 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2022-49648
vulnetix vdb fixes CVE-2022-49648

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2022-49648/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›