CVE-2026-59048
UnknownSummary
In rb_cpu_init of trace.c, there is a possible out-of-bounds read due to an incorrect bounds check. This could lead to local information disclosure with no additional execution privileges needed; user interaction is not required.
Risk Assessment
Could allow a local attacker to read sensitive data from process memory.
Recommendation
Apply the available system update containing the fix for this issue.
Other vulnerabilities in trace.c
See all- CVE-2026-59047Unknown
In multiple locations, there is a possible denial of service due to a logic error in the code. This could lead to local denial of service with no additional execution privileges needed; user interaction is not required.
- CVE-2026-59045Unknown
In multiple locations, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed; user interaction is not required.
- CVE-2026-59044High
In multiple locations, there is a possible use-after-free due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed; user interaction is not required.
- CVE-2026-58824Unknown
In __pkvm_load_tracing of trace.c, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed.
Original NVD description (English source)
In rb_cpu_init of trace.c, there is a possible out-of-bounds read due to an incorrect bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS