Skip to content
Noroxi
CVE-2026-64375· NVD / CVE Program· CNA Linux

proc: protect ptrace_may_access() with exec_update_lock (FD links)

Noroxi assessment

Priority: Monitor (action score 31/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.10% (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 138c692d2b2d63d26f2eb957d0e4fcc5d61f9ff2, 497c6bae5167428596575f20af6613ff5671f383, 6253dfee5afba536bb54fc6fe6c091c3758fafe1; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1.

Low priority for now. Upgrade to Linux Linux 138c692d2b2d63d26f2eb957d0e4fcc5d61f9ff2, 497c6bae5167428596575f20af6613ff5671f383, 6253dfee5afba536bb54fc6fe6c091c3758fafe1; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1 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: 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().

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jul 25, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 0th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Follow CVE-2026-64375

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.18 and later · before 5.10.261
  • linux linux kernel5.11 and later · before 5.15.212
  • linux linux kernel5.16 and later · before 6.1.178
  • linux linux kernel6.2 and later · before 6.6.145
  • linux linux kernel6.7 and later · before 6.12.97
  • linux linux kernel6.13 and later · before 6.18.40
  • linux linux kernel6.19 and later · before 7.1.4

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

    • 2.6.18affected
    • 778c1144771f0064b6f51bee865cceb0d996f2f9 and later · before 6253dfee5afba536bb54fc6fe6c091c3758fafe1affected · git
    • 778c1144771f0064b6f51bee865cceb0d996f2f9 and later · before 65bf0d2b6e914f1448d6a2fde193dcf60936a651affected · git
    • 778c1144771f0064b6f51bee865cceb0d996f2f9 and later · before de497d7aa2fae453a7e7c8f7d3e8682e565e3aafaffected · git
    • 778c1144771f0064b6f51bee865cceb0d996f2f9 and later · before 138c692d2b2d63d26f2eb957d0e4fcc5d61f9ff2affected · git
    • 778c1144771f0064b6f51bee865cceb0d996f2f9 and later · before 83b17872e3166c295c599279fc9562ac3840c638affected · git
    • 778c1144771f0064b6f51bee865cceb0d996f2f9 and later · before 497c6bae5167428596575f20af6613ff5671f383affected · git
    • 778c1144771f0064b6f51bee865cceb0d996f2f9 and later · before dfd1894cb64cbd8758b461ed713800fe73db4f82affected · git
    • 778c1144771f0064b6f51bee865cceb0d996f2f9 and later · before 6255da28d4bb5349fe18e84cb043ccd394eba75daffected · git
    • before 2.6.18not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:12linux-6.12before 6.12.100-1~deb12u16.12.100-1~deb12u1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.4-17.1.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-64372Jul 25, 2026 · cpufreq: pcc: fix use-after-free and double free in _OSC evaluation
    31Monitor
  • ← EarlierCVE-2026-64374Jul 25, 2026 · sched/rt: Have RT_PUSH_IPI be default off for non PREEMPT_RT
    30Monitor
  • Later →CVE-2026-64377Jul 25, 2026 · cpufreq: qcom-cpufreq-hw: Fix possible double free
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux138c692d2b2d63d26f2eb957d0e4fcc5d61f9ff2Vendor (CNA)
Linux Linux497c6bae5167428596575f20af6613ff5671f383Vendor (CNA)
Linux Linux6253dfee5afba536bb54fc6fe6c091c3758fafe1Vendor (CNA)
Linux Linux6255da28d4bb5349fe18e84cb043ccd394eba75dVendor (CNA)
Linux Linux65bf0d2b6e914f1448d6a2fde193dcf60936a651Vendor (CNA)
Linux Linux83b17872e3166c295c599279fc9562ac3840c638Vendor (CNA)
Linux Linuxde497d7aa2fae453a7e7c8f7d3e8682e565e3aafVendor (CNA)
Linux Linuxdfd1894cb64cbd8758b461ed713800fe73db4f82Vendor (CNA)
azl3 kernel 6.6.144.1-1 on Azure Linux 3.06.6.145.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package 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.

EPSS, last 120 days

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 researchers

Finders, 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).

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records