Menu

Star on GitHub · 3.2k

CVE-2022-50561

In the Linux kernel, the following vulnerability has been resolved: iio: fix memory leak in iio_device_register_eventset() When iio_device_register_sysfs_group() returns failed, iio_device_regist…

Published Oct 22, 2025EPSS 0.21%

Overview

CVE-2022-50561 is a known-severity vulnerability. It was published on October 22, 2025.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

iio: fix memory leak in iio_device_register_eventset()

When iio_device_register_sysfs_group() returns failed,

iio_device_register_eventset() needs to free attrs array.

Otherwise, kmemleak would scan & report memory leak as below:

unreferenced object 0xffff88810a1cc3c0 (size 32):

comm "100-i2c-vcnl302", pid 728, jiffies 4295052307 (age 156.027s)

backtrace:

__kmalloc+0x46/0x1b0

iio_device_register_eventset at drivers/iio/industrialio-event.c:541

__iio_device_register at drivers/iio/industrialio-core.c:1959

__devm_iio_device_register at drivers/iio/industrialio-core.c:2040

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.

Frequently asked questions

What is CVE-2022-50561?

CVE-2022-50561 is a known-severity vulnerability. It was published on October 22, 2025.

How severe is CVE-2022-50561?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2022-50561?

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.

How can CyberStrike help with CVE-2022-50561?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50561 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.