CVE-2022-50813
UnknownEPSS 0.23%
Last modified
CVE-2022-50813 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: drivers: mcb: fix resource leak in mcb_probe() When probe hook function failed in mcb_probe(), it doesn't put the device. Compiled test only.. EPSS estimates a 0.23% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: drivers: mcb: fix resource leak in mcb_probe() When probe hook function failed in mcb_probe(), it doesn't put the device. Compiled test only.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 7bc364097a89a0a9a5e5e4989d6b3e6fb2027a9e, < 531ac7b911a962b3b29565dad6ea6b5c3fad3317; >= 7bc364097a89a0a9a5e5e4989d6b3e6fb2027a9e, < 6f3467aa5712e6b5550e75a16454b3f17aa1f380; >= 7bc364097a89a0a9a5e5e4989d6b3e6fb2027a9e, < e420ca85bf42a684ea729c505c07de6709500ed2; >= 7bc364097a89a0a9a5e5e4989d6b3e6fb2027a9e, < 68e54d9ee8222d7805a0b9d3e1c37b8cf3be536a; >= 7bc364097a89a0a9a5e5e4989d6b3e6fb2027a9e, < 0d1c2c8db28919c4351000d7c1692f1767bdc4f7; >= 7bc364097a89a0a9a5e5e4989d6b3e6fb2027a9e, < f3686e5e8de0a03c8e70e3ee0ce3078fed612909; >= 7bc364097a89a0a9a5e5e4989d6b3e6fb2027a9e, < 0a23dda78946f604ff752fe223c3c1f4fa6dd7b4; >= 7bc364097a89a0a9a5e5e4989d6b3e6fb2027a9e, < 0468a585710bbb807a1b9c31df54bcf564d28b2b; >= 7bc364097a89a0a9a5e5e4989d6b3e6fb2027a9e, < d7237462561fcd224fa687c56ccb68629f50fc0d |
| Linux | Linux | 4.7 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2022-50813?
In the Linux kernel, the following vulnerability has been resolved:
drivers: mcb: fix resource leak in mcb_probe()
When probe hook function failed in mcb_probe(), it doesn't put the device.
Compiled test only.
How severe is CVE-2022-50813?
Severity scoring for CVE-2022-50813 is pending analysis. The EPSS model estimates a 0.23% probability of exploitation in the next 30 days.
How do I fix CVE-2022-50813?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-50807Rejected reason: This candidate was withdrawn by its CNA. Fu…
- CVE-2022-50808CoolerMaster MasterPlus 1.8.5 contains an unquoted service p…8.5
- CVE-2022-50809In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50810In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50811In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50812In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50814In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50815In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50816In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50817In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50818In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50819In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2022-50813?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST