Description
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix kernel bug on rename operation of broken directory Syzbot reported that in rename directory operation on broken directory on nilfs2, __block_write_begin_int() called to prepare block write may fail BUG_ON check for access exceeding the folio/page size. This is because nilfs_dotdot(), which gets parent directory reference entry ("..") of the directory to be moved or renamed, does not check consistency enough, and may return location exceeding folio/page size for broken directories. Fix this issue by checking required directory entries ("." and "..") in the first chunk of the directory in nilfs_dotdot().
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-48.48 |
| linux-allwinner-5.19 | — | — |
| linux-aws | — | 6.8.0-1018.20 |
| linux-aws-5.0 | — | — |
| linux-aws-5.11 | — | — |
| linux-aws-5.13 | — | — |
| linux-aws-5.15 | — | 5.15.0-1069.75~20.04.1 |
| linux-aws-5.19 | — | — |
| linux-aws-5.3 | — | — |
| linux-aws-5.4 | — | 5.4.0-1132.142~18.04.1 |
| linux-aws-5.8 | — | — |
| linux-aws-6.2 | — | — |
| linux-aws-6.5 | — | — |
| linux-aws-6.8 | — | 6.8.0-1018.19~22.04.1 |
| linux-aws-fips | — | 5.15.0-1069.75+fips1 |
| linux-aws-hwe | — | — |
| linux-azure | — | 6.8.0-1017.20 |
| linux-azure-4.15 | — | — |
| linux-azure-5.11 | — | — |
| linux-azure-5.13 | — | — |
| linux-azure-5.15 | — | 5.15.0-1072.81~20.04.1 |
| linux-azure-5.19 | — | — |
| linux-azure-5.3 | — | — |
| linux-azure-5.4 | — | 5.4.0-1137.144~18.04.1 |
| linux-azure-5.8 | — | — |
| linux-azure-6.2 | — | — |
| linux-azure-6.5 | — | — |
| linux-azure-6.8 | — | 6.8.0-1017.20~22.04.1 |
| linux-azure-edge | — | — |
| linux-azure-fde | — | 5.15.0-1072.81.1 |
| linux-azure-fde-5.19 | — | — |
| linux-azure-fde-6.2 | — | — |
| linux-azure-fips | — | 5.15.0-1072.81+fips1 |
| linux-bluefield | — | — |
| linux-fips | — | 6.8.0-78.78+fips1 |
| linux-gcp | — | 6.8.0-1017.19 |
| linux-gcp-4.15 | — | — |
| linux-gcp-5.11 | — | — |
| linux-gcp-5.13 | — | — |
| linux-gcp-5.15 | — | 5.15.0-1068.76~20.04.1 |
| linux-gcp-5.19 | — | — |
| linux-gcp-5.3 | — | — |
| linux-gcp-5.4 | — | 5.4.0-1136.145~18.04.1 |
| linux-gcp-5.8 | — | — |
| linux-gcp-6.2 | — | — |
| linux-gcp-6.5 | — | — |
| linux-gcp-6.8 | — | 6.8.0-1017.19~22.04.1 |
| linux-gcp-fips | — | 5.15.0-1068.76+fips1 |
| linux-gke | — | 6.8.0-1013.17 |
| linux-gke-4.15 | — | — |
| linux-gke-5.15 | — | — |
| linux-gke-5.4 | — | — |
| linux-gkeop | — | 6.8.0-1002.4 |
| linux-gkeop-5.15 | — | 5.15.0-1052.59~20.04.1 |
| linux-gkeop-5.4 | — | — |
| linux-hwe | — | — |
| linux-hwe-5.11 | — | — |
| linux-hwe-5.13 | — | — |
| linux-hwe-5.15 | — | 5.15.0-121.131~20.04.1 |
| linux-hwe-5.19 | — | — |
| linux-hwe-5.4 | — | 5.4.0-195.215~18.04.1 |
| linux-hwe-5.8 | — | — |
| linux-hwe-6.2 | — | — |
| linux-hwe-6.5 | — | — |
| linux-hwe-6.8 | — | 6.8.0-48.48~22.04.1 |
| linux-hwe-edge | — | — |
| linux-ibm | — | 6.8.0-1015.15 |
| linux-ibm-5.15 | — | 5.15.0-1062.65~20.04.1 |
| linux-ibm-5.4 | — | 5.4.0-1079.84~18.04.1 |
| linux-ibm-6.8 | — | 6.8.0-1015.15~22.04.1 |
| linux-intel-5.13 | — | — |
| linux-intel-iot-realtime | — | 5.15.0-1063.65 |
| linux-intel-iotg | — | 5.15.0-1064.70 |
| linux-intel-iotg-5.15 | — | 5.15.0-1064.70~20.04.1 |
| linux-iot | — | 5.4.0-1043.44 |
| linux-kvm | — | 5.15.0-1066.71 |
| linux-lowlatency | — | 6.8.0-48.48.3 |
| linux-lowlatency-hwe-5.15 | — | 5.15.0-121.131~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-48.48.3~22.04.1 |
| linux-lts-xenial | — | — |
| linux-nvidia | — | 6.8.0-1017.19 |
| linux-nvidia-6.2 | — | — |
| linux-nvidia-6.5 | — | — |
| linux-nvidia-6.8 | — | 6.8.0-1017.19~22.04.1 |
| linux-nvidia-lowlatency | — | 6.8.0-1017.19.1 |
| linux-nvidia-tegra | — | 5.15.0-1028.28 |
| linux-nvidia-tegra-5.15 | — | 5.15.0-1030.30~20.04.1 |
| linux-nvidia-tegra-igx | — | 5.15.0-1016.16 |
| 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-1016.16 |
| linux-oracle | — | 6.8.0-1015.16 |
| linux-oracle-5.0 | — | — |
| linux-oracle-5.11 | — | — |
| linux-oracle-5.13 | — | — |
| linux-oracle-5.15 | — | 5.15.0-1067.73~20.04.1 |
| linux-oracle-5.3 | — | — |
| linux-oracle-5.4 | — | 5.4.0-1131.140~18.04.1 |
| linux-oracle-5.8 | — | — |
| linux-oracle-6.5 | — | — |
| linux-oracle-6.8 | — | 6.8.0-1015.15~22.04.1 |
| linux-raspi | — | 6.8.0-1014.16 |
| linux-raspi-5.4 | — | 5.4.0-1116.128~18.04.1 |
| linux-raspi-realtime | — | 6.8.0-2013.14 |
| linux-raspi2 | — | — |
| linux-realtime | — | 6.8.1-1011.11 |
| linux-realtime-6.8 | — | 6.8.1-1011.11~22.04.1 |
| linux-riscv | — | 6.8.0-48.48.1 |
| linux-riscv-5.11 | — | — |
| linux-riscv-5.15 | — | 5.15.0-1065.69~20.04.1 |
| linux-riscv-5.19 | — | — |
| linux-riscv-5.8 | — | — |
| linux-riscv-6.5 | — | — |
| linux-riscv-6.8 | — | 6.8.0-48.48.1~22.04.2 |
| linux-starfive-5.19 | — | — |
| linux-starfive-6.2 | — | — |
| linux-starfive-6.5 | — | — |
| linux-xilinx | — | 6.8.0-1009.10 |
| 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
Site Security Check
Concerned your site may already be targeted?
BotEraser analyzes incoming traffic patterns and helps identify bot behavior consistent with known exploit attempts.
Check 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.
