# CVE-2025-38485: iio: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush

> A race condition in the fxls8962af accelerometer driver causes a use-after-free, leading to a kernel crash and denial of service.

- **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:** 28 Jul 2025
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-65934, AZL-73452, BELL-CVE-2025-38485, DEBIAN-CVE-2025-38485, GHSA-433x-cqcq-wqv9, ROOT-OS-DEBIAN-12-CVE-2025-38485, ROOT-OS-UBUNTU-2204-CVE-2025-38485, ROOT-OS-UBUNTU-2404-CVE-2025-38485, UBUNTU-CVE-2025-38485

## What is CVE-2025-38485?

CVE-2025-38485 is a high-severity use after free vulnerability in Debian Debian Linux, published on 28 Jul 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: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush

fxls8962af_fifo_flush() uses indio_dev->active_scan_mask (with
iio_for_each_active_channel()) without making sure the indio_dev
stays in buffer mode.
There is a race if indio_dev exits buffer mode in the middle of the
interrupt that flushes the fifo. Fix this by calling
synchronize_irq() to ensure that no interrupt is currently running when
disabling buffer mode.

Unable to handle kernel NULL pointer dereference at virtual address 00000000 when read
[...]
_find_first_bit_le from fxls8962af_fifo_flush+0x17c/0x290
fxls8962af_fifo_flush from fxls8962af_interrupt+0x80/0x178
fxls8962af_interrupt from irq_thread_fn+0x1c/0x7c
irq_thread_fn from irq_thread+0x110/0x1f4
irq_thread from kthread+0xe0/0xfc
kthread from ret_from_fork+0x14/0x2c

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2025-38485?

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

## How do I fix CVE-2025-38485?

Apply the vendor's patch.

## Is CVE-2025-38485 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-38485 and fix it if it is affected.

What it is: CVE-2025-38485 is a high-severity use after free vulnerability in Debian Debian Linux, published on 28 Jul 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-2025-38485 in the wild and no public exploit code.

Affected product: Debian Debian 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-2025-38485/ (Markdown: https://insights.sbomify.com/CVE-2025-38485/index.md)
```

## Sources

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

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