# CVE-2024-26697: nilfs2: fix data corruption in dsync block recovery for small block sizes

> An attacker with local access can trigger data corruption and leak uninitialized memory during nilfs2 recovery on systems with small block sizes.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Apr 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2024-26697, DEBIAN-CVE-2024-26697, GHSA-xg7r-7865-v6c7, UBUNTU-CVE-2024-26697

## What is CVE-2024-26697?

CVE-2024-26697 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 3 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

nilfs2: fix data corruption in dsync block recovery for small block sizes

The helper function nilfs_recovery_copy_block() of
nilfs_recovery_dsync_blocks(), which recovers data from logs created by
data sync writes during a mount after an unclean shutdown, incorrectly
calculates the on-page offset when copying repair data to the file's page
cache.  In environments where the block size is smaller than the page
size, this flaw can cause data corruption and leak uninitialized memory
bytes during the recovery process.

Fix these issues by correcting this byte offset calculation on the page.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2024-26697?

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

## How do I fix CVE-2024-26697?

Apply the vendor's patch.

## Is CVE-2024-26697 being exploited?

There is no known exploitation of CVE-2024-26697 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-26697 and fix it if it is affected.

What it is: CVE-2024-26697 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 3 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-26697 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-26697/ (Markdown: https://insights.sbomify.com/CVE-2024-26697/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-26697
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-26697
- OSV: https://osv.dev/vulnerability/CVE-2024-26697

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-26697/
Summaries are generated and may contain mistakes; the official description above is the record.