Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64371proc: protect ptrace_may_access() with exec_update_lock (part 1)

Description

In the Linux kernel, the following vulnerability has been resolved: proc: protect ptrace_may_access() with exec_update_lock (part 1) Fix the easy cases where procfs currently calls ptrace_may_access() without exec_update_lock protection, where the fix is to simply add the extra lock or use mm_access(): - do_task_stat(): grab exec_update_lock - proc_pid_wchan(): grab exec_update_lock - proc_map_files_lookup(): use mm_access() instead of get_task_mm() - proc_map_files_readdir(): use mm_access() instead of get_task_mm() - proc_ns_get_link(): grab exec_update_lock - proc_ns_readlink(): grab exec_update_lock

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64371, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected f83ce3e6b02d5e48b3a43b001390e2b58820389d – < ae1e630bcaac739f625822078edbaea98366930d
    • affected f83ce3e6b02d5e48b3a43b001390e2b58820389d – < d54f14655fd7d7b293698a8b6918563c4c0465e7
    • affected f83ce3e6b02d5e48b3a43b001390e2b58820389d – < bb43679356f1f2a4c6b1c88aec4f021e5b5c74e9
    • affected f83ce3e6b02d5e48b3a43b001390e2b58820389d – < 7456ae990a9738962b33146916fabca62ae3d4e0
    • affected f83ce3e6b02d5e48b3a43b001390e2b58820389d – < 4bfe8c481846cee52473a2f7d7b30ee8e6749fc4
    • affected f83ce3e6b02d5e48b3a43b001390e2b58820389d – < f9b4b03ccc9c69bf7f7298d4559906ebea7143b3
    • affected f83ce3e6b02d5e48b3a43b001390e2b58820389d – < c1cfd63326f5d09999134e9052c353faf738286e
    • affected f83ce3e6b02d5e48b3a43b001390e2b58820389d – < 6650527444dadc63d84aa939d14ecba4fadb2f69
    • affected 6b06d6282100dd5aacf7d45443d651a1995bd9c4
    • affected 334ed22054b2ec8477e4409e214fc139cf937ef6
    • affected 2.6.27.23 – < 2.6.28
    • affected 2.6.29.3 – < 2.6.30
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64371 badge
[![CVE-2026-64371](https://cveledger.app/badge/CVE-2026-64371.svg)](https://cveledger.app/cve/CVE-2026-64371)

Record last updated .