CVE-2022-49796

System crash via stale kprobe trace_array pointer

Published May 1, 2025 · Updated May 11, 2026

Null-pointer dereference in the Linux kernel allows local users to crash the system during kprobe test-module cleanup. If test_gen_kprobe_cmd() fails after kprobe_event_gen_cmd_end(), the delete path frees the resource while gen_kretprobe_test.trace_array retains a stale pointer. Reaching the fault requires low-privileged local access and the affected kprobe event-generator test path; the demonstrated consequence is a kernel oops and service interruption.

CVSS severity5.5
Medium
EPSS probability0.19%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Null-pointer dereference in the Linux kernel allows local users to crash the system during kprobe test-module cleanup. If test_gen_kprobe_cmd() fails after kprobe_event_gen_cmd_end(), the delete path frees the resource while gen_kretprobe_test.trace_array retains a stale pointer. Reaching the fault requires low-privileged local access and the affected kprobe event-generator test path; the demonstrated consequence is a kernel oops and service interruption.

The record

CVE
CVE-2022-49796
Published
May 1, 2025
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 1, 2025CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.6
  2. Affected versionversion=64836248dda20c8e7427b493f7e06d9bf8f58850 <22ea4ca9631eb137e64e5ab899e9c89cb6670959
  3. Affected versionversion=64836248dda20c8e7427b493f7e06d9bf8f58850 <28a54854a95923b6266a9479ad660ca2cc0e1d5f
  4. Affected versionversion=64836248dda20c8e7427b493f7e06d9bf8f58850 <510c12f93674ea0a1423b24f36c67357168a262a
  5. Affected versionversion=64836248dda20c8e7427b493f7e06d9bf8f58850 <e57daa750369fedbf678346aec724a43b9a51749

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=5.6; version=64836248dda20c8e7427b493f7e06d9bf8f58850 <22ea4ca9631eb137e64e5ab899e9c89cb6670959; version=64836248dda20c8e7427b493f7e06d9bf8f58850 <28a54854a95923b6266a9479ad660ca2cc0e1d5f; version=64836248dda20c8e7427b493f7e06d9bf8f58850 <510c12f93674ea0a1423b24f36c67357168a262a; version=64836248dda20c8e7427b493f7e06d9bf8f58850 <e57daa750369fedbf678346aec724a43b9a51749

Published CVSS scores

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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo