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

ipmi: fix refcount leak in i_ipmi_request()

Linux · Linux

…UnscoredAssess manually
Recommended action
Needs assessment

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence.

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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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-72040 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: ipmi: fix refcount leak in i_ipmi_request()
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's Intelligent Platform Management Interface (IPMI) subsystem. When a caller provides a message to the `i_ipmi_request()` function, a reference count is incremented. However, if an error occurs during this process, the reference count is not properly decremented, resulting in a permanent resource leak. This resource leak could allow a local attacker to cause a denial of service (DoS) condition on the system.
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-58998

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: ipmi: fix refcount leak in i_ipmi_request() When a caller provides a `supplied_recv` message to i_ipmi_request(), the function increments the user's `nr_msgs` reference count. If an error occurs later, the out_err cleanup path only frees the recv_msg if the function allocated it itself (i.e., !supplied_recv). In the supplied_recv case the cleanup is skipped, leaving the reference count elevated. The caller ipmi_request_supply_msgs() does not release the supplied_recv on error, so the reference is permanently leaked. Fix this by explicitly reverting the reference count operations when a supplied recv_msg with a valid user pointer is present in the error path: decrement nr_msgs and drop the user's kref.

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
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionNeeds assessment

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: ipmi: fix refcount leak in i_ipmi_request() When a caller provides a `supplied_recv` message to i_ipmi_request(), the function increments the user's `nr_msgs` reference count. If an error occurs later, the out_err cleanup path only frees the recv_msg if the function allocated it itself (i.e., !supplied_recv). In the supplied_recv case the cleanup is skipped, leaving the reference count elevated. The caller ipmi_request_supply_msgs() does not release the supplied_recv on error, so the reference is permanently leaked. Fix this by explicitly reverting the reference count operations when a supplied recv_msg with a valid user pointer is present in the error path: decrement nr_msgs and drop the user's kref.

What

In the Linux kernel, the following vulnerability has been resolved: ipmi: fix refcount leak in i_ipmi_request() When a caller provides a `supplied_recv` message to i_ipmi_request(), the function increments the user's `nr_msgs` reference count. If an error occurs later, the out_err cleanup path only frees the recv_msg if the function allocated it itself (i.e., !supplied_recv). In the supplied_recv case the cleanup is skipped, leaving the reference count elevated. The caller ipmi_request_supply_msgs() does not release the supplied_recv on error, so the reference is permanently leaked. Fix this by explicitly reverting the reference count operations when a supplied recv_msg with a valid user pointer is present in the error path: decrement nr_msgs and drop the user's kref.

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 the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may gain additional privileges.

What

In the Linux kernel, the following vulnerability has been resolved: ipmi: fix refcount leak in i_ipmi_request() When a caller provides a `supplied_recv` message to i_ipmi_request(), the function increments the user's `nr_msgs` reference count. If an error occurs later, the out_err cleanup path only frees the recv_msg if the function allocated it itself (i.e., !supplied_recv). In the supplied_recv case the cleanup is skipped, leaving the reference count elevated. The caller ipmi_request_supply_msgs() does not release the supplied_recv on error, so the reference is permanently leaked. Fix this by explicitly reverting the reference count operations when a supplied recv_msg with a valid user pointer is present in the error path: decrement nr_msgs and drop the user's kref.

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 the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may gain additional privileges.

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
the affected interface → vulnerable operation → gain additional privileges
Attack surface
Unspecified
Privileges required
Not stated in the selected CVSS metric
User interaction
Not stated in the selected CVSS metric
Attack complexity
Not stated in the selected CVSS metric
Security boundary
Not stated in the selected CVSS metric
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.
Not available from the selected scoring authority.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
Privilege escalation
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-58998Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: ipmi: fix refcount leak in i_ipmi_request() When a caller provides a `supplied_recv` message to i_ipmi_request(), the function increments the user's `nr_msgs` reference count. If an error occurs later, the out_err cleanup path only frees the recv_msg if the function allocated it itself (i.e., !supplied_recv). In the supplied_recv case the cleanup is skipped, leaving the reference count elevated. The caller ipmi_request_supply_msgs() does not release the supplied_recv on error, so the reference is permanently leaked. Fix this by explicitly reverting the reference count operations when a supplied recv_msg with a valid user pointer is present in the error path: decrement nr_msgs and drop the user's kref.

Official EUVD record
BSI · German · WID-SEC-W-2026-2852Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.

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

