CVE-2025-68330

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> iio: accel: bmc150: Fix irq assumption regression<br /> <br /> The code in bmc150-accel-core.c unconditionally calls<br /> bmc150_accel_set_interrupt() in the iio_buffer_setup_ops,<br /> such as on the runtime PM resume path giving a kernel<br /> splat like this if the device has no interrupts:<br /> <br /> Unable to handle kernel NULL pointer dereference at virtual<br /> address 00000001 when read<br /> <br /> PC is at bmc150_accel_set_interrupt+0x98/0x194<br /> LR is at __pm_runtime_resume+0x5c/0x64<br /> (...)<br /> Call trace:<br /> bmc150_accel_set_interrupt from bmc150_accel_buffer_postenable+0x40/0x108<br /> bmc150_accel_buffer_postenable from __iio_update_buffers+0xbe0/0xcbc<br /> __iio_update_buffers from enable_store+0x84/0xc8<br /> enable_store from kernfs_fop_write_iter+0x154/0x1b4<br /> <br /> This bug seems to have been in the driver since the beginning,<br /> but it only manifests recently, I do not know why.<br /> <br /> Store the IRQ number in the state struct, as this is a common<br /> pattern in other drivers, then use this to determine if we have<br /> IRQ support or not.