BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-64419High confidence

mm/shrinker: do not hold RCU lock in shrinker_debugfs_count_show()

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

20 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-64419 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: mm/shrinker: do not hold RCU lock in shrinker_debugfs_count_show()
274 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel. A local user could trigger a system crash by reading a specific debugfs "count" file related to memory management. This issue arises because a function attempts to perform an operation that can cause it to pause (sleep) while holding a critical system lock, which is an invalid operation. This vulnerability could lead to a denial of service, making the system unavailable.
Remediation
No remediation text is recorded.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-48963

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: mm/shrinker: do not hold RCU lock in shrinker_debugfs_count_show() Reading the debugfs "count" file of a memcg-aware shrinker can sleep inside an RCU read-side critical section: BUG: sleeping function called from invalid context at kernel/cgroup/rstat.c:421 RCU nest depth: 1, expected: 0 css_rstat_flush mem_cgroup_flush_stats zswap_shrinker_count shrinker_debugfs_count_show shrinker_debugfs_count_show() invokes the ->count_objects() callback under rcu_read_lock(). The zswap callback flushes memcg stats via css_rstat_flush(), which may sleep, so it must not run under RCU. The RCU lock is not needed here. mem_cgroup_iter() takes RCU internally and returns a memcg holding a css reference (dropped on the next iteration or by mem_cgroup_iter_break()), so the memcg stays alive without it. The shrinker is kept alive by the open debugfs file: shrinker_free() removes the debugfs entries via debugfs_remove_recursive(), which waits for in-flight readers to drain, before call_rcu(..., shrinker_free_rcu_cb). The sibling "scan" handler already invokes the sleeping ->scan_objects() callback with no RCU section. Drop the rcu_read_lock()/rcu_read_unlock().

What

In the Linux kernel, the following vulnerability has been resolved: mm/shrinker: do not hold RCU lock in shrinker_debugfs_count_show() Reading the debugfs "count" file of a memcg-aware shrinker can sleep inside an RCU read-side critical section: BUG: sleeping function called from invalid context at kernel/cgroup/rstat.c:421 RCU nest depth: 1, expected: 0 css_rstat_flush mem_cgroup_flush_stats zswap_shrinker_count shrinker_debugfs_count_show shrinker_debugfs_count_show() invokes the ->count_objects() callback under rcu_read_lock(). The zswap callback flushes memcg stats via css_rstat_flush(), which may sleep, so it must not run under RCU. The RCU lock is not needed here. mem_cgroup_iter() takes RCU internally and returns a memcg holding a css reference (dropped on the next iteration or by mem_cgroup_iter_break()), so the memcg stays alive without it. The shrinker is kept alive by the open debugfs file: shrinker_free() removes the debugfs entries via debugfs_remove_recursive(), which waits for in-flight readers to drain, before call_rcu(..., shrinker_free_rcu_cb). The sibling "scan" handler already invokes the sleeping ->scan_objects() callback with no RCU section. Drop the rcu_read_lock()/rcu_read_unlock().

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: mm/shrinker: do not hold RCU lock in shrinker_debugfs_count_show() Reading the debugfs "count" file of a memcg-aware shrinker can sleep inside an RCU read-side critical section: BUG: sleeping function called from invalid context at kernel/cgroup/rstat.c:421 RCU nest depth: 1, expected: 0 css_rstat_flush mem_cgroup_flush_stats zswap_shrinker_count shrinker_debugfs_count_show shrinker_debugfs_count_show() invokes the ->count_objects() callback under rcu_read_lock(). The zswap callback flushes memcg stats via css_rstat_flush(), which may sleep, so it must not run under RCU. The RCU lock is not needed here. mem_cgroup_iter() takes RCU internally and returns a memcg holding a css reference (dropped on the next iteration or by mem_cgroup_iter_break()), so the memcg stays alive without it. The shrinker is kept alive by the open debugfs file: shrinker_free() removes the debugfs entries via debugfs_remove_recursive(), which waits for in-flight readers to drain, before call_rcu(..., shrinker_free_rcu_cb). The sibling "scan" handler already invokes the sleeping ->scan_objects() callback with no RCU section. Drop the rcu_read_lock()/rcu_read_unlock().

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-W-2026-2527Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.