d?id=CVE-2026-68445 Référence CVE CVE-2026-68446 https://www.cve.org/CVERecord?id=CVE-2026-68446 Référence CVE CVE-2026-68449 https://www.cve.org/CVERecord?id=CVE-2026-68449 Référence CVE CVE-2026-68450 https://www.cve.org/CVERecord?id=CVE-2026-68450 Référence CVE CVE-2026-72015 https://www.cve.org/CVERecord?id=CVE-2026-72015 Référence CVE CVE-2026-72017 https://www.cve.org/CVERecord?id=CVE-2026-72017 Référence CVE CVE-2026-72023 https://www.cve.org/CVERecord?id=CVE-2026-72023 Référence CVE CVE-2026-72030 https://www.cve.org/CVERecord?id=CVE-2026-72030 Référence CVE CVE-2026-72032 https://www.cve.org/CVERecord?id=CVE-2026-72032 Référence CVE CVE-2026-72040 https://www.cve.org/CVERecord?id=CVE-2026-72040 Référence CVE CVE-2026-72045 https://www.cve.org/CVERecord?id=CVE-2026-72045 Référence CVE CVE-2026-72046 https://www.cve.org/CVERecord?id=CVE-2026-72046 Référence CVE CVE-2026-72051 https://www.cve.org/CVERecord?id=CVE-2026-72051 Référence CVE CVE-2026-72062 https://www.cve.org/CVERecord?id=CVE-2026-72062 Référence CVE CVE-2026-72065 https://www.cve.org/CVERecord?id=CVE-2026-72065 Référence CVE CVE-2026-72069 https://www.cve.org/CVERecord?id=CVE-2026-72069 Référence CVE CVE-2026-72070 https://www.cve.org/CVERecord?id=CVE-2026-72070 Référence CVE CVE-2026-72101 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
f63723ca7d7623f9dae1990973cd158671f03c56 < 122ca6b2af714e114c9b872a48372ace31a9ab1f; 348121b29594d42d1635648fd3ed31dfa25351d5 < 9409e18ffe7378d202efe1cf69989df9f67b0369; 53d6e403affbf6df2c859a0ea00ccfc1e72090ca < e2a3b77df6aef031455dd83ea8ed4344b7dca1f9; b52da4054ee0bf9ecb44996f2c83236ff50b3812 < f5c5065963024390ddad51bd455d1adc710de575; b52da4054ee0bf9ecb44996f2c83236ff50b3812 < 0fd23994ec8c5436d9f0b50848deb87ed933e6b3; b52da4054ee0bf9ecb44996f2c83236ff50b3812 < a3f3859cecacb64f18fd446271ece9a3b3f2d4de; 0ed73be9a2547ffb9b5c1d879ad9bfab73d920b5; 6.1.157 < 6.1.184
Fixed
< 6.18; 6.1.184 ≤ 6.1.*; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 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 15 Aug 2026 · Last source change 23 Aug 2026, 12:46 UTC · CWE not yet assigned

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

Missing structured fields: CVSS base score, 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.
    Before
    authoritative remediation link
    After
    authoritative remediation link
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    348121b29594d42d1635648fd3ed31dfa25351d5 < 9409e18ffe7378d202efe1cf69989df9f67b0369; 53d6e403affbf6df2c859a0ea00ccfc1e72090ca < e2a3b77df6aef031455dd83ea8ed4344b7dca1f9; b52da4054ee0bf9ecb44996f2c83236ff50b3812 < f5c5065963024390ddad51bd455d1adc710de575; b52da4054ee0bf9ecb44996f2c83236ff50b3812 < 0fd23994ec8c5436d9f0b50848deb87ed933e6b3; b52da4054ee0bf9ecb44996f2c83236ff50b3812 < a3f3859cecacb64f18fd446271ece9a3b3f2d4de; f63723ca7d7623f9dae1990973cd158671f03c56; 0ed73be9a2547ffb9b5c1d879ad9bfab73d920b5; 6.6.113 < 6.6.148 · Fixed: < 6.18; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2 ≤ *
    After
    f63723ca7d7623f9dae1990973cd158671f03c56 < 122ca6b2af714e114c9b872a48372ace31a9ab1f; 348121b29594d42d1635648fd3ed31dfa25351d5 < 9409e18ffe7378d202efe1cf69989df9f67b0369; 53d6e403affbf6df2c859a0ea00ccfc1e72090ca < e2a3b77df6aef031455dd83ea8ed4344b7dca1f9; b52da4054ee0bf9ecb44996f2c83236ff50b3812 < f5c5065963024390ddad51bd455d1adc710de575; b52da4054ee0bf9ecb44996f2c83236ff50b3812 < 0fd23994ec8c5436d9f0b50848deb87ed933e6b3; b52da4054ee0bf9ecb44996f2c83236ff50b3812 < a3f3859cecacb64f18fd446271ece9a3b3f2d4de; 0ed73be9a2547ffb9b5c1d879ad9bfab73d920b5; 6.1.157 < 6.1.184 · Fixed: < 6.18; 6.1.184 ≤ 6.1.*; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    348121b29594d42d1635648fd3ed31dfa25351d5 < 9409e18ffe7378d202efe1cf69989df9f67b0369; 53d6e403affbf6df2c859a0ea00ccfc1e72090ca < e2a3b77df6aef031455dd83ea8ed4344b7dca1f9; b52da4054ee0bf9ecb44996f2c83236ff50b3812 < f5c5065963024390ddad51bd455d1adc710de575; b52da4054ee0bf9ecb44996f2c83236ff50b3812 < 0fd23994ec8c5436d9f0b50848deb87ed933e6b3; b52da4054ee0bf9ecb44996f2c83236ff50b3812 < a3f3859cecacb64f18fd446271ece9a3b3f2d4de; f63723ca7d7623f9dae1990973cd158671f03c56; 0ed73be9a2547ffb9b5c1d879ad9bfab73d920b5; 6.6.113 < 6.6.148 · Fixed: < 6.18; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    348121b29594d42d1635648fd3ed31dfa25351d5 < 9409e18ffe7378d202efe1cf69989df9f67b0369; 53d6e403affbf6df2c859a0ea00ccfc1e72090ca < e2a3b77df6aef031455dd83ea8ed4344b7dca1f9; b52da4054ee0bf9ecb44996f2c83236ff50b3812 < f5c5065963024390ddad51bd455d1adc710de575; b52da4054ee0bf9ecb44996f2c83236ff50b3812 < 0fd23994ec8c5436d9f0b50848deb87ed933e6b3; b52da4054ee0bf9ecb44996f2c83236ff50b3812 < a3f3859cecacb64f18fd446271ece9a3b3f2d4de; f63723ca7d7623f9dae1990973cd158671f03c56; 0ed73be9a2547ffb9b5c1d879ad9bfab73d920b5; 6.6.113 < 6.6.148 · Fixed: < 6.18; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  4. Catalogue recordCVE added to the BlackTree catalogue.
    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-58998↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor 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-72040 · cve.blacktree.nl