BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-72085High confidence

scsi: xen: scsiback: Free unsubmitted command instead of double-putting it

Linux · Linux

9.3CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.19% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.100-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.180-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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-72085 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: scsi: xen: scsiback: Free unsubmitted command instead of double-putting it
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 `scsi: xen: scsiback` component. This vulnerability allows a malicious virtualized SCSI (pvSCSI) guest to trigger a reference count underflow by sending specially crafted requests. This can lead to a denial of service, potentially stopping a Logical Unit Number (LUN) session or causing the host system to crash.
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.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

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-59043

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 actionPatch only the product branches with a verified fix

Critical technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: scsi: xen: scsiback: Free unsubmitted command instead of double-putting it scsiback_get_pend_req() obtains a command tag and returns a vscsibk_pend whose embedded se_cmd has only been memset to 0, so its cmd_kref is 0; the se_cmd is initialised (kref_init() via target_init_cmd()) only later, in scsiback_cmd_exec(), on the successful VSCSIIF_ACT_SCSI_CDB path. The two error paths in scsiback_do_cmd_fn() taken before the command is submitted -- a failed scsiback_gnttab_data_map() and an unknown ring_req.act -- call transport_generic_free_cmd(&pending_req->se_cmd, 0), which kref_put()s a refcount of 0. That underflows it ("refcount_t: underflow; use-after-free") and, as the release function is not run, leaks the command tag. Impact: a pvSCSI guest can leak every command tag of a LUN's session, stopping the LUN, by submitting requests with a bad grant reference or an unknown request type; under panic_on_warn the refcount underflow panics the host. Add a helper that just returns the tag with target_free_tag() and sends the error response. It frees the tag while the v2p reference still pins the session, and snapshots the response fields beforehand because freeing the tag can let another ring reuse the pending_req slot.

What

In the Linux kernel, the following vulnerability has been resolved: scsi: xen: scsiback: Free unsubmitted command instead of double-putting it scsiback_get_pend_req() obtains a command tag and returns a vscsibk_pend whose embedded se_cmd has only been memset to 0, so its cmd_kref is 0; the se_cmd is initialised (kref_init() via target_init_cmd()) only later, in scsiback_cmd_exec(), on the successful VSCSIIF_ACT_SCSI_CDB path. The two error paths in scsiback_do_cmd_fn() taken before the command is submitted -- a failed scsiback_gnttab_data_map() and an unknown ring_req.act -- call transport_generic_free_cmd(&pending_req->se_cmd, 0), which kref_put()s a refcount of 0. That underflows it ("refcount_t: underflow; use-after-free") and, as the release function is not run, leaks the command tag. Impact: a pvSCSI guest can leak every command tag of a LUN's session, stopping the LUN, by submitting requests with a bad grant reference or an unknown request type; under panic_on_warn the refcount underflow panics the host. Add a helper that just returns the tag with target_free_tag() and sends the error response. It frees the tag while the v2p reference still pins the session, and snapshots the response fields beforehand because freeing the tag can let another ring reuse the pending_req slot.

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 without authentication or user interaction. 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: scsi: xen: scsiback: Free unsubmitted command instead of double-putting it scsiback_get_pend_req() obtains a command tag and returns a vscsibk_pend whose embedded se_cmd has only been memset to 0, so its cmd_kref is 0; the se_cmd is initialised (kref_init() via target_init_cmd()) only later, in scsiback_cmd_exec(), on the successful VSCSIIF_ACT_SCSI_CDB path. The two error paths in scsiback_do_cmd_fn() taken before the command is submitted -- a failed scsiback_gnttab_data_map() and an unknown ring_req.act -- call transport_generic_free_cmd(&pending_req->se_cmd, 0), which kref_put()s a refcount of 0. That underflows it ("refcount_t: underflow; use-after-free") and, as the release function is not run, leaks the command tag. Impact: a pvSCSI guest can leak every command tag of a LUN's session, stopping the LUN, by submitting requests with a bad grant reference or an unknown request type; under panic_on_warn the refcount underflow panics the host. Add a helper that just returns the tag with target_free_tag() and sends the error response. It frees the tag while the v2p reference still pins the session, and snapshots the response fields beforehand because freeing the tag can let another ring reuse the pending_req slot.

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 without authentication or user interaction. 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
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different 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:N/UI:N/S:C/C:H/I:H/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.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.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.
Unauthenticated
A

