# CVE-2026-63930: iio: buffer: hw-consumer: fix use-after-free in error path

> A use-after-free vulnerability in the Linux kernel's IIO buffer subsystem allows attackers to potentially execute code or escalate privileges via a crafted error path.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jul 2026
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2026-63930, DEBIAN-CVE-2026-63930, GHSA-ggvg-29pg-f22f, ROOT-OS-UBUNTU-2204-CVE-2026-63930, UBUNTU-CVE-2026-63930

## What is CVE-2026-63930?

CVE-2026-63930 is a high-severity use after free vulnerability in Linux, published on 19 Jul 2026. 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: buffer: hw-consumer: fix use-after-free in error path

In the err_put_buffers cleanup path of iio_hw_consumer_alloc(), the code
was using list_for_each_entry() to iterate through buffers while calling
iio_buffer_put() which can free the current buffer if refcount drops to 0.
The list_for_each_entry() loop macro then evaluates buf->head.next to
continue iteration, accessing the freed buffer.

Fix this by using list_for_each_entry_safe().

## Which versions are affected by CVE-2026-63930?


## How do I fix CVE-2026-63930?

Apply the vendor's patch.

## Is CVE-2026-63930 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63930 and fix it if it is affected.

What it is: CVE-2026-63930 is a high-severity use after free vulnerability in Linux, published on 19 Jul 2026. 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-2026-63930 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-2026-63930/ (Markdown: https://insights.sbomify.com/CVE-2026-63930/index.md)
```

## Sources

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

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