Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2022-49648— tracing/histograms: Fix memory leak problem

EPSS 0.01% · P1
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2022-49648

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
tracing/histograms: Fix memory leak problem
Source: NVD (National Vulnerability Database)
Vulnerability Description
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
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于tracing/histograms中的内存泄漏。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 240dd5118a9e0454f280ffeae63f22bd14735733 ~ eb622d5580b9e2ff694f62da6410618bd73853cb -
LinuxLinux 5.9 -

II. Public POCs for CVE-2022-49648

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2022-49648

登录查看更多情报信息。

Same Patch Batch · Linux · 2025-02-26 · 706 CVEs total

CVE-2022-49496media: mediatek: vcodec: prevent kernel crash when rmmod mtk-vcodec-dec.ko
CVE-2022-49487mtd: rawnand: intel: fix possible null-ptr-deref in ebu_nand_probe()
CVE-2022-49486ASoC: fsl: Fix refcount leak in imx_sgtl5000_probe
CVE-2022-49488drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock is detected
CVE-2022-49489drm/msm/disp/dpu1: set vbif hw config to NULL to avoid use after memory free during pm run
CVE-2022-49490drm/msm/mdp5: Return error code in mdp5_pipe_release when deadlock is detected
CVE-2022-49491drm/rockchip: vop: fix possible null-ptr-deref in vop_bind()
CVE-2022-49492nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags
CVE-2022-49493ASoC: rt5645: Fix errorenous cleanup order
CVE-2022-49494mtd: rawnand: cadence: fix possible null-ptr-deref in cadence_nand_dt_probe()
CVE-2022-49495drm/msm/hdmi: check return value after calling platform_get_resource_byname()
CVE-2022-49497net: remove two BUG() from skb_checksum_help()
CVE-2022-49503ath9k_htc: fix potential out of bounds access with invalid rxstatus->rs_keyix
CVE-2022-49508HID: elan: Fix potential double free in elan_input_configured
CVE-2022-49506drm/mediatek: Add vblank register/unregister callback functions
CVE-2022-49504scsi: lpfc: Inhibit aborts if external loopback plug is inserted
CVE-2022-49505NFC: NULL out the dev->rfkill to prevent UAF
CVE-2022-49502media: rga: fix possible memory leak in rga_probe
CVE-2022-49499drm/msm: Fix null pointer dereferences without iommu
CVE-2022-49498ALSA: pcm: Check for null pointer of pointer substream before dereferencing it

Showing top 20 of 706 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2022-49648

No comments yet


Leave a comment