Official authority intelligence

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

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

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

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260819Security Bulletin 19 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 19 Aug 2026, published on 19 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-72020 Référence CVE CVE-2026-72033 https://www.cve.org/CVERecord?id=CVE-2026-72033 Référence CVE CVE-2026-72041 https://www.cve.org/CVERecord?id=CVE-2026-72041 Référence CVE CVE-2026-72046 https://www.cve.org/CVERecord?id=CVE-2026-72046 Référence CVE CVE-2026-72064 https://www.cve.org/CVERecord?id=CVE-2026-72064 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-72083 https://www.cve.org/CVERecord?id=CVE-2026-72083 Référence CVE CVE-2026-72084 https://www.cve.org/CVERecord?id=CVE-2026-72084 Référence CVE CVE-2026-72085 https://www.cve.org/CVERecord?id=CVE-2026-72085 Référence CVE CVE-2026-72098 https://www.cve.org/CVERecord?id=CVE-2026-72098 Référence CVE CVE-2026-72129 https://www.cve.org/CVERecord?id=CVE-2026-72129 Référence CVE CVE-2026-72130 https://www.cve.org/CVERecord?id=CVE-2026-72130 Référence CVE CVE-2026-72137 https://www.cve.org/CVERecord?id=CVE-2026-72137 Référence CVE CVE-2026-72139 https://www.cve.org/CVERecord?id=CVE-2026-72139 Référence CVE CVE-2026-72191 https://www.cve.org/CVERecord?id=CVE-2026-72191 Référence CVE CVE-2026-72192 https://www.cve.org/CVERecord?id=CVE-2026-72192 Référence CVE CVE-2026-72194 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-72020 Référence CVE CVE-2026-72033 https://www.cve.org/CVERecord?id=CVE-2026-72033 Référence CVE CVE-2026-72041 https://www.cve.org/CVERecord?id=CVE-2026-72041 Référence CVE CVE-2026-72046 https://www.cve.org/CVERecord?id=CVE-2026-72046 Référence CVE CVE-2026-72064 https://www.cve.org/CVERecord?id=CVE-2026-72064 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-72083 https://www.cve.org/CVERecord?id=CVE-2026-72083 Référence CVE CVE-2026-72084 https://www.cve.org/CVERecord?id=CVE-2026-72084 Référence CVE CVE-2026-72085 https://www.cve.org/CVERecord?id=CVE-2026-72085 Référence CVE CVE-2026-72098 https://www.cve.org/CVERecord?id=CVE-2026-72098 Référence CVE CVE-2026-72129 https://www.cve.org/CVERecord?id=CVE-2026-72129 Référence CVE CVE-2026-72130 https://www.cve.org/CVERecord?id=CVE-2026-72130 Référence CVE CVE-2026-72137 https://www.cve.org/CVERecord?id=CVE-2026-72137 Référence CVE CVE-2026-72139 https://www.cve.org/CVERecord?id=CVE-2026-72139 Référence CVE CVE-2026-72191 https://www.cve.org/CVERecord?id=CVE-2026-72191 Référence CVE CVE-2026-72192 https://www.cve.org/CVERecord?id=CVE-2026-72192 Référence CVE CVE-2026-72194 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-72014 Référence CVE CVE-2026-72020 https://www.cve.org/CVERecord?id=CVE-2026-72020 Référence CVE CVE-2026-72033 https://www.cve.org/CVERecord?id=CVE-2026-72033 Référence CVE CVE-2026-72041 https://www.cve.org/CVERecord?id=CVE-2026-72041 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-72071 https://www.cve.org/CVERecord?id=CVE-2026-72071 Référence CVE CVE-2026-72083 https://www.cve.org/CVERecord?id=CVE-2026-72083 Référence CVE CVE-2026-72084 https://www.cve.org/CVERecord?id=CVE-2026-72084 Référence CVE CVE-2026-72085 https://www.cve.org/CVERecord?id=CVE-2026-72085 Référence CVE CVE-2026-72098 https://www.cve.org/CVERecord?id=CVE-2026-72098 Référence CVE CVE-2026-72111 https://www.cve.org/CVERecord?id=CVE-2026-72111 Référence CVE CVE-2026-72124 https://www.cve.org/CVERecord?id=CVE-2026-72124 Référence CVE CVE-2026-72125 https://www.cve.org/CVERecord?id=CVE-2026-72125 Référence CVE CVE-2026-72126 https://www.cve.org/CVERecord?id=CVE-2026-72126 Référence CVE CVE-2026-72129 https://www.cve.org/CVERecord?id=CVE-2026-72129 Référence CVE CVE-2026-72130 https://www.cve.org/CVERecord?id=CVE-2026-72130 Référence CVE CVE-2026-72191 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.
Fix availability varies by product
Affected
Linux: 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < 9c0f6894982b1f13bda220707497b25ac9c95bdb, 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < a13b789497a7fdd27d4d63f5c69d23db706ef0fe, 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < fa588f28401102652068c4cc75e135507f4b5106, 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < fcd64d4d97af5d9736f31040f8ed8cd4c17e4c45, 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < f1516c56ac540da1769f264c3cfefe4499548a5d, 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < 1e97c404e44991fb087c38ccd7414f2d326f9b74, 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < ca978f8a93d4d36841839bf2847d29b88c2591d6, 4.6
Fixed
Linux: < 4.6, 5.15.212 ≤ 5.15.*, 6.1.178 ≤ 6.1.*, 6.6.145 ≤ 6.6.*, 6.12.97 ≤ 6.12.*, 6.18.40 ≤ 6.18.*, 7.1.5 ≤ 7.1.*, 7.2 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
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 17 Aug 2026, 05:40 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
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-59043
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD received

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. Affected versionsThe structured affected or fixed version information changed.
    Before
    2dbcdf33dbf61f44b29adb52338282c3d7840d0e < 9c0f6894982b1f13bda220707497b25ac9c95bdb; 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < a13b789497a7fdd27d4d63f5c69d23db706ef0fe; 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < fa588f28401102652068c4cc75e135507f4b5106; 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < fcd64d4d97af5d9736f31040f8ed8cd4c17e4c45; 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < f1516c56ac540da1769f264c3cfefe4499548a5d; 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < 1e97c404e44991fb087c38ccd7414f2d326f9b74; 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < ca978f8a93d4d36841839bf2847d29b88c2591d6; 4.6 · Fixed: < 4.6; 5.15.212 ≤ 5.15.*; 6.1.178 ≤ 6.1.*; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2-rc4 ≤ *
    After
    2dbcdf33dbf61f44b29adb52338282c3d7840d0e < 9c0f6894982b1f13bda220707497b25ac9c95bdb; 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < a13b789497a7fdd27d4d63f5c69d23db706ef0fe; 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < fa588f28401102652068c4cc75e135507f4b5106; 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < fcd64d4d97af5d9736f31040f8ed8cd4c17e4c45; 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < f1516c56ac540da1769f264c3cfefe4499548a5d; 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < 1e97c404e44991fb087c38ccd7414f2d326f9b74; 2dbcdf33dbf61f44b29adb52338282c3d7840d0e < ca978f8a93d4d36841839bf2847d29b88c2591d6; 4.6 · Fixed: < 4.6; 5.15.212 ≤ 5.15.*; 6.1.178 ≤ 6.1.*; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  2. SeveritySeverity changed from Unknown to Critical.
    Before
    Unknown
    After
    Critical
    CNA ↗
  3. CVSS scoreCVSS score changed from not recorded to 9.3 (CVSS 3.1 · CNA · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).
    Before
    not recorded
    After
    9.3 (CVSS 3.1 · CNA · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H)
    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-59043↗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-72085 · cve.blacktree.nl