Linux Kernel up to 7.1.3 proc filesystem call_proc_get_link race condition

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.
8.4$0-$5k2.32-

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.1.3. It has been rated as very critical. Affected is the function call_proc_get_link of the component proc filesystem. This manipulation causes race condition. This vulnerability appears as CVE-2026-64375. The attack requires local access. There is no available exploit.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.1.3. It has been declared as very critical. Affected by this vulnerability is the function call_proc_get_link of the component proc filesystem. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. 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: proc: protect ptrace_may_access() with exec_update_lock (FD links) proc_pid_get_link() and proc_pid_readlink() currently look up the task from the pid once, then do the ptrace access check on that task, then look up the task from the pid a second time to do the actual access. That's racy in several ways. To fix it, pass the task to the ->proc_get_link() handler, and instead of proc_fd_access_allowed(), introduce a new helper call_proc_get_link() that looks up and locks the task, does the access check, and calls ->proc_get_link().

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-64375 since 07/19/2026. The exploitation appears to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/25/2026).

Upgrading to version 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.4 or 7.2-rc1 eliminates this vulnerability. Applying the patch 6253dfee5afba536bb54fc6fe6c091c3758fafe1/65bf0d2b6e914f1448d6a2fde193dcf60936a651/de497d7aa2fae453a7e7c8f7d3e8682e565e3aaf/138c692d2b2d63d26f2eb957d0e4fcc5d61f9ff2/83b17872e3166c295c599279fc9562ac3840c638/497c6bae5167428596575f20af6613ff5671f383/dfd1894cb64cbd8758b461ed713800fe73db4f82/6255da28d4bb5349fe18e84cb043ccd394eba75d is able to eliminate this problem.

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: 8.8
VulDB Meta Temp Score: 8.4

VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Race condition
CWE: CWE-362
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

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.261/5.15.212/6.1.178/6.6.145/6.12.97/6.18.40/7.1.4/7.2-rc1
Patch: 6253dfee5afba536bb54fc6fe6c091c3758fafe1/65bf0d2b6e914f1448d6a2fde193dcf60936a651/de497d7aa2fae453a7e7c8f7d3e8682e565e3aaf/138c692d2b2d63d26f2eb957d0e4fcc5d61f9ff2/83b17872e3166c295c599279fc9562ac3840c638/497c6bae5167428596575f20af6613ff5671f383/dfd1894cb64cbd8758b461ed713800fe73db4f82/6255da28d4bb5349fe18e84cb043ccd394eba75d

Timelineinfo

07/19/2026 CVE reserved
07/25/2026 +6 days Advisory disclosed
07/25/2026 +0 days VulDB entry created
07/25/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-64375 (🔒)
GCVE (CVE): GCVE-0-2026-64375
GCVE (VulDB): GCVE-100-383173

Entryinfo

Created: 07/25/2026 17:58
Changes: 07/25/2026 17:58 (59)
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 ▸

Interested in the pricing of exploits?

See the underground prices here!