# CVE-2024-50230: nilfs2: fix kernel bug due to missing clearing of checked flag

> A missing flag clearing in the nilfs2 filesystem can trigger a kernel bug and crash the system when handling corrupted directories.

- **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:** 9 Nov 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-53004, AZL-53066, BELL-CVE-2024-50230, DEBIAN-CVE-2024-50230, GHSA-m4g4-rwxc-376v, UBUNTU-CVE-2024-50230

## What is CVE-2024-50230?

CVE-2024-50230 is a high-severity memory corruption vulnerability in Linux kernel, published on 9 Nov 2024. 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:

nilfs2: fix kernel bug due to missing clearing of checked flag

Syzbot reported that in directory operations after nilfs2 detects
filesystem corruption and degrades to read-only,
__block_write_begin_int(), which is called to prepare block writes, may
fail the BUG_ON check for accesses exceeding the folio/page size,
triggering a kernel bug.

This was found to be because the "checked" flag of a page/folio was not
cleared when it was discarded by nilfs2's own routine, which causes the
sanity check of directory entries to be skipped when the directory
page/folio is reloaded.  So, fix that.

This was necessary when the use of nilfs2's own page discard routine was
applied to more than just metadata files.

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

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-50230 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-50230 is a high-severity memory corruption vulnerability in Linux kernel, published on 9 Nov 2024. 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-2024-50230 in the wild and no public exploit code.

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

## Sources

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

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