{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68330 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-68330 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2025-68330 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-68330/ (Markdown: https://insights.sbomify.com/CVE-2025-68330/index.md)","id":"CVE-2025-68330","markdown":"https://insights.sbomify.com/CVE-2025-68330/index.md","name":"CVE-2025-68330","record":{"aliases":["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"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A local attacker can trigger a kernel NULL pointer dereference in the BMC150 accelerometer driver, causing a system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\niio: accel: bmc150: Fix irq assumption regression\n\nThe code in bmc150-accel-core.c unconditionally calls\nbmc150_accel_set_interrupt() in the iio_buffer_setup_ops,\nsuch as on the runtime PM resume path giving a kernel\nsplat like this if the device has no interrupts:\n\nUnable to handle kernel NULL pointer dereference at virtual\n  address 00000001 when read\n\nPC is at bmc150_accel_set_interrupt+0x98/0x194\nLR is at __pm_runtime_resume+0x5c/0x64\n(...)\nCall trace:\nbmc150_accel_set_interrupt from bmc150_accel_buffer_postenable+0x40/0x108\nbmc150_accel_buffer_postenable from __iio_update_buffers+0xbe0/0xcbc\n__iio_update_buffers from enable_store+0x84/0xc8\nenable_store from kernfs_fop_write_iter+0x154/0x1b4\n\nThis bug seems to have been in the driver since the beginning,\nbut it only manifests recently, I do not know why.\n\nStore the IRQ number in the state struct, as this is a common\npattern in other drivers, then use this to determine if we have\nIRQ support or not.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"iio: accel: bmc150: Fix irq assumption regression","id":"CVE-2025-68330","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"usb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer","id":"CVE-2025-68331"},"packages":[],"prev":{"headline":"tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs","id":"CVE-2025-68329"},"products":["Linux"],"published":"2025-12-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A local attacker can trigger a kernel NULL pointer dereference in the BMC150 accelerometer driver, causing a system crash.","url":"https://insights.sbomify.com/CVE-2025-68330/"}