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

xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN

Linux · Linux

7.1HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 197 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 severityHighOperational priority:Medium, lowered one band.downgradedsince 26 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.17% 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: As exposure requiresRemediation target: Within 365 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 197 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.

18 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 13 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.105-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.107-1~deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.10-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.10-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, 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-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-azure-fde-6.14Affected, 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-nvidia-6.14Affected, 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-gcp-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-hwe-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-lowlatency-hwe-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-nvidia-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-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-oracle-6.14Affected, 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
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.

2 current
CVE-2026-80530 · CSAF 2.0 · revision 9 · interimSUSE Product Security TeamCVE-2026-80530
31 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.1
  • kernel-default as component of SUSE Linux Enterprise Server 16.0
  • kernel-devel as component of SUSE Linux Enterprise Server 16.0
  • kernel-macros as component of SUSE Linux Enterprise Server 16.0
  • kernel-source as component of SUSE Linux Enterprise Server 16.0
  • kernel-source-vanilla as component of SUSE Linux Enterprise Server 16.0
  • kernel-default as component of SUSE Linux Enterprise Server 16.1
  • kernel-devel as component of SUSE Linux Enterprise Server 16.1
  • kernel-macros as component of SUSE Linux Enterprise Server 16.1
Summary
In the Linux kernel, the following vulnerability has been resolved: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN When exchanging two full-file ranges, xmi_can_exchange_reflink_flags() can move the reflink inode flag from the file that currently has it to the other file, as long as exactly one side is marked. This assumes that the file contents, and therefore all shared extents, are exchanged. That assumption is not true when XFS_EXCHMAPS_INO1_WRITTEN is set. xfs_exchmaps_can_skip_mapping() can skip hole and unwritten mappings from file1, so an exchange can complete without moving every mapping that the earlier flag-swap decision accounted for. In that case the post-operation cleanup can clear the reflink flag from an inode that still owns shared written extents. Later writes then take the non-reflink write path and may update blocks that should still have been protected by CoW, which shows up as data corruption between reflink-related files. Fix this by disabling the reflink flag exchange whenever XFS_EXCHMAPS_INO1_WRITTEN is requested. The contents exchange can still proceed; the conservative outcome is that both inodes keep the reflink flag. The regular reflink flag cleanup path can drop the extra flag later once the inode no longer has shared extents.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-80530 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN
184 known affected

The vendor explicitly identifies these products as 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 XFS filesystem. When performing file range exchanges with the XFS_EXCHMAPS_INO1_WRITTEN flag set, the reflink flag can be prematurely cleared from an inode that still manages shared written data. This can lead to data corruption between files that share data through the reflink mechanism, as subsequent writes may bypass Copy-on-Write (CoW) protection.
Remediation
To mitigate this issue, prevent module xfs from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically.
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-66445

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN When exchanging two full-file ranges, xmi_can_exchange_reflink_flags() can move the reflink inode flag from the file that currently has it to the other file, as long as exactly one side is marked. This assumes that the file contents, and therefore all shared extents, are exchanged. That assumption is not true when XFS_EXCHMAPS_INO1_WRITTEN is set. xfs_exchmaps_can_skip_mapping() can skip hole and unwritten mappings from file1, so an exchange can complete without moving every mapping that the earlier flag-swap decision accounted for. In that case the post-operation cleanup can clear the reflink flag from an inode that still owns shared written extents. Later writes then take the non-reflink write path and may update blocks that should still have been protected by CoW, which shows up as data corruption between reflink-related files. Fix this by disabling the reflink flag exchange whenever XFS_EXCHMAPS_INO1_WRITTEN is requested. The contents exchange can still proceed; the conservative outcome is that both inodes keep the reflink flag. The regular reflink flag cleanup path can drop the extra flag later once the inode no longer has shared extents.

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
7.1 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 197 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: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN When exchanging two full-file ranges, xmi_can_exchange_reflink_flags() can move the reflink inode flag from the file that currently has it to the other file, as long as exactly one side is marked. This assumes that the file contents, and therefore all shared extents, are exchanged. That assumption is not true when XFS_EXCHMAPS_INO1_WRITTEN is set. xfs_exchmaps_can_skip_mapping() can skip hole and unwritten mappings from file1, so an exchange can complete without moving every mapping that the earlier flag-swap decision accounted for. In that case the post-operation cleanup can clear the reflink flag from an inode that still owns shared written extents. Later writes then take the non-reflink write path and may update blocks that should still have been protected by CoW, which shows up as data corruption between reflink-related files. Fix this by disabling the reflink flag exchange whenever XFS_EXCHMAPS_INO1_WRITTEN is requested. The contents exchange can still proceed; the conservative outcome is that both inodes keep the reflink flag. The regular reflink flag cleanup path can drop the extra flag later once the inode no longer has shared extents.

