CVE-2025-68330
Last modified
CVE-2025-68330 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= c16bff4844ffa678ba0c9d077e9797506924ccdd, < aad9d048a3211c48ec02efa405bf462856feb862; >= c16bff4844ffa678ba0c9d077e9797506924ccdd, < c891f504bb66604c822e7985e093cf39b97fdeb0; >= c16bff4844ffa678ba0c9d077e9797506924ccdd, < cdd4a9e98004bd7c7488311951fa6dbae38b2b80; >= c16bff4844ffa678ba0c9d077e9797506924ccdd, < 65ad4ed983fd9ee0259d86391d6a53f78203918c; >= c16bff4844ffa678ba0c9d077e9797506924ccdd, < 93eaa5ddc5fc4f50ac396afad8ce261102ebd4f3; >= c16bff4844ffa678ba0c9d077e9797506924ccdd, < 3aa385a9c75c09b59dcab2ff76423439d23673ab |
| Linux | Linux | 4.2 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-68330?
How severe is CVE-2025-68330?
How do I fix CVE-2025-68330?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-68325In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68326In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68327In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68328In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68329In the Linux kernel, the following vulnerability has been re…
- CVE-2025-6833The All in One Time Clock Lite – Tracking Employee Time Has …4.3
- CVE-2025-68331In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68332In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68333In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-68334In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68335In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68336In the Linux kernel, the following vulnerability has been re…7.5
Are you affected by CVE-2025-68330?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
