Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49006: tracing: Free buffers when a used dynamic event is removed

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/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.25% (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 1603feac154ff38514e8354e3079a455eb4801e2, 417d5ea6e735e5d88ffb6c436cf2938f3f476dd1, 4313e5a613049dfc1819a6dfb5f94cf2caff9452.

Low priority for now. Upgrade to Linux Linux 1603feac154ff38514e8354e3079a455eb4801e2, 417d5ea6e735e5d88ffb6c436cf2938f3f476dd1, 4313e5a613049dfc1819a6dfb5f94cf2caff9452 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: Free buffers when a used dynamic event is removed After 65536 dynamic events have been added and removed, the "type" field of the event then uses the first type number that is available (not currently used by other events). A type number is the identifier of the binary blobs in the tracing ring buffer (known as events) to map them to logic that can parse the binary blob. The issue is that if a dynamic event (like a kprobe event) is traced and is in the ring buffer, and then that event is removed (because it is dynamic, which means it can be created and destroyed), if another dynamic event is created that has the same number that new event's logic on parsing the binary blob will be used. To show how this can be an issue, the following can crash the kernel: # cd /sys/kernel/tracing # for i in `seq 65536`; do echo 'p:kprobes/foo do_sys_openat2 $arg1:u32' > kprobe_events # done For every iteration of the above, the writing to the kprobe_events will remove the old event and create a new one (with the same format) and increase the type number to the next available on until the type number reaches over 65535 which is the max number for the 16 bit type. After it reaches that number, the logic to allocate a new number simply looks for the next available number. When an dynamic event is removed, that number is then available to be reused by the next dynamic event created. That is, once the above reaches the max number, the number assigned to the event in that loop will remain the same. Now that means deleting one dynamic event and created another will reuse the previous events type number. This is where bad things can happen. After the above loop finishes, the kprobes/foo event which reads the do_sys_openat2 function call's first parameter as an integer. # echo 1 > kprobes/foo/enable # cat /etc/passwd > /dev/null # cat trace cat-2211 [005] .... 2007.849603: foo: (do_sys_openat2+0x0/0x130) arg1=4294967196 cat-2211 [005] .... 2007.849620: foo: (do_sys_openat2+0x0/0x130) arg1=4294967196 cat-2211 [005] .... 2007.849838: foo: (do_sys_openat2+0x0/0x130) arg1=4294967196 cat-2211 [005] .... 2007.849880: foo: (do_sys_openat2+0x0/0x130) arg1=4294967196 # echo 0 > kprobes/foo/enable Now if we delete the kprobe and create a new one that reads a string: # echo 'p:kprobes/foo do_sys_openat2 +0($arg2):string' > kprobe_events And now we can the trace: # cat trace sendmail-1942 [002] ..... 530.136320: foo: (do_sys_openat2+0x0/0x240) arg1= cat-2046 [004] ..... 530.930817: foo: (do_sys_openat2+0x0/0x240) arg1="������������������������������������������������������������������������������������������������" cat-2046 [004] ..... 530.930961: foo: (do_sys_openat2+0x0/0x240) arg1="������������������������������������������������������������������������������������������������" cat-2046 [004] ..... 530.934278: foo: (do_sys_openat2+0x0/0x240) arg1="������������������������������������������������������������������������������������������������" cat-2046 [004] ..... 530.934563: foo: (do_sys_openat2+0x0/0x240) arg1="��������������������������������������� ---truncated---

Published
Oct 21, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 17th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 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-49006

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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

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

    • 2.6.33affected
    • 77b44d1b7c28360910cdbd427fb62d485c08674c and later · before 1603feac154ff38514e8354e3079a455eb4801e2affected · git
    • 77b44d1b7c28360910cdbd427fb62d485c08674c and later · before be111ebd8868d4b7c041cb3c6102e1ae27d6dc1daffected · git
    • 77b44d1b7c28360910cdbd427fb62d485c08674c and later · before 417d5ea6e735e5d88ffb6c436cf2938f3f476dd1affected · git
    • 77b44d1b7c28360910cdbd427fb62d485c08674c and later · before c52d0c8c4f38f7580cff61c4dfe1034c580cedfdaffected · git
    • 77b44d1b7c28360910cdbd427fb62d485c08674c and later · before 4313e5a613049dfc1819a6dfb5f94cf2caff9452affected · git
    • before 2.6.33not affected · semver
    • 5.4.226 and later · up to and including 5.4.*not affected · semver
    • 5.10.158 and later · up to and including 5.10.*not affected · semver
    • 5.15.82 and later · up to and including 5.15.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.0.12-16.0.12-1
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-develbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-64k-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-64k-develbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debug-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debug-develbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-develbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-devel-matchedbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-docbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-rt-64k-debug-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-rt-64k-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-rt-debug-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-rt-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-tools-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6

+84

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-49004Oct 21, 2024 · riscv: Sync efi page table's kernel mappings before switching
    22Monitor
  • ← EarlierCVE-2022-49005Oct 21, 2024 · ASoC: ops: Fix bounds check for _sx controls
    22Monitor
  • Later →CVE-2022-49007Oct 21, 2024 · nilfs2: fix NULL pointer dereference in nilfs_palloc_commit_free_entry()
    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 Linux1603feac154ff38514e8354e3079a455eb4801e2Vendor (CNA)
Linux Linux417d5ea6e735e5d88ffb6c436cf2938f3f476dd1Vendor (CNA)
Linux Linux4313e5a613049dfc1819a6dfb5f94cf2caff9452Vendor (CNA)
Linux Linuxbe111ebd8868d4b7c041cb3c6102e1ae27d6dc1dVendor (CNA)
Linux Linuxc52d0c8c4f38f7580cff61c4dfe1034c580cedfdVendor (CNA)
debian:linux6.0.12-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
suse:kernel-64kb5.3.18-150300.59.185.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-default5.3.18-150300.59.185.1 · SUSE:Linux Enterprise Live Patching 15 SP3Package registry (OSV)
suse:kernel-default-base5.3.18-150300.59.185.1.150300.18.109.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-docs5.3.18-150300.59.185.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP3_Update_511-150300.7.3.1 · SUSE:Linux Enterprise Live Patching 15 SP3Package registry (OSV)
suse:kernel-obs-build5.3.18-150300.59.185.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-preempt5.3.18-150300.59.185.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-rt5.3.18-150300.194.1 · SUSE:Linux Enterprise Micro 5.1Package registry (OSV)
suse:kernel-source5.3.18-150300.59.185.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-source-rt5.3.18-150300.194.1 · SUSE:Linux Enterprise Micro 5.1Package registry (OSV)
suse:kernel-syms5.3.18-150300.59.185.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-zfcpdump5.3.18-150300.59.185.1 · SUSE:Linux Enterprise Server 15 SP3-LTSSPackage registry (OSV)

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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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.

References

All records