CVE-2022-49098 | Drivers: hv: vmbus: Fix potential crash on module unload

In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: vmbus: Fix potential crash on module unload The vmbus driver relies on the panic notifier infrastructure to perform some operations when a panic event is detected. Since vmbus can be built as module, it is required that the driver handles both registering and unregistering such panic notifier callback. After commit 74347a99e73a ("x86/Hyper-V: Unload vmbus channel in hv panic callback") though, the panic notifier registration is done unconditionally in the module initialization routine whereas the unregistering procedure is conditionally guarded and executes only if HV_FEATURE_GUEST_CRASH_MSR_AVAILABLE capability is set. This patch fixes that by unconditionally unregistering the panic notifier in the module's exit routine as well.

Published: 2025-02-26 Last update: 2025-10-14 Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Conclusion & alert: CVE-2022-49098 is rated Low Risk (22.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-49098

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-06 0.05% 0.01% -0.04%
2 2025-12-23 0.04% 0.05% +0.01%
3 2025-11-21 0.04%

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-49098

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8 3.6 [email protected]

Weakness enumeration for CVE-2022-49098

OS Trackers for CVE-2022-49098

vendor priority summary link
debian not yet assigned CVE-2022-49098 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-49098
redhat low https://access.redhat.com/security/cve/CVE-2022-49098
suse medium https://www.suse.com/security/cve/CVE-2022-49098/
ubuntu medium CVE-2022-49098 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, ignored 147, released 129, not-affected 127, needed 3. https://ubuntu.com/security/CVE-2022-49098

Affected software / configurations for CVE-2022-49098

Vendor Product Version Raw CPE
linux linux_kernel >= 4.19.118, < 4.19.238 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.4.35, < 5.4.189 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.6.7, < 5.7 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.7.1, < 5.10.111 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.11, < 5.15.34 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.16, < 5.16.20 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.17, < 5.17.3 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel 5.7 cpe:2.3:o:linux:linux_kernel:5.7:-:*:*:*:*:*:*
linux linux_kernel 5.7 cpe:2.3:o:linux:linux_kernel:5.7:rc2:*:*:*:*:*:*
linux linux_kernel 5.7 cpe:2.3:o:linux:linux_kernel:5.7:rc3:*:*:*:*:*:*
linux linux_kernel 5.7 cpe:2.3:o:linux:linux_kernel:5.7:rc4:*:*:*:*:*:*
linux linux_kernel 5.7 cpe:2.3:o:linux:linux_kernel:5.7:rc5:*:*:*:*:*:*
linux linux_kernel 5.7 cpe:2.3:o:linux:linux_kernel:5.7:rc6:*:*:*:*:*:*
linux linux_kernel 5.7 cpe:2.3:o:linux:linux_kernel:5.7:rc7:*:*:*:*:*:*
linux linux_kernel 5.18 cpe:2.3:o:linux:linux_kernel:5.18:rc1:*:*:*:*:*:*

References for CVE-2022-49098

cvelogic Threat Intelligence