CVE-2020-35513

What it is

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.

At a glance

Exploitability

Can be exploited over the network with an admin-level account. High risk of service disruption.

Exploit odds

1.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2021-01-26 18:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 03:13 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.4% in the next 30 days (EPSS).
• Severity: 4.9 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2021-01-26 18:15 UTC

Last modified

2026-06-17 03:13 UTC

Exploit probability

1.4% · EPSS, next 30 days

Weakness

CWE-271

Record status

Modified

Affected

• Linux Kernel 4.2
• Redhat Enterprise Linux 7.0

Attack profile CVSS 3.1 · 4.9

Attack vector

Network

Complexity

Low

Privileges needed

High

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-35513.md and follow it. Check whether this project is affected by CVE-2020-35513. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge