Description
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential bug in end_buffer_async_write According to a syzbot report, end_buffer_async_write(), which handles the completion of block device writes, may detect abnormal condition of the buffer async_write flag and cause a BUG_ON failure when using nilfs2. Nilfs2 itself does not use end_buffer_async_write(). But, the async_write flag is now used as a marker by commit 7f42ec394156 ("nilfs2: fix issue with race condition of competition between segments for dirty blocks") as a means of resolving double list insertion of dirty blocks in nilfs_lookup_dirty_data_buffers() and nilfs_lookup_node_buffers() and the resulting crash. This modification is safe as long as it is used for file data and b-tree node blocks where the page caches are independent. However, it was irrelevant and redundant to also introduce async_write for segment summary and super root blocks that share buffers with the backing device. This led to the possibility that the BUG_ON check in end_buffer_async_write would fail as described above, if independent writebacks of the backing device occurred in parallel. The use of async_write for segment summary buffers has already been removed in a previous change. Fix this issue by removing the manipulation of the async_write flag for the remaining super root block buffer.
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 | — | 5.15.0-106.116 |
| linux-allwinner-5.19 | — | — |
| linux-aws | — | 5.15.0-1061.67 |
| linux-aws-5.0 | — | — |
| linux-aws-5.11 | — | — |
| linux-aws-5.13 | — | — |
| linux-aws-5.15 | — | 5.15.0-1061.67~20.04.1 |
| linux-aws-5.19 | — | — |
| linux-aws-5.3 | — | — |
| linux-aws-5.4 | — | 5.4.0-1124.134~18.04.1 |
| linux-aws-5.8 | — | — |
| linux-aws-6.2 | — | — |
| linux-aws-6.5 | — | 6.5.0-1023.23~22.04.1 |
| linux-aws-fips | — | 5.15.0-1061.67+fips1 |
| linux-aws-hwe | — | 4.15.0-1178.191~16.04.1 |
| linux-azure | — | 5.15.0-1063.72 |
| linux-azure-4.15 | — | 4.15.0-1186.201 |
| linux-azure-5.11 | — | — |
| linux-azure-5.13 | — | — |
| linux-azure-5.15 | — | 5.15.0-1063.72~20.04.1 |
| linux-azure-5.19 | — | — |
| linux-azure-5.3 | — | — |
| linux-azure-5.4 | — | 5.4.0-1129.136~18.04.1 |
| linux-azure-5.8 | — | — |
| linux-azure-6.2 | — | — |
| linux-azure-6.5 | — | 6.5.0-1024.25~22.04.1 |
| linux-azure-edge | — | — |
| linux-azure-fde | — | — |
| linux-azure-fde-5.19 | — | — |
| linux-azure-fde-6.2 | — | — |
| linux-azure-fde-6.8 | — | — |
| linux-azure-fips | — | 5.15.0-1063.72+fips1 |
| linux-bluefield | — | — |
| linux-fips | — | 5.15.0-106.116+fips1 |
| linux-gcp | — | 5.15.0-1059.67 |
| linux-gcp-4.15 | — | 4.15.0-1171.188 |
| linux-gcp-5.11 | — | — |
| linux-gcp-5.13 | — | — |
| linux-gcp-5.15 | — | 5.15.0-1059.67~20.04.1 |
| linux-gcp-5.19 | — | — |
| linux-gcp-5.3 | — | — |
| linux-gcp-5.4 | — | 5.4.0-1128.137~18.04.1 |
| linux-gcp-5.8 | — | — |
| linux-gcp-6.2 | — | — |
| linux-gcp-6.5 | — | 6.5.0-1024.26~22.04.1 |
| linux-gcp-fips | — | 5.15.0-1059.67+fips1 |
| linux-gke | — | 5.15.0-1058.63 |
| linux-gke-4.15 | — | — |
| linux-gke-5.15 | — | — |
| linux-gke-5.4 | — | — |
| linux-gkeop | — | 5.15.0-1044.51 |
| linux-gkeop-5.15 | — | 5.15.0-1044.51~20.04.1 |
| linux-gkeop-5.4 | — | — |
| linux-hwe | — | — |
| linux-hwe-5.11 | — | — |
| linux-hwe-5.13 | — | — |
| linux-hwe-5.15 | — | 5.15.0-106.116~20.04.1 |
| linux-hwe-5.19 | — | — |
| linux-hwe-5.4 | — | 5.4.0-181.201~18.04.1 |
| linux-hwe-5.8 | — | — |
| linux-hwe-6.2 | — | — |
| linux-hwe-6.5 | — | 6.5.0-44.44~22.04.1 |
| linux-hwe-edge | — | — |
| linux-ibm | — | 5.15.0-1054.57 |
| linux-ibm-5.15 | — | 5.15.0-1054.57~20.04.1 |
| linux-ibm-5.4 | — | 5.4.0-1071.76~18.04.1 |
| linux-intel-5.13 | — | — |
| linux-intel-iot-realtime | — | 5.15.0-1054.56 |
| linux-intel-iotg | — | 5.15.0-1057.63 |
| linux-intel-iotg-5.15 | — | 5.15.0-1058.64~20.04.1 |
| linux-iot | — | 5.4.0-1036.37 |
| linux-kvm | — | 5.15.0-1058.63 |
| linux-lowlatency | — | 5.15.0-106.116 |
| linux-lowlatency-hwe-5.15 | — | 5.15.0-106.116~20.04.1 |
| linux-lowlatency-hwe-5.19 | — | — |
| linux-lowlatency-hwe-6.2 | — | — |
| linux-lowlatency-hwe-6.5 | — | 6.5.0-44.44.1~22.04.1 |
| linux-lts-xenial | — | 4.4.0-266.300~14.04.1 |
| linux-nvidia | — | 5.15.0-1054.55 |
| linux-nvidia-6.2 | — | — |
| linux-nvidia-6.5 | — | 6.5.0-1023.24 |
| 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 | — | 6.5.0-1027.28 |
| linux-oracle | — | 5.15.0-1059.65 |
| linux-oracle-5.0 | — | — |
| linux-oracle-5.11 | — | — |
| linux-oracle-5.13 | — | — |
| linux-oracle-5.15 | — | 5.15.0-1059.65~20.04.1 |
| linux-oracle-5.3 | — | — |
| linux-oracle-5.4 | — | 5.4.0-1123.132~18.04.1 |
| linux-oracle-5.8 | — | — |
| linux-oracle-6.5 | — | 6.5.0-1026.26~22.04.1 |
| linux-raspi | — | 5.15.0-1054.57 |
| linux-raspi-5.4 | — | 5.4.0-1108.120~18.04.1 |
| linux-raspi-realtime | — | 6.8.0-2001.1 |
| linux-raspi2 | — | — |
| linux-realtime | — | 5.15.0-1062.70 |
| linux-riscv | — | — |
| linux-riscv-5.11 | — | — |
| linux-riscv-5.15 | — | 5.15.0-1057.61~20.04.1 |
| linux-riscv-5.19 | — | — |
| linux-riscv-5.8 | — | — |
| linux-riscv-6.5 | — | — |
| linux-starfive-5.19 | — | — |
| linux-starfive-6.2 | — | — |
| linux-starfive-6.5 | — | 6.5.0-1017.18~22.04.1 |
| linux-xilinx-zynqmp | — | 5.15.0-1030.34 |
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
Vulnerability Monitoring
Stay informed about vulnerabilities in your stack
BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →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.
