Bug 2348148 (CVE-2022-49098) - CVE-2022-49098 kernel: Drivers: hv: vmbus: Fix potential crash on module unload
Summary: CVE-2022-49098 kernel: Drivers: hv: vmbus: Fix potential crash on module unload
Keywords:
Status: NEW
Alias: CVE-2022-49098
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-26 03:19 UTC by OSIDB Bzimport
Modified: 2025-02-27 08:56 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-02-26 03:19:16 UTC
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.

Comment 1 Avinash Hanwate 2025-02-26 19:03:06 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022600-CVE-2022-49098-9755@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.