CVE-2022-49423: rtla: Avoid record NULL pointer dereference
In the Linux kernel, the following vulnerability has been resolved:
rtla: Avoid record NULL pointer dereference
Fix the following null/deref_null.cocci errors:
./tools/tracing/rtla/src/osnoise_hist.c:870:31-36: ERROR: record is NULL but dereferenced.
./tools/tracing/rtla/src/osnoise_top.c:650:31-36: ERROR: record is NULL but dereferenced.
./tools/tracing/rtla/src/timerlat_hist.c:905:31-36: ERROR: record is NULL but dereferenced.
./tools/tracing/rtla/src/timerlat_top.c:700:31-36: ERROR: record is NULL but dereferenced.
"record" is NULL before calling osnoise_init_trace_tool.
Add a tag "out_free" to avoid dereferring a NULL pointer.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49423 is a Linux rtla tooling bug where an error path could dereference a NULL pointer. The evidence points to a crash risk in Linux tracing utilities, not remote system compromise. No active exploitation is reported in the provided sources, and no CVSS score is available.
Executive priority
Treat as routine patch management unless rtla is operationally important in production diagnostics. The known impact is availability of a tracing tool, with no evidence of active exploitation or broader compromise in the supplied sources.
Technical view
The fix addresses NULL pointer dereferences in tools/tracing/rtla source files for osnoise and timerlat hist/top paths. The CVE text states record is NULL before osnoise_init_trace_tool and adds an out_free path to avoid dereferencing it. Affected Linux versions include 5.18-era releases per the CVE record.
Likely exposure
Exposure is likely limited to environments using affected Linux kernel source/tooling that includes rtla, especially Linux 5.18 through the fixed stable updates. Systems not using rtla may still carry the code but have lower practical exposure.
Exploitation context
The public record describes static-analysis-found NULL dereference errors. The provided sources do not show remote exploitation, privilege escalation, public exploit code, or CISA KEV listing. Practical impact appears to be local rtla tool failure under specific error handling conditions.
Researcher notes
Evidence is narrow: CVE text and kernel stable commits only. Severity, CWE, and CVSS are not provided. The bug is in Linux tools/tracing/rtla, so validation should distinguish kernel runtime exposure from installed developer or tracing tooling.
Mitigation direction
Update to a Linux kernel or rtla package containing the referenced stable fixes.
Check your Linux distribution advisory for backported fixes.
Prioritize systems where rtla tracing utilities are installed or used.
If updates are unavailable, limit rtla use to trusted administrators.
Validation and detection
Inventory systems for Linux 5.18-era kernels and rtla tooling.
Confirm vendor packages include the referenced stable commits.
Review distribution changelogs for CVE-2022-49423 coverage.
Verify rtla users are limited to authorized administrators.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-49423 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 26, 2025, 02:12 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.