Vulnerability · Published Apr 3, 2024 · Assigned by Linux

CVE-2024-26696nilfs2: fix hang in nilfs_lookup_dirty_data_buffers()

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 9% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 91.2% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix hang in nilfs_lookup_dirty_data_buffers() Syzbot reported a hang issue in migrate_pages_batch() called by mbind() and nilfs_lookup_dirty_data_buffers() called in the log writer of nilfs2. While migrate_pages_batch() locks a folio and waits for the writeback to complete, the log writer thread that should bring the writeback to completion picks up the folio being written back in nilfs_lookup_dirty_data_buffers() that it calls for subsequent log creation and was trying to lock the folio. Thus causing a deadlock. In the first place, it is unexpected that folios/pages in the middle of writeback will be updated and become dirty. Nilfs2 adds a checksum to verify the validity of the log being written and uses it for recovery at mount, so data changes during writeback are suppressed. Since this is broken, an unclean shutdown could potentially cause recovery to fail. Investigation revealed that the root cause is that the wait for writeback completion in nilfs_page_mkwrite() is conditional, and if the backing device does not require stable writes, data may be modified without waiting. Fix these issues by making nilfs_page_mkwrite() wait for writeback to finish regardless of the stable write requirement of the backing device.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.82-1DEBIAN-CVE-2024-26696
Debian:13linux6.7.7-1DEBIAN-CVE-2024-26696
Debian:14linux6.7.7-1DEBIAN-CVE-2024-26696
Ubuntu:22.04:LTSlinux5.15.0-106.116UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-aws5.15.0-1061.67UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-aws-6.56.5.0-1023.23~22.04.1UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-aws-6.56.5.0-1023.23~22.04.1USN-6895-3
Ubuntu:22.04:LTSlinux-azure5.15.0-1063.72UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-azure-6.56.5.0-1024.25~22.04.1UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-azure-6.56.5.0-1024.25~22.04.1USN-6895-2
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1063.72.1UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-gcp5.15.0-1059.67UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-gcp-6.56.5.0-1024.26~22.04.1USN-6895-2
Ubuntu:22.04:LTSlinux-gcp-6.56.5.0-1024.26~22.04.1UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-gke5.15.0-1058.63UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1044.51UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-hwe-6.56.5.0-44.44~22.04.1USN-6900-1
Ubuntu:22.04:LTSlinux-hwe-6.56.5.0-44.44~22.04.1UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-ibm5.15.0-1054.57UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1057.63UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-kvm5.15.0-1058.63UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-106.116UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.56.5.0-44.44.1~22.04.1UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.56.5.0-44.44.1~22.04.1USN-6895-3
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1054.55UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-nvidia-6.56.5.0-1023.24USN-6895-1
Ubuntu:22.04:LTSlinux-nvidia-6.56.5.0-1023.24UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1026.26UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1015.15UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-oem-6.56.5.0-1027.28USN-6895-4
Ubuntu:22.04:LTSlinux-oem-6.56.5.0-1027.28UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-oracle5.15.0-1059.65UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-oracle-6.56.5.0-1026.26~22.04.1UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-oracle-6.56.5.0-1026.26~22.04.1USN-6895-3
Ubuntu:22.04:LTSlinux-raspi5.15.0-1054.57UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-starfive-6.56.5.0-1017.18~22.04.1USN-6895-3
Ubuntu:22.04:LTSlinux-starfive-6.56.5.0-1017.18~22.04.1UBUNTU-CVE-2024-26696
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1030.34UBUNTU-CVE-2024-26696

Affected products (as reported)

VendorProductVersions
Linux Linux 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 – before 228742b2ddfb99dfd71e5a307e6088ab6836272e1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 – before 862ee4422c38be5c249844a684b00d0dbe9d1e461d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 – before 98a4026b22ff440c7f47056481bcbbe442f607d61d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 – before 7e9b622bd0748cc104d66535b76d9b3535f9dc0f1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 – before 8494ba2c9ea00a54d5b50e69b22c55a8958bce321d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 – before ea5ddbc11613b55e5128c85f57b08f907abd9b281d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 – before e38585401d464578d30f5868ff4ca54475c34f7d1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 – before 38296afe3c6ee07319e01bb249aa4bb47c07b534
Linux Linux 3.9

References