CVE-2026-64253: kernel/fork: clear PF_BLOCK_TS in copy_process()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 77bba61a20f1b3d206f4f90e10a7bb3cd90b9619, 99e6c712cc300883b8cbf03347d5359ec1a4d6dd, ee0801aceabdf583392477baf69a290b09448b8f.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 77bba61a20f1b3d206f4f90e10a7bb3cd90b9619, 99e6c712cc300883b8cbf03347d5359ec1a4d6dd, ee0801aceabdf583392477baf69a290b09448b8f or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 24, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.9 and later · before 6.12.95
- linux linux kernel6.13 and later · before 6.18.38
- linux linux kernel6.19 and later · before 7.1.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.9affected
- 06b23f92af87a84d70881b2ecaa72e00f7838264 and later · before ee0801aceabdf583392477baf69a290b09448b8faffected · git
- 06b23f92af87a84d70881b2ecaa72e00f7838264 and later · before 99e6c712cc300883b8cbf03347d5359ec1a4d6ddaffected · git
- 06b23f92af87a84d70881b2ecaa72e00f7838264 and later · before 77bba61a20f1b3d206f4f90e10a7bb3cd90b9619affected · git
- 06b23f92af87a84d70881b2ecaa72e00f7838264 and later · before fd38b75c4b43295b10d69772a46d1c74dbd6fc81affected · git
- before 6.9not affected · semver
- 6.12.95 and later · up to and including 6.12.*not affected · semver
- 6.18.38 and later · up to and including 6.18.*not affected · semver
- 7.1.3 and later · up to and including 7.1.*not affected · semver
- 7.2 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.95-1 | 6.12.95-1 |
| Debian:14 | linux | before 7.1.3-1 | 7.1.3-1 |
| openSUSE:Tumbleweed | kernel-source | before 7.1.7-1.1 | 7.1.7-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-64251Jul 24, 2026 · pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next()31Monitor
- ← EarlierCVE-2026-64252Jul 24, 2026 · MIPS: DEC: Prevent initial console buffer from landing in XKPHYS22Monitor
- Later →CVE-2026-64254Jul 24, 2026 · NTB: epf: Avoid pci_iounmap() with offset when PEER_SPAD and CONFIG share BAR22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 77bba61a20f1b3d206f4f90e10a7bb3cd90b9619 | Vendor (CNA) |
| Linux Linux | 99e6c712cc300883b8cbf03347d5359ec1a4d6dd | Vendor (CNA) |
| Linux Linux | ee0801aceabdf583392477baf69a290b09448b8f | Vendor (CNA) |
| Linux Linux | fd38b75c4b43295b10d69772a46d1c74dbd6fc81 | Vendor (CNA) |
| debian:linux | 6.12.95-1 · Debian:13 | Package registry (OSV) |
| opensuse:kernel-source | 7.1.7-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0636 · Jul 27, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.