Description
In the Linux kernel, the following vulnerability has been resolved: HID: i2c-hid: remove I2C_HID_READ_PENDING flag to prevent lock-up The flag I2C_HID_READ_PENDING is used to serialize I2C operations. However, this is not necessary, because I2C core already has its own locking for that. More importantly, this flag can cause a lock-up: if the flag is set in i2c_hid_xfer() and an interrupt happens, the interrupt handler (i2c_hid_irq) will check this flag and return immediately without doing anything, then the interrupt handler will be invoked again in an infinite loop. Since interrupt handler is an RT task, it takes over the CPU and the flag-clearing task never gets scheduled, thus we have a lock-up. Delete this unnecessary flag.
Details
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| linux | — | 6.8.0-39.39 |
| linux-allwinner-5.19 | — | — |
| linux-aws | — | 6.8.0-1012.13 |
| linux-aws-5.0 | — | — |
| linux-aws-5.11 | — | — |
| linux-aws-5.13 | — | — |
| linux-aws-5.15 | — | 5.15.0-1065.71~20.04.1 |
| linux-aws-5.19 | — | — |
| linux-aws-5.3 | — | — |
| linux-aws-5.4 | — | 5.4.0-1128.138~18.04.1 |
| linux-aws-5.8 | — | — |
| linux-aws-6.2 | — | — |
| linux-aws-6.5 | — | — |
| linux-aws-6.8 | — | 6.8.0-1013.14~22.04.1 |
| linux-aws-fips | — | 5.15.0-1065.71+fips1 |
| linux-aws-hwe | — | 4.15.0-1170.183~16.04.1 |
| linux-azure | — | 6.8.0-1012.14 |
| linux-azure-4.15 | — | 4.15.0-1179.194 |
| linux-azure-5.11 | — | — |
| linux-azure-5.13 | — | — |
| linux-azure-5.15 | — | 5.15.0-1068.77~20.04.1 |
| linux-azure-5.19 | — | — |
| linux-azure-5.3 | — | — |
| linux-azure-5.4 | — | 5.4.0-1133.140~18.04.1 |
| linux-azure-5.8 | — | — |
| linux-azure-6.2 | — | — |
| linux-azure-6.5 | — | — |
| linux-azure-6.8 | — | 6.8.0-1012.14~22.04.1 |
| linux-azure-edge | — | — |
| linux-azure-fde | — | 5.15.0-1068.77.1 |
| linux-azure-fde-5.19 | — | — |
| linux-azure-fde-6.2 | — | — |
| linux-azure-fips | — | 5.15.0-1068.77+fips1 |
| linux-bluefield | — | — |
| linux-fips | — | 6.8.0-78.78+fips1 |
| linux-gcp | — | 6.8.0-1011.12 |
| linux-gcp-4.15 | — | 4.15.0-1164.181 |
| linux-gcp-5.11 | — | — |
| linux-gcp-5.13 | — | — |
| linux-gcp-5.15 | — | 5.15.0-1065.73~20.04.1 |
| linux-gcp-5.19 | — | — |
| linux-gcp-5.3 | — | — |
| linux-gcp-5.4 | — | 5.4.0-1132.141~18.04.1 |
| linux-gcp-5.8 | — | — |
| linux-gcp-6.2 | — | — |
| linux-gcp-6.5 | — | — |
| linux-gcp-6.8 | — | 6.8.0-1011.12~22.04.1 |
| linux-gcp-fips | — | 5.15.0-1064.72+fips1 |
| linux-gke | — | 6.8.0-1007.10 |
| linux-gke-4.15 | — | — |
| linux-gke-5.15 | — | — |
| linux-gke-5.4 | — | — |
| linux-gkeop | — | 5.15.0-1048.55 |
| linux-gkeop-5.15 | — | 5.15.0-1048.55~20.04.1 |
| linux-gkeop-5.4 | — | — |
| linux-hwe | — | — |
| linux-hwe-5.11 | — | — |
| linux-hwe-5.13 | — | — |
| linux-hwe-5.15 | — | 5.15.0-116.126~20.04.1 |
| linux-hwe-5.19 | — | — |
| linux-hwe-5.4 | — | 5.4.0-189.209~18.04.1 |
| linux-hwe-5.8 | — | — |
| linux-hwe-6.2 | — | — |
| linux-hwe-6.5 | — | — |
| linux-hwe-6.8 | — | 6.8.0-39.39~22.04.1 |
| linux-hwe-edge | — | — |
| linux-ibm | — | 6.8.0-1009.9 |
| linux-ibm-5.15 | — | 5.15.0-1058.61~20.04.1 |
| linux-ibm-5.4 | — | 5.4.0-1075.80~18.04.1 |
| linux-ibm-6.8 | — | 6.8.0-1010.10~22.04.1 |
| linux-intel-5.13 | — | — |
| linux-intel-iot-realtime | — | 5.15.0-1058.60 |
| linux-intel-iotg | — | 5.15.0-1060.66 |
| linux-intel-iotg-5.15 | — | 5.15.0-1060.66~20.04.1 |
| linux-iot | — | 5.4.0-1040.41 |
| linux-kvm | — | 5.15.0-1062.67 |
| linux-lowlatency | — | 6.8.0-39.39.1 |
| linux-lowlatency-hwe-5.15 | — | 5.15.0-116.126~20.04.1 |
| linux-lowlatency-hwe-5.19 | — | — |
| linux-lowlatency-hwe-6.2 | — | — |
| linux-lowlatency-hwe-6.5 | — | — |
| linux-lowlatency-hwe-6.8 | — | 6.8.0-40.40.1~22.04.1 |
| linux-lts-xenial | — | 4.4.0-257.291~14.04.1 |
| linux-nvidia | — | 6.8.0-1010.10 |
| linux-nvidia-6.2 | — | — |
| linux-nvidia-6.5 | — | — |
| linux-nvidia-6.8 | — | 6.8.0-1010.10~22.04.1 |
| linux-nvidia-lowlatency | — | 6.8.0-1011.11.1 |
| linux-nvidia-tegra | — | 5.15.0-1026.26 |
| linux-nvidia-tegra-5.15 | — | 5.15.0-1027.27~20.04.1 |
| linux-nvidia-tegra-igx | — | 5.15.0-1015.15 |
| linux-oem | — | — |
| linux-oem-5.10 | — | — |
| linux-oem-5.13 | — | — |
| linux-oem-5.14 | — | — |
| linux-oem-5.17 | — | — |
| linux-oem-5.6 | — | — |
| linux-oem-6.0 | — | — |
| linux-oem-6.1 | — | — |
| linux-oem-6.5 | — | — |
| linux-oem-6.8 | — | 6.8.0-1009.9 |
| linux-oracle | — | 6.8.0-1010.10 |
| linux-oracle-5.0 | — | — |
| linux-oracle-5.11 | — | — |
| linux-oracle-5.13 | — | — |
| linux-oracle-5.15 | — | 5.15.0-1063.69~20.04.1 |
| linux-oracle-5.3 | — | — |
| linux-oracle-5.4 | — | 5.4.0-1127.136~18.04.1 |
| linux-oracle-5.8 | — | — |
| linux-oracle-6.5 | — | — |
| linux-oracle-6.8 | — | 6.8.0-1010.10~22.04.1 |
| linux-raspi | — | 6.8.0-1008.8 |
| linux-raspi-5.4 | — | 5.4.0-1112.124~18.04.1 |
| linux-raspi-realtime | — | 6.8.0-2007.7 |
| linux-raspi2 | — | — |
| linux-realtime | — | 6.8.1-1005.5 |
| linux-realtime-6.8 | — | 6.8.1-1005.5~22.04.2 |
| linux-riscv | — | 6.8.0-39.39.1 |
| linux-riscv-5.11 | — | — |
| linux-riscv-5.15 | — | 5.15.0-1061.65~20.04.1 |
| linux-riscv-5.19 | — | — |
| linux-riscv-5.8 | — | — |
| linux-riscv-6.5 | — | — |
| linux-riscv-6.8 | — | 6.8.0-39.39.1~22.04.1 |
| linux-starfive-5.19 | — | — |
| linux-starfive-6.2 | — | — |
| linux-starfive-6.5 | — | — |
| linux-xilinx-zynqmp | — | 5.15.0-1035.39 |
References
Similar Threats
- Unknown CGA-23jx-hhcx-m389
- Unknown CGA-2qp7-6757-fmgc
- Unknown CGA-2rj5-jc55-r267
- Unknown CGA-3m96-cwq8-6xmx
- Unknown CGA-3qj9-973w-fh9g
Free Vulnerability Check
Is your WordPress site affected?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.
