Linux Kernel up to 7.1.8 NFS use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.5$5k-$25k1.72-

Summaryinfo

A vulnerability classified as very critical has been found in Linux Kernel up to 7.1.8. The affected element is an unknown function of the component NFS. This manipulation causes use after free. This vulnerability is tracked as CVE-2026-74730. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.1.8. It has been declared as very critical. Affected by this vulnerability is some unknown processing of the component NFS. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: NFS: Pin the 'struct nfs_server' during a FREE_STATEID call Dan Aloni reports that he was able to hit a use-after-free bug if a FREE_STATEID operation gets delayed for whatever reason. Fix this by bumping the refcount of the 'struct nfs_server' object for the duration of the FREE_STATEID so it doesn't get cleaned up from underneath us while operations are still in flight.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-74730 since 08/15/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/22/2026).

Upgrading to version 5.10.265, 5.15.216, 6.1.183, 6.6.152, 6.12.104, 6.18.45 or 7.1.9 eliminates this vulnerability. Applying the patch ed2f92ce2fc48463c41e0e540b9a3454889e8af8/d858ab09e787106432d4d9830bad9dfedf02f890/af62f1af182d33a0de38308c012841885d8ab92e/caee6a68ffaa5016dfc01cd0b3dc1896a32e3abd/ed1161ab6239761958b38d5667225634fc2be894/d71dfffa512e71b166a889484e4c3b148a9a3af2/80ed3d762628b36c9e4b22fac7c65b72ef3b13dd/cf616096a0f3a2b60f7d68b6b39674a6867ded9c is able to eliminate this problem.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-64417). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 9.5

VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.265/5.15.216/6.1.183/6.6.152/6.12.104/6.18.45/7.1.9
Patch: ed2f92ce2fc48463c41e0e540b9a3454889e8af8/d858ab09e787106432d4d9830bad9dfedf02f890/af62f1af182d33a0de38308c012841885d8ab92e/caee6a68ffaa5016dfc01cd0b3dc1896a32e3abd/ed1161ab6239761958b38d5667225634fc2be894/d71dfffa512e71b166a889484e4c3b148a9a3af2/80ed3d762628b36c9e4b22fac7c65b72ef3b13dd/cf616096a0f3a2b60f7d68b6b39674a6867ded9c

Timelineinfo

08/15/2026 CVE reserved
08/22/2026 +7 days Advisory disclosed
08/22/2026 +0 days VulDB entry created
08/22/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-74730 (🔒)
GCVE (CVE): GCVE-0-2026-74730
GCVE (VulDB): GCVE-100-394477
EUVD: 🔒

Entryinfo

Created: 08/22/2026 18:58
Updated: 08/22/2026 19:20
Changes: 08/22/2026 18:58 (58), 08/22/2026 19:20 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!