Skip to content
Noroxi
CVE-2022-49779· NVD / CVE Program· CNA Linux

kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case

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.22% (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 55788ebbe8b365b4375bd56b4ba7db79d393a370, 5dd7caf0bdc5d0bae7cf9776b4d739fb09bd5ebb, 7b0007b28dd970176f2e297c06ae63eea2447127.

Low priority for now. Upgrade to Linux Linux 55788ebbe8b365b4375bd56b4ba7db79d393a370, 5dd7caf0bdc5d0bae7cf9776b4d739fb09bd5ebb, 7b0007b28dd970176f2e297c06ae63eea2447127 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: kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case In __unregister_kprobe_top(), if the currently unregistered probe has post_handler but other child probes of the aggrprobe do not have post_handler, the post_handler of the aggrprobe is cleared. If this is a ftrace-based probe, there is a problem. In later calls to disarm_kprobe(), we will use kprobe_ftrace_ops because post_handler is NULL. But we're armed with kprobe_ipmodify_ops. This triggers a WARN in __disarm_kprobe_ftrace() and may even cause use-after-free: Failed to disarm kprobe-ftrace at kernel_clone+0x0/0x3c0 (error -2) WARNING: CPU: 5 PID: 137 at kernel/kprobes.c:1135 __disarm_kprobe_ftrace.isra.21+0xcf/0xe0 Modules linked in: testKprobe_007(-) CPU: 5 PID: 137 Comm: rmmod Not tainted 6.1.0-rc4-dirty #18 [...] Call Trace: <TASK> __disable_kprobe+0xcd/0xe0 __unregister_kprobe_top+0x12/0x150 ? mutex_lock+0xe/0x30 unregister_kprobes.part.23+0x31/0xa0 unregister_kprobe+0x32/0x40 __x64_sys_delete_module+0x15e/0x260 ? do_user_addr_fault+0x2cd/0x6b0 do_syscall_64+0x3a/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd [...] For the kprobe-on-ftrace case, we keep the post_handler setting to identify this aggrprobe armed with kprobe_ipmodify_ops. This way we can disarm it correctly.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
May 1, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 11th 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%

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-49779

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.

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 kernel5.4 and later · before 5.4.225
  • linux linux kernel5.5 and later · before 5.10.156
  • linux linux kernel5.11 and later · before 5.15.80
  • linux linux kernel5.16 and later · before 6.0.10
  • linux linux kernel6.1

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

    • 5.4affected
    • 0bc11ed5ab60c135aa764a62c02cd5ea68289de4 and later · before 7b0007b28dd970176f2e297c06ae63eea2447127affected · git
    • 0bc11ed5ab60c135aa764a62c02cd5ea68289de4 and later · before 7d606ae1abcc3eab5408e42444d789dc7def51b8affected · git
    • 0bc11ed5ab60c135aa764a62c02cd5ea68289de4 and later · before c49cc2c059b503e962c2f13a806c105f9b757df4affected · git
    • 0bc11ed5ab60c135aa764a62c02cd5ea68289de4 and later · before 55788ebbe8b365b4375bd56b4ba7db79d393a370affected · git
    • 0bc11ed5ab60c135aa764a62c02cd5ea68289de4 and later · before 5dd7caf0bdc5d0bae7cf9776b4d739fb09bd5ebbaffected · git
    • before 5.4not affected · semver
    • 5.4.225 and later · up to and including 5.4.*not affected · semver
    • 5.10.156 and later · up to and including 5.10.*not affected · semver
    • 5.15.80 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.10-16.0.10-1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-64kbbefore 5.14.21-150400.24.167.15.14.21-150400.24.167.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-docsbefore 5.14.21-150400.24.167.15.14.21-150400.24.167.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-obs-buildbefore 5.14.21-150400.24.167.15.14.21-150400.24.167.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-sourcebefore 5.14.21-150400.24.167.15.14.21-150400.24.167.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-symsbefore 5.14.21-150400.24.167.15.14.21-150400.24.167.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-64kbbefore 5.14.21-150500.55.110.15.14.21-150500.55.110.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-docsbefore 5.14.21-150500.55.110.15.14.21-150500.55.110.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-obs-buildbefore 5.14.21-150500.55.110.15.14.21-150500.55.110.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-symsbefore 5.14.21-150500.55.110.15.14.21-150500.55.110.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_41before 1-150400.9.3.11-150400.9.3.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_27before 1-150500.11.7.11-150500.11.7.1
SUSE:Linux Enterprise Micro 5.3kernel-defaultbefore 5.14.21-150400.24.167.15.14.21-150400.24.167.1
SUSE:Linux Enterprise Micro 5.3kernel-default-basebefore 5.14.21-150400.24.167.1.150400.24.84.15.14.21-150400.24.167.1.150400.24.84.1
SUSE:Linux Enterprise Micro 5.3kernel-rtbefore 5.14.21-150400.15.121.15.14.21-150400.15.121.1
SUSE:Linux Enterprise Micro 5.3kernel-source-rtbefore 5.14.21-150400.15.121.15.14.21-150400.15.121.1
SUSE:Linux Enterprise Micro 5.5kernel-defaultbefore 5.14.21-150500.55.110.15.14.21-150500.55.110.1
SUSE:Linux Enterprise Micro 5.5kernel-default-basebefore 5.14.21-150500.55.110.1.150500.6.51.35.14.21-150500.55.110.1.150500.6.51.3
SUSE:Linux Enterprise Micro 5.5kernel-rtbefore 5.14.21-150500.13.97.15.14.21-150500.13.97.1
SUSE:Linux Enterprise Micro 5.5kernel-sourcebefore 5.14.21-150500.55.110.15.14.21-150500.55.110.1
SUSE:Linux Enterprise Micro 5.5kernel-source-rtbefore 5.14.21-150500.13.97.15.14.21-150500.13.97.1
SUSE:Linux Enterprise Server 15 SP4-LTSSkernel-zfcpdumpbefore 5.14.21-150400.24.167.15.14.21-150400.24.167.1
SUSE:Linux Enterprise Server 15 SP5-LTSSkernel-zfcpdumpbefore 5.14.21-150500.55.110.15.14.21-150500.55.110.1

Other highest-scoring records for the same primary product.

  • 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
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-49777May 1, 2025 · Input: i8042 - fix leaking of platform device on module removal
    22Monitor
  • ← EarlierCVE-2022-49778May 1, 2025 · arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud
    22Monitor
  • Later →CVE-2022-49780May 1, 2025 · scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus()
    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 Linux55788ebbe8b365b4375bd56b4ba7db79d393a370Vendor (CNA)
Linux Linux5dd7caf0bdc5d0bae7cf9776b4d739fb09bd5ebbVendor (CNA)
Linux Linux7b0007b28dd970176f2e297c06ae63eea2447127Vendor (CNA)
Linux Linux7d606ae1abcc3eab5408e42444d789dc7def51b8Vendor (CNA)
Linux Linuxc49cc2c059b503e962c2f13a806c105f9b757df4Vendor (CNA)
debian:linux6.0.10-1 · Debian:12Package registry (OSV)
suse:kernel-64kb5.14.21-150500.55.110.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSPackage registry (OSV)
suse:kernel-default5.14.21-150500.55.110.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-default-base5.14.21-150500.55.110.1.150500.6.51.3 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-docs5.14.21-150500.55.110.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP4_Update_411-150400.9.3.1 · SUSE:Linux Enterprise Live Patching 15 SP4Package registry (OSV)
suse:kernel-livepatch-SLE15-SP5_Update_271-150500.11.7.1 · SUSE:Linux Enterprise Live Patching 15 SP5Package registry (OSV)
suse:kernel-obs-build5.14.21-150500.55.110.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSPackage registry (OSV)
suse:kernel-rt5.14.21-150400.15.121.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-source5.14.21-150500.55.110.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-source-rt5.14.21-150400.15.121.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-syms5.14.21-150500.55.110.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSPackage registry (OSV)
suse:kernel-zfcpdump5.14.21-150500.55.110.1 · SUSE:Linux Enterprise Server 15 SP5-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.

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.

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
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.

Change log

  1. Fix✗ → ✓

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

References

All records