Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Fixed version: Linux Linux 3aa385a9c75c09b59dcab2ff76423439d23673ab, 65ad4ed983fd9ee0259d86391d6a53f78203918c, 93eaa5ddc5fc4f50ac396afad8ce261102ebd4f3; azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 6.6.119.3-1.

Low priority for now. Upgrade to Linux Linux 3aa385a9c75c09b59dcab2ff76423439d23673ab, 65ad4ed983fd9ee0259d86391d6a53f78203918c, 93eaa5ddc5fc4f50ac396afad8ce261102ebd4f3; azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 6.6.119.3-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Dec 22, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 8th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-68330

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.2affected
    • c16bff4844ffa678ba0c9d077e9797506924ccdd and later · before aad9d048a3211c48ec02efa405bf462856feb862affected · git
    • c16bff4844ffa678ba0c9d077e9797506924ccdd and later · before c891f504bb66604c822e7985e093cf39b97fdeb0affected · git
    • c16bff4844ffa678ba0c9d077e9797506924ccdd and later · before cdd4a9e98004bd7c7488311951fa6dbae38b2b80affected · git
    • c16bff4844ffa678ba0c9d077e9797506924ccdd and later · before 65ad4ed983fd9ee0259d86391d6a53f78203918caffected · git
    • c16bff4844ffa678ba0c9d077e9797506924ccdd and later · before 93eaa5ddc5fc4f50ac396afad8ce261102ebd4f3affected · git
    • c16bff4844ffa678ba0c9d077e9797506924ccdd and later · before 3aa385a9c75c09b59dcab2ff76423439d23673abaffected · git
    • before 4.2not affected · semver
    • 5.15.197 and later · up to and including 5.15.*not affected · semver
    • 6.1.159 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.159-16.1.159-1
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.11-16.17.11-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-68328Dec 22, 2025 · firmware: stratix10-svc: fix bug in saving controller data
    0Monitor
  • ← EarlierCVE-2025-68329Dec 22, 2025 · tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs
    0Monitor
  • Later →CVE-2025-68331Dec 22, 2025 · usb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3aa385a9c75c09b59dcab2ff76423439d23673abVendor (CNA)
Linux Linux65ad4ed983fd9ee0259d86391d6a53f78203918cVendor (CNA)
Linux Linux93eaa5ddc5fc4f50ac396afad8ce261102ebd4f3Vendor (CNA)
Linux Linuxaad9d048a3211c48ec02efa405bf462856feb862Vendor (CNA)
Linux Linuxc891f504bb66604c822e7985e093cf39b97fdeb0Vendor (CNA)
Linux Linuxcdd4a9e98004bd7c7488311951fa6dbae38b2b80Vendor (CNA)
azl3 kernel 6.6.117.1-1 on Azure Linux 3.06.6.119.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.159-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records