# CVE-2026-64498: iio: buffer: hw-consumer: free scan_mask on buffer release

> A missing memory free in the Linux kernel IIO subsystem can lead to memory corruption, potentially allowing local attackers to escalate privileges or cause a denial of service.

- **Severity:** Not scored
- **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:** 25 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-64498, GHSA-vmjp-jvmv-9wwr, ROOT-OS-UBUNTU-2204-CVE-2026-64498, UBUNTU-CVE-2026-64498

## What is CVE-2026-64498?

CVE-2026-64498 is a memory corruption vulnerability in Linux, published on 25 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: free scan_mask on buffer release

The scan_mask lifetime changed in commit 9a2e1233d38c ("iio: buffer:
hw-consumer: remove redundant scan_mask flexible array").

Before that change, the scan mask storage was embedded in struct
hw_consumer_buffer, so iio_hw_buf_release() could free the whole
allocation with a single kfree(hw_buf).

That commit moved the scan mask to a separate bitmap_zalloc() allocation
stored in buffer.scan_mask, but left iio_hw_buf_release() unchanged.

Free the scan mask in iio_hw_buf_release() before freeing the buffer
wrapper.

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


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

Apply the vendor's patch.

## Is CVE-2026-64498 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64498 is a memory corruption vulnerability in Linux, published on 25 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-64498 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-64498/ (Markdown: https://insights.sbomify.com/CVE-2026-64498/index.md)
```

## Sources

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

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