# CVE-2022-50869: fs/ntfs3: Fix slab-out-of-bounds in r_page

> A slab-out-of-bounds write in the Linux kernel NTFS3 driver allows attackers to cause denial of service or potentially execute code via crafted filesystem images.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 Dec 2025
- **Updated:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2022-50869, GHSA-qq73-f9v2-mjmw, UBUNTU-CVE-2022-50869

## What is CVE-2022-50869?

CVE-2022-50869 is a high-severity memory corruption vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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

fs/ntfs3: Fix slab-out-of-bounds in r_page

When PAGE_SIZE is 64K, if read_log_page is called by log_read_rst for
the first time, the size of *buffer would be equal to
DefaultLogPageSize(4K).But for *buffer operations like memcpy,
if the memory area size(n) which being assigned to buffer is larger
than 4K (log->page_size(64K) or bytes(64K-page_off)), it will cause
an out of boundary error.
 Call trace:
  [...]
  kasan_report+0x44/0x130
  check_memory_region+0xf8/0x1a0
  memcpy+0xc8/0x100
  ntfs_read_run_nb+0x20c/0x460
  read_log_page+0xd0/0x1f4
  log_read_rst+0x110/0x75c
  log_replay+0x1e8/0x4aa0
  ntfs_loadlog_and_replay+0x290/0x2d0
  ntfs_fill_super+0x508/0xec0
  get_tree_bdev+0x1fc/0x34c
  [...]

Fix this by setting variable r_page to NULL in log_read_rst.

## Which versions are affected by CVE-2022-50869?


## How do I fix CVE-2022-50869?

Apply the vendor's patch.

## Is CVE-2022-50869 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50869 and fix it if it is affected.

What it is: CVE-2022-50869 is a high-severity memory corruption vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-50869 in the wild and no public exploit code.

Affected product: 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-2022-50869/ (Markdown: https://insights.sbomify.com/CVE-2022-50869/index.md)
```

## Sources

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

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