CVE-2024-26685

    Dashboard / Vulnerabilities / CVE-2024-26685

    CVE-2024-26685

    Published: 3 Apr 2024Last Modified: 8 Oct 2026

    Summary: nilfs2: fix potential bug in end_buffer_async_write

    Details: 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.

    References: https://git.kernel.org/stable/c/2c3bdba00283a6c7a5b19481a59a730f46063803, https://git.kernel.org/stable/c/5bc09b397cbf1221f8a8aacb1152650c9195b02b, https://git.kernel.org/stable/c/626daab3811b772086aef1bf8eed3ffe6f523eff, https://git.kernel.org/stable/c/6589f0f72f8edd1fa11adce4eedbd3615f2e78ab, https://git.kernel.org/stable/c/8fa90634ec3e9cc50f42dd605eec60f2d146ced8, https://git.kernel.org/stable/c/c4a09fdac625e64abe478dcf88bfa20406616928, https://git.kernel.org/stable/c/d31c8721e816eff5ca6573cc487754f357c093cd, https://git.kernel.org/stable/c/f3e4963566f58726d3265a727116a42b591f6596, https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html, https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html, https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/26xxx/CVE-2024-26685.json, https://nvd.nist.gov/vuln/detail/CVE-2024-26685, https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected packages

    Package

    Name:

    Purl:

    Affected ranges

    Type: GIT

    Events:

    Introduced- 7f42ec3941560f0902fe3671e36f2c20ffd3af0a
    Fixed -c4a09fdac625e64abe478dcf88bfa20406616928

    Affected versions

    v3.2.102
    v3.2.101
    v3.2.100
    v3.2.99
    v3.2.98
    v3.2.97
    v3.2.96
    v3.2.95
    v3.2.94
    v3.2.93
    v3.2.92
    v3.2.91
    v3.2.90
    v3.2.89
    v3.2.88
    v3.2.87
    v3.2.86
    v3.2.85
    v3.2.84
    v3.2.83
    v3.2.82
    v3.2.81
    v3.2.80
    v3.2.79
    v3.2.78
    v3.2.77
    v3.2.76
    v3.2.75
    v3.2.74
    v3.2.73
    v3.2.72
    v3.2.71
    v3.2.70
    v3.2.69
    v3.2.68
    v3.2.67
    v3.2.66
    v3.2.65
    v3.2.64
    v3.2.63
    v3.2.62
    v3.2.61
    v3.2.60
    v3.2.59
    v3.2.58
    v3.2.57
    v3.2.56
    v3.2.55
    v3.2.54
    v3.2.53
    v3.2.52

    Common Vulnerability Scoring System

    Attack Vector
    Network
    Adjacent
    Local
    Physical
    Privileges Required
    None
    Low
    High
    User Interaction
    None
    Required
    Scope
    Unchanged
    Changed
    Confidentiality
    None
    Low
    High
    Integrity
    None
    Low
    High
    Availability
    None
    Low
    High
    CVE-2024-26685 | CVE-DB