CVE-2022-50550

/// Technical 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 pol

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References