What

In the Linux kernel, the following vulnerability has been resolved: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN When exchanging two full-file ranges, xmi_can_exchange_reflink_flags() can move the reflink inode flag from the file that currently has it to the other file, as long as exactly one side is marked. This assumes that the file contents, and therefore all shared extents, are exchanged. That assumption is not true when XFS_EXCHMAPS_INO1_WRITTEN is set. xfs_exchmaps_can_skip_mapping() can skip hole and unwritten mappings from file1, so an exchange can complete without moving every mapping that the earlier flag-swap decision accounted for. In that case the post-operation cleanup can clear the reflink flag from an inode that still owns shared written extents. Later writes then take the non-reflink write path and may update blocks that should still have been protected by CoW, which shows up as data corruption between reflink-related files. Fix this by disabling the reflink flag exchange whenever XFS_EXCHMAPS_INO1_WRITTEN is requested. The contents exchange can still proceed; the conservative outcome is that both inodes keep the reflink flag. The regular reflink flag cleanup path can drop the extra flag later once the inode no longer has shared extents.

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: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN When exchanging two full-file ranges, xmi_can_exchange_reflink_flags() can move the reflink inode flag from the file that currently has it to the other file, as long as exactly one side is marked. This assumes that the file contents, and therefore all shared extents, are exchanged. That assumption is not true when XFS_EXCHMAPS_INO1_WRITTEN is set. xfs_exchmaps_can_skip_mapping() can skip hole and unwritten mappings from file1, so an exchange can complete without moving every mapping that the earlier flag-swap decision accounted for. In that case the post-operation cleanup can clear the reflink flag from an inode that still owns shared written extents. Later writes then take the non-reflink write path and may update blocks that should still have been protected by CoW, which shows up as data corruption between reflink-related files. Fix this by disabling the reflink flag exchange whenever XFS_EXCHMAPS_INO1_WRITTEN is requested. The contents exchange can still proceed; the conservative outcome is that both inodes keep the reflink flag. The regular reflink flag cleanup path can drop the extra flag later once the inode no longer has shared extents.

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:H/I:H/A:N

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.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
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.

