# CVE-2025-68330: iio: accel: bmc150: Fix irq assumption regression

> A local attacker can trigger a kernel NULL pointer dereference in the BMC150 accelerometer driver, causing a system crash.

- **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:** 22 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-68330, DEBIAN-CVE-2025-68330, GHSA-vm46-5j34-6g6f, ROOT-OS-DEBIAN-11-CVE-2025-68330, ROOT-OS-DEBIAN-12-CVE-2025-68330, ROOT-OS-DEBIAN-13-CVE-2025-68330, ROOT-OS-UBUNTU-2204-CVE-2025-68330, ROOT-OS-UBUNTU-2404-CVE-2025-68330, UBUNTU-CVE-2025-68330

## What is CVE-2025-68330?

CVE-2025-68330 is a vulnerability in Linux, published on 22 Dec 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: bmc150: Fix irq assumption regression

The code in bmc150-accel-core.c unconditionally calls
bmc150_accel_set_interrupt() in the iio_buffer_setup_ops,
such as on the runtime PM resume path giving a kernel
splat like this if the device has no interrupts:

Unable to handle kernel NULL pointer dereference at virtual
  address 00000001 when read

PC is at bmc150_accel_set_interrupt+0x98/0x194
LR is at __pm_runtime_resume+0x5c/0x64
(...)
Call trace:
bmc150_accel_set_interrupt from bmc150_accel_buffer_postenable+0x40/0x108
bmc150_accel_buffer_postenable from __iio_update_buffers+0xbe0/0xcbc
__iio_update_buffers from enable_store+0x84/0xc8
enable_store from kernfs_fop_write_iter+0x154/0x1b4

This bug seems to have been in the driver since the beginning,
but it only manifests recently, I do not know why.

Store the IRQ number in the state struct, as this is a common
pattern in other drivers, then use this to determine if we have
IRQ support or not.

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


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

Apply the vendor's patch.

## Is CVE-2025-68330 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68330 is a vulnerability in Linux, published on 22 Dec 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-68330 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-2025-68330/ (Markdown: https://insights.sbomify.com/CVE-2025-68330/index.md)
```

## Sources

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

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