Linux Kernel up to 6.12.94/6.18.37/7.1.2 fork copy_process null pointer dereference

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-$5k1.66-

Summaryinfo

A vulnerability classified as very critical has been found in Linux Kernel up to 6.12.94/6.18.37/7.1.2. Affected is the function copy_process of the component fork. The manipulation leads to null pointer dereference. This vulnerability is uniquely identified as CVE-2026-64253. Local access is required to approach this attack. No exploit exists.

Detailsinfo

A vulnerability, which was classified as very critical, has been found in Linux Kernel up to 6.12.94/6.18.37/7.1.2. This issue affects the function copy_process of the component fork. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: kernel/fork: clear PF_BLOCK_TS in copy_process() PF_BLOCK_TS is only set in blk_time_get_ns() when current->plug is non-NULL, and blk_finish_plug() clears it via __blk_flush_plug() before NULLing the plug pointer. copy_process() breaks the invariant by inheriting PF_BLOCK_TS from the parent while resetting the child's plug to NULL. Clear PF_BLOCK_TS alongside that assignment so callers can rely on "PF_BLOCK_TS set implies current->plug != NULL" and dereference current->plug unguarded.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-64253 since 07/19/2026. The exploitation is known 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/24/2026).

Upgrading to version 6.12.95, 6.18.38, 7.1.3 or 7.2-rc1 eliminates this vulnerability. Applying the patch ee0801aceabdf583392477baf69a290b09448b8f/99e6c712cc300883b8cbf03347d5359ec1a4d6dd/77bba61a20f1b3d206f4f90e10a7bb3cd90b9619/fd38b75c4b43295b10d69772a46d1c74dbd6fc81 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: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

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 6.12.95/6.18.38/7.1.3/7.2-rc1
Patch: ee0801aceabdf583392477baf69a290b09448b8f/99e6c712cc300883b8cbf03347d5359ec1a4d6dd/77bba61a20f1b3d206f4f90e10a7bb3cd90b9619/fd38b75c4b43295b10d69772a46d1c74dbd6fc81

Timelineinfo

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

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-64253 (🔒)
GCVE (CVE): GCVE-0-2026-64253
GCVE (VulDB): GCVE-100-382997

Entryinfo

Created: 07/24/2026 19:36
Changes: 07/24/2026 19:36 (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.

Want to know what is going to be exploited?

We predict KEV entries!