CVE-20XX-?
agent?

CVE-2022-26356

5.6 MEDIUM 0.2% exploit odds Fix listed

What it is

Racy interactions between dirty vram tracking and paging log dirty hypercalls Activation of log dirty mode done by XEN_DMOP_track_dirty_vram (was named HVMOP_track_dirty_vram before Xen 4.9) is racy with ongoing log dirty hypercalls. A suitably timed call to XEN_DMOP_track_dirty_vram can enable log dirty while another CPU is still in the process of tearing down the structures related to a previously enabled log dirty mode (XEN_DOMCTL_SHADOW_OP_OFF). This is due to lack of mutually exclusive locking between both operations and can lead to entries being added in already freed slots, resulting in a memory leak.

At a glance

Exploitability
Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
Exploit odds
0.2% chance of exploitation in the next 30 days (EPSS).
Fix
A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

  1. PublishedDisclosed publicly on CVE.org and NVD
  2. Last updatedMost recent change to the record

Why it ranks here

Details

Published
Last modified
Exploit probability
0.2% · EPSS, next 30 days
Weakness
CWE-667
Record status
Modified

Affected

Attack profile CVSS 3.1 · 5.6

Attack vector
Local
Complexity
High
Privileges needed
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High
Raw vector

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

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2022-26356.md and follow it. Check whether this project is affected by CVE-2022-26356. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Meme: I wake up, CVE-2022-26356
Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record