CVE-2022-49098: Drivers: hv: vmbus: Fix potential crash on module unload
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2133c422a103cf7c7768c37b9ac382e73b691892, 3d0078f8bddd58d9bb1ad40bbe929f8633abb276, 4.19.238.
Low priority for now. Upgrade to Linux Linux 2133c422a103cf7c7768c37b9ac382e73b691892, 3d0078f8bddd58d9bb1ad40bbe929f8633abb276, 4.19.238 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.19.118 and later · before 4.19.238
- linux linux kernel5.4.35 and later · before 5.4.189
- linux linux kernel5.6.7 and later · before 5.7
- linux linux kernel5.7.1 and later · before 5.10.111
- linux linux kernel5.11 and later · before 5.15.34
- linux linux kernel5.16 and later · before 5.16.20
- linux linux kernel5.17 and later · before 5.17.3
- linux linux kernel5.18
- linux linux kernel5.7
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- caeeb3787167c884b955404a7e669fd77f267e44, 5.7affected
- 5e059fc0f054309036d3f612bc8b0a502ca58545 and later · before 6b4c0149a56147b29169e07000d566162892722aaffected · git
- 9f38f7b46de0747c1909e8c557aa21715dce20c5 and later · before 2133c422a103cf7c7768c37b9ac382e73b691892affected · git
- 74347a99e73ae00b8385f1209aaea193c670f901 and later · before cf580d2e3884dbafd6b90269b03a24d661578624affected · git
- 74347a99e73ae00b8385f1209aaea193c670f901 and later · before dcd6b1a624c0ffa21034d8b1e02e9d068458f596affected · git
- 74347a99e73ae00b8385f1209aaea193c670f901 and later · before 5ea98d0f5f035c1bcf1517ccec0e024ae35a48b2affected · git
- 74347a99e73ae00b8385f1209aaea193c670f901 and later · before 3d0078f8bddd58d9bb1ad40bbe929f8633abb276affected · git
- 74347a99e73ae00b8385f1209aaea193c670f901 and later · before 792f232d57ff28bbd5f9c4abe0466b23d5879dc8affected · git
- 4.19.118 and later · before 4.19.238affected · semver
- 5.4.35 and later · before 5.4.189affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.17.3-1 | 5.17.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49096Feb 26, 2025 · net: sfc: add missing xdp queue reinitialization22Monitor
- ← EarlierCVE-2022-49097Feb 26, 2025 · NFS: Avoid writeback threads getting stuck in mempool_alloc()22Monitor
- Later →CVE-2022-49099Feb 26, 2025 · Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_register()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2133c422a103cf7c7768c37b9ac382e73b691892 | Vendor (CNA) |
| Linux Linux | 3d0078f8bddd58d9bb1ad40bbe929f8633abb276 | Vendor (CNA) |
| Linux Linux | 4.19.238 | Vendor (CNA) |
| Linux Linux | 5.4.189 | Vendor (CNA) |
| Linux Linux | 5.7 | Vendor (CNA) |
| Linux Linux | 5ea98d0f5f035c1bcf1517ccec0e024ae35a48b2 | Vendor (CNA) |
| Linux Linux | 6b4c0149a56147b29169e07000d566162892722a | Vendor (CNA) |
| Linux Linux | 792f232d57ff28bbd5f9c4abe0466b23d5879dc8 | Vendor (CNA) |
| Linux Linux | cf580d2e3884dbafd6b90269b03a24d661578624 | Vendor (CNA) |
| Linux Linux | dcd6b1a624c0ffa21034d8b1e02e9d068458f596 | Vendor (CNA) |
| debian:linux | 5.17.3-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/3d0078f8bddd58d9bb1ad40bbe929f8633abb276
- git.kernel.org/stable/c/5ea98d0f5f035c1bcf1517ccec0e024ae35a48b2
- git.kernel.org/stable/c/6b4c0149a56147b29169e07000d566162892722a
- git.kernel.org/stable/c/792f232d57ff28bbd5f9c4abe0466b23d5879dc8
- git.kernel.org/stable/c/cf580d2e3884dbafd6b90269b03a24d661578624
- git.kernel.org/stable/c/dcd6b1a624c0ffa21034d8b1e02e9d068458f596
Vendor advisories and official records. Exploit/PoC links are deliberately left out.