Linux Kernel KVM expected behavior violation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.2$0-$5k0.00

Summaryinfo

A vulnerability has been found in Linux Kernel and classified as problematic. Impacted is an unknown function of the component KVM. This manipulation causes expected behavior violation. This vulnerability appears as CVE-2022-3344. The attack may be initiated remotely. There is no available exploit. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in Linux Kernel (Operating System) (the affected version unknown). It has been declared as problematic. Affected by this vulnerability is an unknown part of the component KVM. The manipulation with an unknown input leads to a expected behavior violation vulnerability. The CWE definition for the vulnerability is CWE-440. A feature, API, or function does not perform according to its specification. As an impact it is known to affect availability. The summary by CVE is:

A flaw was found in the KVM's AMD nested virtualization (SVM). A malicious L1 guest could purposely fail to intercept the shutdown of a cooperative nested guest (L2), possibly leading to a page fault and kernel panic in the host (L0).

The weakness was presented 10/25/2022. The advisory is shared at bugzilla.redhat.com. This vulnerability is known as CVE-2022-3344 since 09/27/2022. Neither technical details nor an exploit are publicly available.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at lore.kernel.org.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.2

VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Expected behavior violation
CWE: CWE-440 / CWE-436
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: lore.kernel.org

Timelineinfo

09/27/2022 🔍
10/25/2022 +28 days 🔍
10/25/2022 +0 days 🔍
05/07/2025 +925 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: bugzilla.redhat.com
Status: Confirmed

CVE: CVE-2022-3344 (🔍)
GCVE (CVE): GCVE-0-2022-3344
GCVE (VulDB): GCVE-100-212173

Entryinfo

Created: 10/25/2022 22:10
Updated: 05/07/2025 22:24
Changes: 10/25/2022 22:10 (40), 05/07/2025 22:24 (26)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!