| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025072815-CVE-2025-38485-3cec@gregkh> Date: Mon, 28 Jul 2025 13:22:27 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-38485: iio: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: iio: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush fxls8962af_fifo_flush() uses indio_dev->active_scan_mask (with iio_for_each_active_channel()) without making sure the indio_dev stays in buffer mode. There is a race if indio_dev exits buffer mode in the middle of the interrupt that flushes the fifo. Fix this by calling synchronize_irq() to ensure that no interrupt is currently running when disabling buffer mode. Unable to handle kernel NULL pointer dereference at virtual address 00000000 when read [...] _find_first_bit_le from fxls8962af_fifo_flush+0x17c/0x290 fxls8962af_fifo_flush from fxls8962af_interrupt+0x80/0x178 fxls8962af_interrupt from irq_thread_fn+0x1c/0x7c irq_thread_fn from irq_thread+0x110/0x1f4 irq_thread from kthread+0xe0/0xfc kthread from ret_from_fork+0x14/0x2c The Linux kernel CVE team has assigned CVE-2025-38485 to this issue. Affected and fixed versions =========================== Issue introduced in 5.14 with commit 79e3a5bdd9efbdf4e1069793d7735b432d641e7c and fixed in 6.1.147 with commit 6ecd61c201b27ad2760b3975437ad2b97d725b98 Issue introduced in 5.14 with commit 79e3a5bdd9efbdf4e1069793d7735b432d641e7c and fixed in 6.6.100 with commit dda42f23a8f5439eaac9521ce0531547d880cc54 Issue introduced in 5.14 with commit 79e3a5bdd9efbdf4e1069793d7735b432d641e7c and fixed in 6.12.40 with commit bfcda3e1015791b3a63fb4d3aad408da9cf76e8f Issue introduced in 5.14 with commit 79e3a5bdd9efbdf4e1069793d7735b432d641e7c and fixed in 6.15.8 with commit 1803d372460aaa9ae0188a30c9421d3f157f2f04 Issue introduced in 5.14 with commit 79e3a5bdd9efbdf4e1069793d7735b432d641e7c and fixed in 6.16 with commit 1fe16dc1a2f5057772e5391ec042ed7442966c9a Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2025-38485 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/iio/accel/fxls8962af-core.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/6ecd61c201b27ad2760b3975437ad2b97d725b98 https://git.kernel.org/stable/c/dda42f23a8f5439eaac9521ce0531547d880cc54 https://git.kernel.org/stable/c/bfcda3e1015791b3a63fb4d3aad408da9cf76e8f https://git.kernel.org/stable/c/1803d372460aaa9ae0188a30c9421d3f157f2f04 https://git.kernel.org/stable/c/1fe16dc1a2f5057772e5391ec042ed7442966c9a
Powered by blists - more mailing lists