CVE-2022-50550
Last modified
CVE-2022-50550 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: blk-iolatency: Fix memory leak on add_disk() failures When a gendisk is successfully initialized but add_disk() fails such as when a loop device has invalid number of minor device numbers specified, blkcg_init_disk() is called during init and then blkcg_exit_disk() during error handling. Unfortunately, iolatency gets initialized in the former but doesn't get cleaned up in the latter. This is because, in non-error cases, the cleanup is performed by del_gendisk() calling rq_qos_exit(), the assumption being that rq_qos policies, iolatency being one of them, can only be activated once the disk is fully registered and visible. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: blk-iolatency: Fix memory leak on add_disk() failures When a gendisk is successfully initialized but add_disk() fails such as when a loop device has invalid number of minor device numbers specified, blkcg_init_disk() is called during init and then blkcg_exit_disk() during error handling. Unfortunately, iolatency gets initialized in the former but doesn't get cleaned up in the latter. This is because, in non-error cases, the cleanup is performed by del_gendisk() calling rq_qos_exit(), the assumption being that rq_qos policies, iolatency being one of them, can only be activated once the disk is fully registered and visible. That assumption is true for wbt and iocost, but not so for iolatency as it gets initialized before add_disk() is called. It is desirable to lazy-init rq_qos policies because they are optional features and add to hot path overhead once initialized - each IO has to walk all the registered rq_qos policies. So, we want to switch iolatency to lazy init too. However, that's a bigger change. As a fix for the immediate problem, let's just add an extra call to rq_qos_exit() in blkcg_exit_disk(). This is safe because duplicate calls to rq_qos_exit() become noop's.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 4.19, < 6.0.17 |
| Linux | Linux Kernel | >= 6.1, < 6.1.2 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2022-50550?
How severe is CVE-2022-50550?
How do I fix CVE-2022-50550?
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-50544In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50545In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50546In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50547In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50548In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50549In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50551In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2022-50552In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50553In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50554In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50555In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50556In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2022-50550?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
