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

CVE record · `CVE-2024-50230`

- **Identifiers:** `CVE-2024-50230`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-787](https://cwe.mitre.org/data/definitions/787.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 9 Nov 2024
- **Updated:** 5 Aug 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 9 Nov 2024, 10:14 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `8c26c4e2694a163d525976e804d81cd955bbb40c to before 994b2fa13a6c9cf3feca93090a9c337d48e3d60d` (git)
  - affected: `8c26c4e2694a163d525976e804d81cd955bbb40c to before 64afad73e4623308d8943645e5631f2c7a2d7971` (git)
  - affected: `8c26c4e2694a163d525976e804d81cd955bbb40c to before aa0cee46c5d3fd9a39575a4c8a4f65f25f095b89` (git)
  - affected: `8c26c4e2694a163d525976e804d81cd955bbb40c to before f05dbebb8ee34882505d53d83af7d18f28a49248` (git)
  - affected: `8c26c4e2694a163d525976e804d81cd955bbb40c to before cd0cdb51b15203fa27d4b714be83b7dfffa0b752` (git)
  - affected: `8c26c4e2694a163d525976e804d81cd955bbb40c to before f2f1fa446676c21edb777e6d2bc4fa8f956fab68` (git)
  - affected: `8c26c4e2694a163d525976e804d81cd955bbb40c to before 56c6171932a7fb267ac6cb4ff8759b93ee1d0e2e` (git)
  - affected: `8c26c4e2694a163d525976e804d81cd955bbb40c to before 41e192ad2779cae0102879612dfe46726e4396aa` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.10`
  - unaffected: `before 3.10` (semver)
  - unaffected: `4.19.323 to 4.19.*, inclusive` (semver)
  - unaffected: `5.4.285 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.229 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.171 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.116 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.60 to 6.6.*, inclusive` (semver)
  - unaffected: `6.11.7 to 6.11.*, inclusive` (semver)
  - unaffected: `6.12 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`, from CNA (Linux) (used for this record)
- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0028, the 20th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 9 Nov 2024. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2024-50230](https://www.cve.org/CVERecord?id=CVE-2024-50230)
- [NVD: CVE-2024-50230](https://nvd.nist.gov/vuln/detail/CVE-2024-50230)

### References from the CNA

- <https://git.kernel.org/stable/c/994b2fa13a6c9cf3feca93090a9c337d48e3d60d>
- <https://git.kernel.org/stable/c/64afad73e4623308d8943645e5631f2c7a2d7971>
- <https://git.kernel.org/stable/c/aa0cee46c5d3fd9a39575a4c8a4f65f25f095b89>
- <https://git.kernel.org/stable/c/f05dbebb8ee34882505d53d83af7d18f28a49248>
- <https://git.kernel.org/stable/c/cd0cdb51b15203fa27d4b714be83b7dfffa0b752>
- <https://git.kernel.org/stable/c/f2f1fa446676c21edb777e6d2bc4fa8f956fab68>
- <https://git.kernel.org/stable/c/56c6171932a7fb267ac6cb4ff8759b93ee1d0e2e>
- <https://git.kernel.org/stable/c/41e192ad2779cae0102879612dfe46726e4396aa>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2024-50230>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2024-50230/>. Everything for agents: <https://agentprime.io/llms.txt>.
