# CVE-2022-50561: iio: fix memory leak in iio_device_register_eventset()

> A memory leak in the Linux kernel IIO subsystem allows local attackers to exhaust system memory, potentially causing a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Oct 2025
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-50561, GHSA-9xgm-4j53-mch4, UBUNTU-CVE-2022-50561

## What is CVE-2022-50561?

CVE-2022-50561 is a memory corruption vulnerability in Linux, published on 22 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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

## Which versions are affected by CVE-2022-50561?


## How do I fix CVE-2022-50561?

Apply the vendor's patch.

## Is CVE-2022-50561 being exploited?

There is no known exploitation of CVE-2022-50561 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50561 and fix it if it is affected.

What it is: CVE-2022-50561 is a memory corruption vulnerability in Linux, published on 22 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-50561 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-50561/ (Markdown: https://insights.sbomify.com/CVE-2022-50561/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-50561
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-50561
- OSV: https://osv.dev/vulnerability/CVE-2022-50561

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-50561/
Summaries are generated and may contain mistakes; the official description above is the record.