Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 22eeff55679d9e7c0f768c79bfbd83e2f8142d89, 4.19.253, 4d453eb5e1eec89971aa5b3262857ee26cfdffd3.

Low priority for now. Upgrade to Linux Linux 22eeff55679d9e7c0f768c79bfbd83e2f8142d89, 4.19.253, 4d453eb5e1eec89971aa5b3262857ee26cfdffd3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Feb 26, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 19th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-49648

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.19.149 and later · before 4.19.253
  • linux linux kernel5.4.69 and later · before 5.4.207
  • linux linux kernel5.8.13 and later · before 5.10.132
  • linux linux kernel5.11 and later · before 5.15.56
  • linux linux kernel5.16 and later · before 5.18.13
  • linux linux kernel5.19

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • e3a23511638a3dcf0275c1e71a46d1ca2e2e6788, 5.9affected
    • 240dd5118a9e0454f280ffeae63f22bd14735733 and later · before eb622d5580b9e2ff694f62da6410618bd73853cbaffected · git
    • e92c490f104993cea35e5f5d5108ac12df1850ac and later · before ecc6dec12c33aa92c086cd702af9f544ddaf3c75affected · git
    • 46bbe5c671e06f070428b9be142cc4ee5cedebac and later · before 78a1400c42ee11197eb1f0f85ba51df9a4fdfff0affected · git
    • 46bbe5c671e06f070428b9be142cc4ee5cedebac and later · before 22eeff55679d9e7c0f768c79bfbd83e2f8142d89affected · git
    • 46bbe5c671e06f070428b9be142cc4ee5cedebac and later · before 4d453eb5e1eec89971aa5b3262857ee26cfdffd3affected · git
    • 46bbe5c671e06f070428b9be142cc4ee5cedebac and later · before 7edc3945bdce9c39198a10d6129377a5c53559c2affected · git
    • 4.19.149 and later · before 4.19.253affected · semver
    • 5.4.69 and later · before 5.4.207affected · semver
    • 5.8.13 and later · before 5.9affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9kernelbefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-64kbefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-64k-corebefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-64k-debugbefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-64k-develbefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-corebefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-cross-headersbefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-debugbefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-debug-corebefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-debug-develbefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7
AlmaLinux:9kernel-debug-modules-corebefore 5.14.0-611.5.1.el9_75.14.0-611.5.1.el9_7

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-49646Feb 26, 2025 · wifi: mac80211: fix queue selection for mesh/OCB interfaces
    22Monitor
  • ← EarlierCVE-2022-49647Feb 26, 2025 · cgroup: Use separate src/dst nodes when preloading css_sets for migration
    31Monitor
  • Later →CVE-2022-49649Feb 26, 2025 · xen/netback: avoid entering xenvif_rx_next_skb() with an empty rx queue
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux22eeff55679d9e7c0f768c79bfbd83e2f8142d89Vendor (CNA)
Linux Linux4.19.253Vendor (CNA)
Linux Linux4d453eb5e1eec89971aa5b3262857ee26cfdffd3Vendor (CNA)
Linux Linux5.4.207Vendor (CNA)
Linux Linux5.9Vendor (CNA)
Linux Linux78a1400c42ee11197eb1f0f85ba51df9a4fdfff0Vendor (CNA)
Linux Linux7edc3945bdce9c39198a10d6129377a5c53559c2Vendor (CNA)
Linux Linuxeb622d5580b9e2ff694f62da6410618bd73853cbVendor (CNA)
Linux Linuxecc6dec12c33aa92c086cd702af9f544ddaf3c75Vendor (CNA)
almalinux:kernel5.14.0-611.5.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-611.5.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-611.5.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-611.5.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-611.5.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-611.5.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-611.5.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-611.5.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-611.5.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-611.5.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-611.5.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-611.5.1.el9_7 · AlmaLinux:9Package registry (OSV)
debian:linux5.18.14-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+5

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-401 · Missing Release of Memory after Effective Lifetime

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records