ENISA EUVD · EUVD-2026-66445Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN When exchanging two full-file ranges, xmi_can_exchange_reflink_flags() can move the reflink inode flag from the file that currently has it to the other file, as long as exactly one side is marked. This assumes that the file contents, and therefore all shared extents, are exchanged. That assumption is not true when XFS_EXCHMAPS_INO1_WRITTEN is set. xfs_exchmaps_can_skip_mapping() can skip hole and unwritten mappings from file1, so an exchange can complete without moving every mapping that the earlier flag-swap decision accounted for. In that case the post-operation cleanup can clear the reflink flag from an inode that still owns shared written extents. Later writes then take the non-reflink write path and may update blocks that should still have been protected by CoW, which shows up as data corruption between reflink-related files. Fix this by disabling the reflink flag exchange whenever XFS_EXCHMAPS_INO1_WRITTEN is requested. The contents exchange can still proceed; the conservative outcome is that both inodes keep the reflink flag. The regular reflink flag cleanup path can drop the extra flag later once the inode no longer has shared extents.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3042Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Ausführung von beliebigem Code, die Ausweitung von Berechtigungen, die Offenlegung von Informationen, die Manipulation von Daten oder Denial-of-Service-Zustände.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260902Security Bulletin 2 Sept 2026

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

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1255Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-74717 Référence CVE CVE-2026-74719 https://www.cve.org/CVERecord?id=CVE-2026-74719 Référence CVE CVE-2026-74722 https://www.cve.org/CVERecord?id=CVE-2026-74722 Référence CVE CVE-2026-74723 https://www.cve.org/CVERecord?id=CVE-2026-74723 Référence CVE CVE-2026-74730 https://www.cve.org/CVERecord?id=CVE-2026-74730 Référence CVE CVE-2026-74737 https://www.cve.org/CVERecord?id=CVE-2026-74737 Référence CVE CVE-2026-74743 https://www.cve.org/CVERecord?id=CVE-2026-74743 Référence CVE CVE-2026-74744 https://www.cve.org/CVERecord?id=CVE-2026-74744 Référence CVE CVE-2026-80529 https://www.cve.org/CVERecord?id=CVE-2026-80529 Référence CVE CVE-2026-80530 https://www.cve.org/CVERecord?id=CVE-2026-80530 Référence CVE CVE-2026-80531 https://www.cve.org/CVERecord?id=CVE-2026-80531 Référence CVE CVE-2026-80533 https://www.cve.org/CVERecord?id=CVE-2026-80533 Référence CVE CVE-2026-80534 https://www.cve.org/CVERecord?id=CVE-2026-80534 Référence CVE CVE-2026-80535 https://www.cve.org/CVERecord?id=CVE-2026-80535 Référence CVE CVE-2026-80557 https://www.cve.org/CVERecord?id=CVE-2026-80557 Référence CVE CVE-2026-80558 https://www.cve.org/CVERecord?id=CVE-2026-80558 Référence CVE CVE-2026-80561 https://www.cve.org/CVERecord?id=CVE-2026-80561 Référence CVE CVE-2026-80586 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-74744 Référence CVE CVE-2026-74746 https://www.cve.org/CVERecord?id=CVE-2026-74746 Référence CVE CVE-2026-74748 https://www.cve.org/CVERecord?id=CVE-2026-74748 Référence CVE CVE-2026-80522 https://www.cve.org/CVERecord?id=CVE-2026-80522 Référence CVE CVE-2026-80525 https://www.cve.org/CVERecord?id=CVE-2026-80525 Référence CVE CVE-2026-80526 https://www.cve.org/CVERecord?id=CVE-2026-80526 Référence CVE CVE-2026-80527 https://www.cve.org/CVERecord?id=CVE-2026-80527 Référence CVE CVE-2026-80528 https://www.cve.org/CVERecord?id=CVE-2026-80528 Référence CVE CVE-2026-80529 https://www.cve.org/CVERecord?id=CVE-2026-80529 Référence CVE CVE-2026-80530 https://www.cve.org/CVERecord?id=CVE-2026-80530 Référence CVE CVE-2026-80531 https://www.cve.org/CVERecord?id=CVE-2026-80531 Référence CVE CVE-2026-80532 https://www.cve.org/CVERecord?id=CVE-2026-80532 Référence CVE CVE-2026-80533 https://www.cve.org/CVERecord?id=CVE-2026-80533 Référence CVE CVE-2026-80534 https://www.cve.org/CVERecord?id=CVE-2026-80534 Référence CVE CVE-2026-80535 https://www.cve.org/CVERecord?id=CVE-2026-80535 Référence CVE CVE-2026-80536 https://www.cve.org/CVERecord?id=CVE-2026-80536 Référence CVE CVE-2026-80539 https://www.cve.org/CVERecord?id=CVE-2026-80539 Référence CVE CVE-2026-80540 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
Fixed
Linux: < 6.10, 6.12.105 ≤ 6.12.*, 6.18.46 ≤ 6.18.*, 7.1.10 ≤ 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 26 Aug 2026 · Last source change 3 Sept 2026, 15:07 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-27
European sourceENISA EUVD · EUVD-2026-66445
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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
    bpftool as a component of Red Hat Enterprise Linux 9; kernel as a component of Red Hat Enterprise Linux 9; kernel-64k as a component of Red Hat Enterprise Linux 9; kernel-64k-core as a component of Red Hat Enterprise Linux 9; kernel-64k-debug as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-core as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-64k-devel as a component of Red Hat Enterprise Linux 9; kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-64k-modules as a component of Red Hat Enterprise Linux 9; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 9; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-64k-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-64k-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 9; kernel-core as a component of Red Hat Enterprise Linux 9; kernel-cross-headers as a component of Red Hat Enterprise Linux 9; kernel-debug as a component of Red Hat Enterprise Linux 9; kernel-debug-core as a component of Red Hat Enterprise Linux 9; kernel-debug-devel as a component of Red Hat Enterprise Linux 9; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-debug-modules as a component of Red Hat Enterprise Linux 9; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 9; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 9; and 78 more
    After
    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; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 154 more
    Red Hat Product Security ↗
  2. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-80530 to remediation: access.redhat.com/CVE-2026-80530.
    Before
    remediation: access.redhat.com/CVE-2026-80530
    After
    remediation: access.redhat.com/CVE-2026-80530
    Red Hat Product Security ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    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; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 154 more
    After
    bpftool as a component of Red Hat Enterprise Linux 9; kernel as a component of Red Hat Enterprise Linux 9; kernel-64k as a component of Red Hat Enterprise Linux 9; kernel-64k-core as a component of Red Hat Enterprise Linux 9; kernel-64k-debug as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-core as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-64k-devel as a component of Red Hat Enterprise Linux 9; kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-64k-modules as a component of Red Hat Enterprise Linux 9; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 9; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-64k-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-64k-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 9; kernel-core as a component of Red Hat Enterprise Linux 9; kernel-cross-headers as a component of Red Hat Enterprise Linux 9; kernel-debug as a component of Red Hat Enterprise Linux 9; kernel-debug-core as a component of Red Hat Enterprise Linux 9; kernel-debug-devel as a component of Red Hat Enterprise Linux 9; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-debug-modules as a component of Red Hat Enterprise Linux 9; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 9; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 9; and 78 more
    Red Hat Product Security ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    966ceafc7a437105ecfe1cadb3747b2965a260ca < 2efbd8890b53f4756fdc7b0ef346fa514ffb7d66; 966ceafc7a437105ecfe1cadb3747b2965a260ca < 0f27b22343b63e10773e6781344640c2c753eec3; 966ceafc7a437105ecfe1cadb3747b2965a260ca < 03c9c9116e6da641424681f705698d7f5e2128e0; 966ceafc7a437105ecfe1cadb3747b2965a260ca < b2d5a81dae385333f9734910277fbf94c78bd17f; 6.10 · Fixed: < 6.10; 6.12.105 ≤ 6.12.*; 6.18.46 ≤ 6.18.*; 7.1.10 ≤ 7.1.*; 7.2 ≤ *
    After
    Linux: 966ceafc7a437105ecfe1cadb3747b2965a260ca < 2efbd8890b53f4756fdc7b0ef346fa514ffb7d66, 966ceafc7a437105ecfe1cadb3747b2965a260ca < 0f27b22343b63e10773e6781344640c2c753eec3, 966ceafc7a437105ecfe1cadb3747b2965a260ca < 03c9c9116e6da641424681f705698d7f5e2128e0, 966ceafc7a437105ecfe1cadb3747b2965a260ca < b2d5a81dae385333f9734910277fbf94c78bd17f, 6.10 · Fixed: Linux: < 6.10, 6.12.105 ≤ 6.12.*, 6.18.46 ≤ 6.18.*, 7.1.10 ≤ 7.1.*, 7.2 ≤ *
    CNA ↗
  6. ENISA EUVD mappingEUVD-2026-66445 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-66445"}
    ENISA EUVD ↗
  7. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
  8. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    CNA ↗
  9. CVSS scoreCVSS score changed from not recorded to 7.1 (CVSS 3.1 · CNA · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).
    Before
    not recorded
    After
    7.1 (CVSS 3.1 · CNA · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N)
    CNA ↗
  10. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/2efbd8890b53f4756fdc7b0ef346fa514ffb7d66; removed remediation: git.kernel.org/03c9c9116e6da641424681f705698d7f5e2128e0.
    Before
    remediation: git.kernel.org/03c9c9116e6da641424681f705698d7f5e2128e0
    After
    remediation: git.kernel.org/2efbd8890b53f4756fdc7b0ef346fa514ffb7d66
    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-66445↗Vendor CSAF · SUSE Product Security Team↗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-80530 · cve.blacktree.nl