Drivers: hv: vmbus: Fix potential crash on module unload
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.19.238, 5.4.189, 5.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 4.19.118 · fixed in 4.19.238; From 5.4.35 · fixed in 5.4.189; From 5.6.7 · fixed in 5.7
- Linux Linux
5.7
References 7
git.kernel.org
- stable/c/6b4c0149a56147b29169e07000d566162892722a
- stable/c/2133c422a103cf7c7768c37b9ac382e73b691892
- stable/c/cf580d2e3884dbafd6b90269b03a24d661578624
- stable/c/dcd6b1a624c0ffa21034d8b1e02e9d068458f596
- stable/c/5ea98d0f5f035c1bcf1517ccec0e024ae35a48b2
- stable/c/3d0078f8bddd58d9bb1ad40bbe929f8633abb276
- stable/c/792f232d57ff28bbd5f9c4abe0466b23d5879dc8