CVE-2026-43307: iio: accel: adxl380: Avoid reading more entries than present in FIFO
In the Linux kernel, the following vulnerability has been resolved:
iio: accel: adxl380: Avoid reading more entries than present in FIFO
The interrupt handler reads FIFO entries in batches of N samples, where N is the number of scan elements that have been enabled. However, the sensor fills the FIFO one sample at a time, even when more than one channel is enabled. Therefore,the number of entries reported by the FIFO status registers may not be a multiple of N; if this number is not a multiple, the number of entries read from the FIFO may exceed the number of entries actually present.
To fix the above issue, round down the number of FIFO entries read from the status registers so that it is always a multiple of N.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
In the adxl380 IIO interrupt handler, limit the FIFO read count by rounding down the number of FIFO entries reported by the FIFO status so it is never greater than the entries actually present, and ensure the resulting count is always a multiple of N (the number of enabled scan elements).
Linux kernel iio: accel: adxl380 FIFO entries read (number of scan elements per batch N) = Round down the number of FIFO entries read from the FIFO to the number of entries actually present (ensure it never exceeds available entries).
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43307?
The severity of CVE-2026-43307 is classified as a moderate risk due to potential misreads in FIFO entries.
How do I fix CVE-2026-43307?
To fix CVE-2026-43307, update your Linux kernel to the latest version where this vulnerability has been patched.
Which versions of the Linux kernel are affected by CVE-2026-43307?
CVE-2026-43307 affects specific versions of the Linux kernel that handle FIFO reading improperly.
What impact does CVE-2026-43307 have on system security?
CVE-2026-43307 could lead to incorrect data being processed, which may affect the stability and reliability of kernel operations.
Is CVE-2026-43307 being actively exploited?
As of the latest information, there is no public evidence indicating active exploitation of CVE-2026-43307.