Official advisory
CERT-FR · French · CERTFR-2026-AVI-1031Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-64409 Référence CVE CVE-2026-64411 https://www.cve.org/CVERecord?id=CVE-2026-64411 Référence CVE CVE-2026-64412 https://www.cve.org/CVERecord?id=CVE-2026-64412 Référence CVE CVE-2026-64413 https://www.cve.org/CVERecord?id=CVE-2026-64413 Référence CVE CVE-2026-64414 https://www.cve.org/CVERecord?id=CVE-2026-64414 Référence CVE CVE-2026-64415 https://www.cve.org/CVERecord?id=CVE-2026-64415 Référence CVE CVE-2026-64416 https://www.cve.org/CVERecord?id=CVE-2026-64416 Référence CVE CVE-2026-64417 https://www.cve.org/CVERecord?id=CVE-2026-64417 Référence CVE CVE-2026-64418 https://www.cve.org/CVERecord?id=CVE-2026-64418 Référence CVE CVE-2026-64419 https://www.cve.org/CVERecord?id=CVE-2026-64419 Référence CVE CVE-2026-64420 https://www.cve.org/CVERecord?id=CVE-2026-64420 Référence CVE CVE-2026-64421 https://www.cve.org/CVERecord?id=CVE-2026-64421 Référence CVE CVE-2026-64422 https://www.cve.org/CVERecord?id=CVE-2026-64422 Référence CVE CVE-2026-64423 https://www.cve.org/CVERecord?id=CVE-2026-64423 Référence CVE CVE-2026-64424 https://www.cve.org/CVERecord?id=CVE-2026-64424 Référence CVE CVE-2026-64425 https://www.cve.org/CVERecord?id=CVE-2026-64425 Référence CVE CVE-2026-64428 https://www.cve.org/CVERecord?id=CVE-2026-64428 Référence CVE CVE-2026-64429 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0982Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-64401 Référence CVE CVE-2026-64403 https://www.cve.org/CVERecord?id=CVE-2026-64403 Référence CVE CVE-2026-64406 https://www.cve.org/CVERecord?id=CVE-2026-64406 Référence CVE CVE-2026-64408 https://www.cve.org/CVERecord?id=CVE-2026-64408 Référence CVE CVE-2026-64409 https://www.cve.org/CVERecord?id=CVE-2026-64409 Référence CVE CVE-2026-64411 https://www.cve.org/CVERecord?id=CVE-2026-64411 Référence CVE CVE-2026-64412 https://www.cve.org/CVERecord?id=CVE-2026-64412 Référence CVE CVE-2026-64413 https://www.cve.org/CVERecord?id=CVE-2026-64413 Référence CVE CVE-2026-64417 https://www.cve.org/CVERecord?id=CVE-2026-64417 Référence CVE CVE-2026-64419 https://www.cve.org/CVERecord?id=CVE-2026-64419 Référence CVE CVE-2026-64420 https://www.cve.org/CVERecord?id=CVE-2026-64420 Référence CVE CVE-2026-64422 https://www.cve.org/CVERecord?id=CVE-2026-64422 Référence CVE CVE-2026-64423 https://www.cve.org/CVERecord?id=CVE-2026-64423 Référence CVE CVE-2026-64425 https://www.cve.org/CVERecord?id=CVE-2026-64425 Référence CVE CVE-2026-64428 https://www.cve.org/CVERecord?id=CVE-2026-64428 Référence CVE CVE-2026-64429 https://www.cve.org/CVERecord?id=CVE-2026-64429 Référence CVE CVE-2026-64430 https://www.cve.org/CVERecord?id=CVE-2026-64430 Référence CVE CVE-2026-64432 https://www.cve.org/CVERecord?id=

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
5035ebc644aec92d55d1bbfe042f35341e4bffb5 < de5f69b8dae8698ac5e48dfcd30017887cdf4e5a; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 < e441cbfbd0eaa6404278e985033c33caba4db767; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 < 2fed79f0fe8c8d28a972c290dbfd693c3546c8c4; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 < 560e21e8ccff813e84d05f6500907c549a3d6985; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 < 86237e56091e70f09c0fbf217f9d9c0e08f556c4; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 < b902890c62d200b3509cb5e09cf1e0a66553c128; 6.0
Fixed
< 6.0; 6.1.178 ≤ 6.1.*; 6.6.145 ≤ 6.6.*; 6.12.96 ≤ 6.12.*; 6.18.39 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 25 Jul 2026 · Last source change 17 Aug 2026, 04:55 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-48963
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates →
  1. Vendor guidanceAuthoritative vendor guidance changed from authoritative remediation link to authoritative remediation link · patch.
    Before
    authoritative remediation link
    After
    authoritative remediation link · patch
    416baaa9-dc9f-4396-8d5f-8c081fb06d67 ↗
  2. SeveritySeverity changed from Unknown to Medium.
    Before
    Unknown
    After
    Medium
    NIST NVD ↗
  3. CVSS scoreCVSS score changed from not recorded to 5.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
    Before
    not recorded
    After
    5.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
    NIST NVD ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    5035ebc644aec92d55d1bbfe042f35341e4bffb5 < de5f69b8dae8698ac5e48dfcd30017887cdf4e5a; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 < e441cbfbd0eaa6404278e985033c33caba4db767; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 < 2fed79f0fe8c8d28a972c290dbfd693c3546c8c4; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 < 560e21e8ccff813e84d05f6500907c549a3d6985; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 < 86237e56091e70f09c0fbf217f9d9c0e08f556c4; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 < b902890c62d200b3509cb5e09cf1e0a66553c128; 6.0 · Fixed: < 6.0; 6.1.178 ≤ 6.1.*; 6.6.145 ≤ 6.6.*; 6.12.96 ≤ 6.12.*; 6.18.39 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    5035ebc644aec92d55d1bbfe042f35341e4bffb5 < de5f69b8dae8698ac5e48dfcd30017887cdf4e5a; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 < e441cbfbd0eaa6404278e985033c33caba4db767; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 < 2fed79f0fe8c8d28a972c290dbfd693c3546c8c4; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 < 560e21e8ccff813e84d05f6500907c549a3d6985; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 < 86237e56091e70f09c0fbf217f9d9c0e08f556c4; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 < b902890c62d200b3509cb5e09cf1e0a66553c128; 6.0 · Fixed: < 6.0; 6.1.178 ≤ 6.1.*; 6.6.145 ≤ 6.6.*; 6.12.96 ≤ 6.12.*; 6.18.39 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-48963↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-64419 · cve.blacktree.nl