BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-68358High confidence

btrfs: fix racy bitfield write in btrfs_clear_space_info_full()

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.18% 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: No default targetRemediation target: Normal maintenance

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.69-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.164-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.17.13-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.17.13-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-2025-68358 · CSAF 2.0 · revision 17 · interimSUSE Product Security TeamCVE-2025-68358
557 known affected

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

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() From the memory-barriers.txt document regarding memory barrier ordering guarantees: (*) These guarantees do not apply to bitfields, because compilers often generate code to modify these using non-atomic read-modify-write sequences. Do not attempt to use bitfields to synchronize parallel algorithms. (*) Even in cases where bitfields are protected by locks, all fields in a given bitfield must be protected by one lock. If two fields in a given bitfield are protected by different locks, the compiler's non-atomic read-modify-write sequences can cause an update to one field to corrupt the value of an adjacent field. btrfs_space_info has a bitfield sharing an underlying word consisting of the fields full, chunk_alloc, and flush: struct btrfs_space_info { struct btrfs_fs_info * fs_info; /* 0 8 */ struct btrfs_space_info * parent; /* 8 8 */ ... int clamp; /* 172 4 */ unsigned int full:1; /* 176: 0 4 */ unsigned int chunk_alloc:1; /* 176: 1 4 */ unsigned int flush:1; /* 176: 2 4 */ ... Therefore, to be safe from parallel read-modify-writes losing a write to one of the bitfield members protected by a lock, all writes to all the bitfields must use the lock. They almost universally do, except for btrfs_clear_space_info_full() which iterates over the space_infos and writes out found->full = 0 without a lock. Imagine that we have one thread completing a transaction in which we finished deleting a block_group and are thus calling btrfs_clear_space_info_full() while simultaneously the data reclaim ticket infrastructure is running do_async_reclaim_data_space(): T1 T2 btrfs_commit_transaction btrfs_clear_space_info_full data_sinfo->full = 0 READ: full:0, chunk_alloc:0, flush:1 do_async_reclaim_data_space(data_sinfo) spin_lock(&space_info->lock); if(list_empty(tickets)) space_info->flush = 0; READ: full: 0, chunk_alloc:0, flush:1 MOD/WRITE: full: 0, chunk_alloc:0, flush:0 spin_unlock(&space_info->lock); return; MOD/WRITE: full:0, chunk_alloc:0, flush:1 and now data_sinfo->flush is 1 but the reclaim worker has exited. This breaks the invariant that flush is 0 iff there is no work queued or running. Once this invariant is violated, future allocations that go into __reserve_bytes() will add tickets to space_info->tickets but will see space_info->flush is set to 1 and not queue the work. After this, they will block forever on the resulting ticket, as it is now impossible to kick the worker again. I also confirmed by looking at the assembly of the affected kernel that it is doing RMW operations. For example, to set the flush (3rd) bit to 0, the assembly is: andb $0xfb,0x60(%rbx) and similarly for setting the full (1st) bit to 0: andb $0xfe,-0x20(%rax) So I think this is really a bug on practical systems. I have observed a number of systems in this exact state, but am currently unable to reproduce it. Rather than leaving this footgun lying around for the future, take advantage of the fact that there is room in the struct anyway, and that it is already quite large and simply change the three bitfield members to bools. This avoids writes to space_info->full having any effect on ---truncated---
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-2025-205096

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() From the memory-barriers.txt document regarding memory barrier ordering guarantees: (*) These guarantees do not apply to bitfields, because compilers often generate code to modify these using non-atomic read-modify-write sequences. Do not attempt to use bitfields to synchronize parallel algorithms. (*) Even in cases where bitfields are protected by locks, all fields in a given bitfield must be protected by one lock. If two fields in a given bitfield are protected by different locks, the compiler's non-atomic read-modify-write sequences can cause an update to one field to corrupt the value of an adjacent field. btrfs_space_info has a bitfield sharing an underlying word consisting of the fields full, chunk_alloc, and flush: struct btrfs_space_info { struct btrfs_fs_info * fs_info; /* 0 8 */ struct btrfs_space_info * parent; /* 8 8 */ ... int clamp; /* 172 4 */ unsigned int full:1; /* 176: 0 4 */ unsigned int chunk_alloc:1; /* 176: 1 4 */ unsigned int flush:1; /* 176: 2 4 */ ... Therefore, to be safe from parallel read-modify-writes losing a write to one of the bitfield members protected by a lock, all writes to all the bitfields must use the lock. They almost universally do, except for btrfs_clear_space_info_full() which iterates over the space_infos and writes out found->full = 0 without a lock. Imagine that we have one thread completing a transaction in which we finished deleting a block_group and are thus calling btrfs_clear_space_info_full() while simultaneously the data reclaim ticket infrastructure is running do_async_reclaim_data_space(): T1 T2 btrfs_commit_transaction btrfs_clear_space_info_full data_sinfo->full = 0 READ: full:0, chunk_alloc:0, flush:1 do_async_reclaim_data_space(data_sinfo) spin_lock(&space_info->lock); if(list_empty(tickets)) space_info->flush = 0; READ: full: 0, chunk_alloc:0, flush:1 MOD/WRITE: full: 0, chunk_alloc:0, flush:0 spin_unlock(&space_info->lock); return; MOD/WRITE: full:0, chunk_alloc:0, flush:1 and now data_sinfo->flush is 1 but the reclaim worker has exited. This breaks the invariant that flush is 0 iff there is no work queued or running. Once this invariant is violated, future allocations that go into __reserve_bytes() will add tickets to space_info->tickets but will see space_info->flush is set to 1 and not queue the work. After this, they will block forever on the resulting ticket, as it is now impossible to kick the worker again. I also confirmed by looking at the assembly of the affected kernel that it is doing RMW operations. For example, to set the flush (3rd) bit to 0, the assembly is: andb $0xfb,0x60(%rbx) and similarly for setting the full (1st) bit to 0: andb $0xfe,-0x20(%rax) So I think this is really a bug on practical systems. I have observed a number of systems in this exact state, but am currently unable to reproduce it. Rather than leaving this footgun lying around for the future, take advantage of the fact that there is room in the struct anyway, and that it is already quite large and simply change the three bitfield members to bools. This avoids writes to space_info->full having any effect on ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() From the memory-barriers.txt document regarding memory barrier ordering guarantees: (*) These guarantees do not apply to bitfields, because compilers often generate code to modify these using non-atomic read-modify-write sequences. Do not attempt to use bitfields to synchronize parallel algorithms. (*) Even in cases where bitfields are protected by locks, all fields in a given bitfield must be protected by one lock. If two fields in a given bitfield are protected by different locks, the compiler's non-atomic read-modify-write sequences can cause an update to one field to corrupt the value of an adjacent field. btrfs_space_info has a bitfield sharing an underlying word consisting of the fields full, chunk_alloc, and flush: struct btrfs_space_info { struct btrfs_fs_info * fs_info; /* 0 8 */ struct btrfs_space_info * parent; /* 8 8 */ ... int clamp; /* 172 4 */ unsigned int full:1; /* 176: 0 4 */ unsigned int chunk_alloc:1; /* 176: 1 4 */ unsigned int flush:1; /* 176: 2 4 */ ... Therefore, to be safe from parallel read-modify-writes losing a write to one of the bitfield members protected by a lock, all writes to all the bitfields must use the lock. They almost universally do, except for btrfs_clear_space_info_full() which iterates over the space_infos and writes out found->full = 0 without a lock. Imagine that we have one thread completing a transaction in which we finished deleting a block_group and are thus calling btrfs_clear_space_info_full() while simultaneously the data reclaim ticket infrastructure is running do_async_reclaim_data_space(): T1 T2 btrfs_commit_transaction btrfs_clear_space_info_full data_sinfo->full = 0 READ: full:0, chunk_alloc:0, flush:1 do_async_reclaim_data_space(data_sinfo) spin_lock(&space_info->lock); if(list_empty(tickets)) space_info->flush = 0; READ: full: 0, chunk_alloc:0, flush:1 MOD/WRITE: full: 0, chunk_alloc:0, flush:0 spin_unlock(&space_info->lock); return; MOD/WRITE: full:0, chunk_alloc:0, flush:1 and now data_sinfo->flush is 1 but the reclaim worker has exited. This breaks the invariant that flush is 0 iff there is no work queued or running. Once this invariant is violated, future allocations that go into __reserve_bytes() will add tickets to space_info->tickets but will see space_info->flush is set to 1 and not queue the work. After this, they will block forever on the resulting ticket, as it is now impossible to kick the worker again. I also confirmed by looking at the assembly of the affected kernel that it is doing RMW operations. For example, to set the flush (3rd) bit to 0, the assembly is: andb $0xfb,0x60(%rbx) and similarly for setting the full (1st) bit to 0: andb $0xfe,-0x20(%rax) So I think this is really a bug on practical systems. I have observed a number of systems in this exact state, but am currently unable to reproduce it. Rather than leaving this footgun lying around for the future, take advantage of the fact that there is room in the struct anyway, and that it is already quite large and simply change the three bitfield members to bools. This avoids writes to space_info->full having any effect on ---truncated---

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: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() From the memory-barriers.txt document regarding memory barrier ordering guarantees: (*) These guarantees do not apply to bitfields, because compilers often generate code to modify these using non-atomic read-modify-write sequences. Do not attempt to use bitfields to synchronize parallel algorithms. (*) Even in cases where bitfields are protected by locks, all fields in a given bitfield must be protected by one lock. If two fields in a given bitfield are protected by different locks, the compiler's non-atomic read-modify-write sequences can cause an update to one field to corrupt the value of an adjacent field. btrfs_space_info has a bitfield sharing an underlying word consisting of the fields full, chunk_alloc, and flush: struct btrfs_space_info { struct btrfs_fs_info * fs_info; /* 0 8 */ struct btrfs_space_info * parent; /* 8 8 */ ... int clamp; /* 172 4 */ unsigned int full:1; /* 176: 0 4 */ unsigned int chunk_alloc:1; /* 176: 1 4 */ unsigned int flush:1; /* 176: 2 4 */ ... Therefore, to be safe from parallel read-modify-writes losing a write to one of the bitfield members protected by a lock, all writes to all the bitfields must use the lock. They almost universally do, except for btrfs_clear_space_info_full() which iterates over the space_infos and writes out found->full = 0 without a lock. Imagine that we have one thread completing a transaction in which we finished deleting a block_group and are thus calling btrfs_clear_space_info_full() while simultaneously the data reclaim ticket infrastructure is running do_async_reclaim_data_space(): T1 T2 btrfs_commit_transaction btrfs_clear_space_info_full data_sinfo->full = 0 READ: full:0, chunk_alloc:0, flush:1 do_async_reclaim_data_space(data_sinfo) spin_lock(&space_info->lock); if(list_empty(tickets)) space_info->flush = 0; READ: full: 0, chunk_alloc:0, flush:1 MOD/WRITE: full: 0, chunk_alloc:0, flush:0 spin_unlock(&space_info->lock); return; MOD/WRITE: full:0, chunk_alloc:0, flush:1 and now data_sinfo->flush is 1 but the reclaim worker has exited. This breaks the invariant that flush is 0 iff there is no work queued or running. Once this invariant is violated, future allocations that go into __reserve_bytes() will add tickets to space_info->tickets but will see space_info->flush is set to 1 and not queue the work. After this, they will block forever on the resulting ticket, as it is now impossible to kick the worker again. I also confirmed by looking at the assembly of the affected kernel that it is doing RMW operations. For example, to set the flush (3rd) bit to 0, the assembly is: andb $0xfb,0x60(%rbx) and similarly for setting the full (1st) bit to 0: andb $0xfe,-0x20(%rax) So I think this is really a bug on practical systems. I have observed a number of systems in this exact state, but am currently unable to reproduce it. Rather than leaving this footgun lying around for the future, take advantage of the fact that there is room in the struct anyway, and that it is already quite large and simply change the three bitfield members to bools. This avoids writes to space_info->full having any effect on ---truncated---

Why

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

How

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

02

Exploit reality and attack path

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

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

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

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

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

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

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

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

Official authority intelligence

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

BSI · German · WID-SEC-2025-2920Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251231Security Bulletin 31 Dec 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 31 Dec 2025, published on 31 December 2025. 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

de sécurité SUSE SUSE-SU-2026:23965-1 du 29 septembre 2026 https://www.suse.com/support/update/announcement/2026/suse-su-202623965-1 Bulletin de sécurité SUSE SUSE-SU-2026:23966-1 du 29 septembre 2026 https://www.suse.com/support/update/announcement/2026/suse-su-202623966-1 Bulletin de sécurité SUSE SUSE-SU-2026:23967-1 du 29 septembre 2026 https://www.suse.com/support/update/announcement/2026/suse-su-202623967-1 Bulletin de sécurité SUSE SUSE-SU-2026:23968-1 du 29 septembre 2026 https://www.suse.com/support/update/announcement/2026/suse-su-202623968-1 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-71075 https://www.cve.org/CVERecord?id=CVE-2025-71075 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23306 https://www.cve.org/CVERecord?id=CVE-2026-23306 Référence CVE CVE-2026-23348 https://www.cve.org/CVERecord?id=CVE-2026-23348 Référence CVE CVE-2026-31418 https://www.cve.org/CVERecord?id=CVE-2026-31418 Référence CVE CVE-2026-31530 https://www.cve.org/CVERecord?id=CVE-2026-31530 Référence CVE CVE-2026-31531 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-2025-40016 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40323 https://www.cve.org/CVERecord?id=CVE-2025-40323 Référence CVE CVE-2025-54505 https://www.cve.org/CVERecord?id=CVE-2025-54505 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-68239 https://www.cve.org/CVERecord?id=CVE-2025-68239 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-71150 https://www.cve.org/CVERecord?id=CVE-2025-71150 Référence CVE CVE-2025-71161 https://www.cve.org/CVERecord?id=CVE-2025-71161 Référence CVE CVE-2025-71221 https://www.cve.org/CVERecord?id=CVE-2025-71221 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71233 https://www.cve.org/CVERecord?id=CVE-2025-71233 Référence CVE CVE-2025-71235 https://www.cve.org/CVERecord?id=CVE-2025-71235 Référence CVE CVE-2025-71236 https://www.cve.org/CVERecord?id=CVE-2025-71236 Référence CVE CVE-2025-71237 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40103 Référence CVE CVE-2025-40323 https://www.cve.org/CVERecord?id=CVE-2025-40323 Référence CVE CVE-2025-54505 https://www.cve.org/CVERecord?id=CVE-2025-54505 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-68239 https://www.cve.org/CVERecord?id=CVE-2025-68239 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-71150 https://www.cve.org/CVERecord?id=CVE-2025-71150 Référence CVE CVE-2025-71158 https://www.cve.org/CVERecord?id=CVE-2025-71158 Référence CVE CVE-2025-71160 https://www.cve.org/CVERecord?id=CVE-2025-71160 Référence CVE CVE-2025-71161 https://www.cve.org/CVERecord?id=CVE-2025-71161 Référence CVE CVE-2025-71162 https://www.cve.org/CVERecord?id=CVE-2025-71162 Référence CVE CVE-2025-71163 https://www.cve.org/CVERecord?id=CVE-2025-71163 Référence CVE CVE-2025-71180 https://www.cve.org/CVERecord?id=CVE-2025-71180 Référence CVE CVE-2025-71182 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40016 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40323 https://www.cve.org/CVERecord?id=CVE-2025-40323 Référence CVE CVE-2025-54505 https://www.cve.org/CVERecord?id=CVE-2025-54505 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-68239 https://www.cve.org/CVERecord?id=CVE-2025-68239 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-71150 https://www.cve.org/CVERecord?id=CVE-2025-71150 Référence CVE CVE-2025-71161 https://www.cve.org/CVERecord?id=CVE-2025-71161 Référence CVE CVE-2025-71221 https://www.cve.org/CVERecord?id=CVE-2025-71221 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71233 https://www.cve.org/CVERecord?id=CVE-2025-71233 Référence CVE CVE-2025-71235 https://www.cve.org/CVERecord?id=CVE-2025-71235 Référence CVE CVE-2025-71236 https://www.cve.org/CVERecord?id=CVE-2025-71236 Référence CVE CVE-2025-71237 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-62626 Référence CVE CVE-2025-68175 https://www.cve.org/CVERecord?id=CVE-2025-68175 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68239 https://www.cve.org/CVERecord?id=CVE-2025-68239 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68334 https://www.cve.org/CVERecord?id=CVE-2025-68334 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68736 https://www.cve.org/CVERecord?id=CVE-2025-68736 Référence CVE CVE-2025-71089 https://www.cve.org/CVERecord?id=CVE-2025-71089 Référence CVE CVE-2025-71150 https://www.cve.org/CVERecord?id=CVE-2025-71150 Référence CVE CVE-2025-71152 https://www.cve.org/CVERecord?id=CVE-2025-71152 Référence CVE CVE-2025-71158 https://www.cve.org/CVERecord?id=CVE-2025-71158 Référence CVE CVE-2025-71160 https://www.cve.org/CVERecord?id=CVE-2025-71160 Référence CVE CVE-2025-71161 https://www.cve.org/CVERecord?id=CVE-2025-71161 Référence CVE CVE-2025-71162 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-54505 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-62626 https://www.cve.org/CVERecord?id=CVE-2025-62626 Référence CVE CVE-2025-68175 https://www.cve.org/CVERecord?id=CVE-2025-68175 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-68239 https://www.cve.org/CVERecord?id=CVE-2025-68239 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68334 https://www.cve.org/CVERecord?id=CVE-2025-68334 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68736 https://www.cve.org/CVERecord?id=CVE-2025-68736 Référence CVE CVE-2025-71150 https://www.cve.org/CVERecord?id=CVE-2025-71150 Référence CVE CVE-2025-71152 https://www.cve.org/CVERecord?id=CVE-2025-71152 Référence CVE CVE-2025-71158 https://www.cve.org/CVERecord?id=CVE-2025-71158 Référence CVE CVE-2025-71160 https://www.cve.org/CVERecord?id=CVE-2025-71160 Référence CVE CVE-2025-71161 https://www.cve.org/CVERecord?id=CVE-2025-71161 Référence CVE CVE-2025-71162 https://www.cve.org/CVERecord?id=CVE-2025-71162 Référence CVE CVE-2025-71163 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38591 Référence CVE CVE-2025-40005 https://www.cve.org/CVERecord?id=CVE-2025-40005 Référence CVE CVE-2025-40039 https://www.cve.org/CVERecord?id=CVE-2025-40039 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-54505 https://www.cve.org/CVERecord?id=CVE-2025-54505 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68351 https://www.cve.org/CVERecord?id=CVE-2025-68351 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68749 https://www.cve.org/CVERecord?id=CVE-2025-68749 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68823 https://www.cve.org/CVERecord?id=CVE-2025-68823 Référence CVE CVE-2025-71089 https://www.cve.org/CVERecord?id=CVE-2025-71089 Référence CVE CVE-2025-71160 https://www.cve.org/CVERecord?id=CVE-2025-71160 Référence CVE CVE-2025-71162 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68336 Référence CVE CVE-2025-68337 https://www.cve.org/CVERecord?id=CVE-2025-68337 Référence CVE CVE-2025-68344 https://www.cve.org/CVERecord?id=CVE-2025-68344 Référence CVE CVE-2025-68345 https://www.cve.org/CVERecord?id=CVE-2025-68345 Référence CVE CVE-2025-68346 https://www.cve.org/CVERecord?id=CVE-2025-68346 Référence CVE CVE-2025-68347 https://www.cve.org/CVERecord?id=CVE-2025-68347 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68351 https://www.cve.org/CVERecord?id=CVE-2025-68351 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68369 https://www.cve.org/CVERecord?id=CVE-2025-68369 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-58096 Référence CVE CVE-2024-58097 https://www.cve.org/CVERecord?id=CVE-2024-58097 Référence CVE CVE-2025-37926 https://www.cve.org/CVERecord?id=CVE-2025-37926 Référence CVE CVE-2025-38201 https://www.cve.org/CVERecord?id=CVE-2025-38201 Référence CVE CVE-2025-38591 https://www.cve.org/CVERecord?id=CVE-2025-38591 Référence CVE CVE-2025-40039 https://www.cve.org/CVERecord?id=CVE-2025-40039 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-68351 https://www.cve.org/CVERecord?id=CVE-2025-68351 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68749 https://www.cve.org/CVERecord?id=CVE-2025-68749 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68823 https://www.cve.org/CVERecord?id=CVE-2025-68823 Référence CVE CVE-2025-71160 https://www.cve.org/CVERecord?id=CVE-2025-71160 Référence CVE CVE-2025-71162 https://www.cve.org/CVERecord?id=CVE-2025-71162 Référence CVE CVE-2025-71163 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38408 Référence CVE CVE-2025-38591 https://www.cve.org/CVERecord?id=CVE-2025-38591 Référence CVE CVE-2025-40039 https://www.cve.org/CVERecord?id=CVE-2025-40039 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-40164 https://www.cve.org/CVERecord?id=CVE-2025-40164 Référence CVE CVE-2025-68211 https://www.cve.org/CVERecord?id=CVE-2025-68211 Référence CVE CVE-2025-68340 https://www.cve.org/CVERecord?id=CVE-2025-68340 Référence CVE CVE-2025-68351 https://www.cve.org/CVERecord?id=CVE-2025-68351 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68749 https://www.cve.org/CVERecord?id=CVE-2025-68749 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68817 https://www.cve.org/CVERecord?id=CVE-2025-68817 Référence CVE CVE-2025-68823 https://www.cve.org/CVERecord?id=CVE-2025-68823 Référence CVE CVE-2025-71088 https://www.cve.org/CVERecord?id=CVE-2025-71088 Référence CVE CVE-2025-71090 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38408 Référence CVE CVE-2025-38591 https://www.cve.org/CVERecord?id=CVE-2025-38591 Référence CVE CVE-2025-40039 https://www.cve.org/CVERecord?id=CVE-2025-40039 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-40164 https://www.cve.org/CVERecord?id=CVE-2025-40164 Référence CVE CVE-2025-68211 https://www.cve.org/CVERecord?id=CVE-2025-68211 Référence CVE CVE-2025-68340 https://www.cve.org/CVERecord?id=CVE-2025-68340 Référence CVE CVE-2025-68351 https://www.cve.org/CVERecord?id=CVE-2025-68351 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68749 https://www.cve.org/CVERecord?id=CVE-2025-68749 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68817 https://www.cve.org/CVERecord?id=CVE-2025-68817 Référence CVE CVE-2025-68823 https://www.cve.org/CVERecord?id=CVE-2025-68823 Référence CVE CVE-2025-71088 https://www.cve.org/CVERecord?id=CVE-2025-71088 Référence CVE CVE-2025-71090 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68344 Référence CVE CVE-2025-68345 https://www.cve.org/CVERecord?id=CVE-2025-68345 Référence CVE CVE-2025-68346 https://www.cve.org/CVERecord?id=CVE-2025-68346 Référence CVE CVE-2025-68347 https://www.cve.org/CVERecord?id=CVE-2025-68347 Référence CVE CVE-2025-68348 https://www.cve.org/CVERecord?id=CVE-2025-68348 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68352 https://www.cve.org/CVERecord?id=CVE-2025-68352 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68356 https://www.cve.org/CVERecord?id=CVE-2025-68356 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68359 https://www.cve.org/CVERecord?id=CVE-2025-68359 Référence CVE CVE-2025-68360 https://www.cve.org/CVERecord?id=CVE-2025-68360 Référence CVE CVE-2025-68361 https://www.cve.org/CVERecord?id=CVE-2025-68361 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68344 Référence CVE CVE-2025-68345 https://www.cve.org/CVERecord?id=CVE-2025-68345 Référence CVE CVE-2025-68346 https://www.cve.org/CVERecord?id=CVE-2025-68346 Référence CVE CVE-2025-68347 https://www.cve.org/CVERecord?id=CVE-2025-68347 Référence CVE CVE-2025-68348 https://www.cve.org/CVERecord?id=CVE-2025-68348 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68352 https://www.cve.org/CVERecord?id=CVE-2025-68352 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68356 https://www.cve.org/CVERecord?id=CVE-2025-68356 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68359 https://www.cve.org/CVERecord?id=CVE-2025-68359 Référence CVE CVE-2025-68360 https://www.cve.org/CVERecord?id=CVE-2025-68360 Référence CVE CVE-2025-68361 https://www.cve.org/CVERecord?id=CVE-2025-68361 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68344 Référence CVE CVE-2025-68345 https://www.cve.org/CVERecord?id=CVE-2025-68345 Référence CVE CVE-2025-68346 https://www.cve.org/CVERecord?id=CVE-2025-68346 Référence CVE CVE-2025-68347 https://www.cve.org/CVERecord?id=CVE-2025-68347 Référence CVE CVE-2025-68348 https://www.cve.org/CVERecord?id=CVE-2025-68348 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68352 https://www.cve.org/CVERecord?id=CVE-2025-68352 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68356 https://www.cve.org/CVERecord?id=CVE-2025-68356 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68359 https://www.cve.org/CVERecord?id=CVE-2025-68359 Référence CVE CVE-2025-68360 https://www.cve.org/CVERecord?id=CVE-2025-68360 Référence CVE CVE-2025-68361 https://www.cve.org/CVERecord?id=CVE-2025-68361 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68344 Référence CVE CVE-2025-68345 https://www.cve.org/CVERecord?id=CVE-2025-68345 Référence CVE CVE-2025-68346 https://www.cve.org/CVERecord?id=CVE-2025-68346 Référence CVE CVE-2025-68347 https://www.cve.org/CVERecord?id=CVE-2025-68347 Référence CVE CVE-2025-68348 https://www.cve.org/CVERecord?id=CVE-2025-68348 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68352 https://www.cve.org/CVERecord?id=CVE-2025-68352 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68356 https://www.cve.org/CVERecord?id=CVE-2025-68356 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68359 https://www.cve.org/CVERecord?id=CVE-2025-68359 Référence CVE CVE-2025-68360 https://www.cve.org/CVERecord?id=CVE-2025-68360 Référence CVE CVE-2025-68361 https://www.cve.org/CVERecord?id=CVE-2025-68361 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-23155 Référence CVE CVE-2025-37786 https://www.cve.org/CVERecord?id=CVE-2025-37786 Référence CVE CVE-2025-37822 https://www.cve.org/CVERecord?id=CVE-2025-37822 Référence CVE CVE-2025-37920 https://www.cve.org/CVERecord?id=CVE-2025-37920 Référence CVE CVE-2025-38201 https://www.cve.org/CVERecord?id=CVE-2025-38201 Référence CVE CVE-2025-38643 https://www.cve.org/CVERecord?id=CVE-2025-38643 Référence CVE CVE-2025-39763 https://www.cve.org/CVERecord?id=CVE-2025-39763 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40251 https://www.cve.org/CVERecord?id=CVE-2025-40251 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-71089 https://www.cve.org/CVERecord?id=CVE-2025-71089 Référence CVE CVE-2025-71144 https://www.cve.org/CVERecord?id=CVE-2025-71144 Référence CVE CVE-2025-71220 https://www.cve.org/CVERecord?id=CVE-2025-71220 Référence CVE CVE-2025-71222 https://www.cve.org/CVERecord?id=CVE-2025-71222 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71233 https://www.cve.org/CVERecord?id=CVE-2025-71233 Référence CVE CVE-2025-71235 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-68339 Référence CVE CVE-2025-68340 https://www.cve.org/CVERecord?id=CVE-2025-68340 Référence CVE CVE-2025-68342 https://www.cve.org/CVERecord?id=CVE-2025-68342 Référence CVE CVE-2025-68343 https://www.cve.org/CVERecord?id=CVE-2025-68343 Référence CVE CVE-2025-68344 https://www.cve.org/CVERecord?id=CVE-2025-68344 Référence CVE CVE-2025-68345 https://www.cve.org/CVERecord?id=CVE-2025-68345 Référence CVE CVE-2025-68346 https://www.cve.org/CVERecord?id=CVE-2025-68346 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=CVE-2025-68371 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-68339 Référence CVE CVE-2025-68340 https://www.cve.org/CVERecord?id=CVE-2025-68340 Référence CVE CVE-2025-68342 https://www.cve.org/CVERecord?id=CVE-2025-68342 Référence CVE CVE-2025-68343 https://www.cve.org/CVERecord?id=CVE-2025-68343 Référence CVE CVE-2025-68344 https://www.cve.org/CVERecord?id=CVE-2025-68344 Référence CVE CVE-2025-68345 https://www.cve.org/CVERecord?id=CVE-2025-68345 Référence CVE CVE-2025-68346 https://www.cve.org/CVERecord?id=CVE-2025-68346 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=CVE-2025-68371 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-23155 Référence CVE CVE-2025-37786 https://www.cve.org/CVERecord?id=CVE-2025-37786 Référence CVE CVE-2025-37822 https://www.cve.org/CVERecord?id=CVE-2025-37822 Référence CVE CVE-2025-37920 https://www.cve.org/CVERecord?id=CVE-2025-37920 Référence CVE CVE-2025-38201 https://www.cve.org/CVERecord?id=CVE-2025-38201 Référence CVE CVE-2025-38643 https://www.cve.org/CVERecord?id=CVE-2025-38643 Référence CVE CVE-2025-39763 https://www.cve.org/CVERecord?id=CVE-2025-39763 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40251 https://www.cve.org/CVERecord?id=CVE-2025-40251 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-71089 https://www.cve.org/CVERecord?id=CVE-2025-71089 Référence CVE CVE-2025-71144 https://www.cve.org/CVERecord?id=CVE-2025-71144 Référence CVE CVE-2025-71220 https://www.cve.org/CVERecord?id=CVE-2025-71220 Référence CVE CVE-2025-71222 https://www.cve.org/CVERecord?id=CVE-2025-71222 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71233 https://www.cve.org/CVERecord?id=CVE-2025-71233 Référence CVE CVE-2025-71235 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68340 Référence CVE CVE-2025-68344 https://www.cve.org/CVERecord?id=CVE-2025-68344 Référence CVE CVE-2025-68345 https://www.cve.org/CVERecord?id=CVE-2025-68345 Référence CVE CVE-2025-68346 https://www.cve.org/CVERecord?id=CVE-2025-68346 Référence CVE CVE-2025-68347 https://www.cve.org/CVERecord?id=CVE-2025-68347 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68351 https://www.cve.org/CVERecord?id=CVE-2025-68351 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68357 https://www.cve.org/CVERecord?id=CVE-2025-68357 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68369 https://www.cve.org/CVERecord?id=CVE-2025-68369 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-026155LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。btrfs: btrfs_clear_space_info_full()における競合するビットフィールド書き込みの問題を修正しました。memory-barriers.txtドキュメントにあるメモリバリアの順序保証について説明します。これらの保証はビットフィールドには適用されません。なぜなら、コンパイラはこれらを非原子的な読み取り-修正-書き込みシーケンスで変更するコードを生成することが多いためです。そのため、ビットフィールドを使用して並列アルゴリズムの同期を試みてはいけません。たとえビットフィールドがロックで保護されていても、与えられたビットフィールド内のすべてのフィールドは1つのロックで保護する必要があります。もしビットフィールド内の2つのフィールドが異なるロックで保護されている場合、コンパイラの非原子的な読み取り-修正-書き込みシーケンスのため、1つのフィールドの更新が隣接フィールドの値を破損させる可能性があります。btrfs_space_infoは基になるワードを共有するビットフィールドを持ち、full、chunk_alloc、flushの各フィールドで構成されています。したがって、ロックで保護されたビットフィールドメンバーへの並列読み取り-修正-書き込みによる書き込みの損失を防ぐため、すべてのビットフィールドへの書き込みにロックを使用する必要があります。ほとんどの場合これが守られていますが、btrfs_clear_space_info_full()だけがロックなしでspace_infosを走査しfound-full = 0を書き込んでいました。例として、あるスレッドがブロックグループの削除を完了しbtrfs_clear_space_info_full()を呼び出している一方で、データリクレイムチケットインフラがdo_async_reclaim_data_space()を実行している場合を想定します。T1（btrfs_commit_transaction）でbtrfs_clear_space_info_fullがfullを0に設定し、T2（do_async_reclaim_data_space）でロック取得後flushを0に書き換える処理が競合します。その結果、data_sinfo-flushが1のままリクレイムワーカーは終了し、flushが0なら作業がなければならないという不変条件が破られます。この不変条件が破れると、__reserve_bytes()で将来の割り当てがspace_info-ticketsにチケットを追加してもflushが1のままなので作業キューを生成せず、その後永遠にチケットでブロックされワーカーを再起動できなくなります。影響を受けるカーネルのアセンブリを調査したところ、flushビット（3番目のビット）を0にセットするためにandb命令が使われ、fullビット（1番目のビット）を0にする場合も同様の読み取り-修正-書き込み操作が行われているため、実際のシステム上で問題となるバグであると判断しています。現在この状態のシステムはいくつか観測されていますが、再現は困難です。今後の問題を防ぐため、構造体に余裕があることから3つのビットフィールドメンバーをbool型に変更し対応しました。これにより、space_info-fullへの書き込みが他のビットの値に影響を与えることを防ぎます。

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: < 4.8, 5.15.201 ≤ 5.15.*, 6.1.164 ≤ 6.1.*, 6.6.124 ≤ 6.6.*, 6.12.68 ≤ 6.12.*, 6.17.13 ≤ 6.17.*, 6.18.2 ≤ 6.18.*, 6.19 ≤ *
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 24 Dec 2025 · Last source change 11 May 2026, 21:51 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-205096
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    kernel-default as component of SLES-LTSS-TERADATA 15 SP2; kernel-source as component of SLES-LTSS-TERADATA 15 SP2; kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP3; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP6; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP6; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; 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; and 525 more · Fixed: kernel-64kb-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-64kb-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-64kb-extra-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-extra-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-vdso-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-base-6.12.0-160000.38.1.160000.2.24 as component of SUSE Linux Enterprise Server 16.0; kernel-default-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-extra-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-livepatch-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-vdso-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-docs-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-docs-html-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-kvmsmall-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-kvmsmall-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-kvmsmall-vdso-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-macros-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-obs-qa-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-source-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-source-vanilla-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-syms-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-zfcpdump-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; cluster-md-kmp-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; dlm-kmp-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; gfs2-kmp-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-64kb-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-64kb-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; and 38 more
    After
    kernel-default as component of SLES-LTSS-TERADATA 15 SP2; kernel-source as component of SLES-LTSS-TERADATA 15 SP2; kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP3; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP6; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP6; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; 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; and 527 more
    SUSE Product Security Team ↗
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-2025-205096↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-68358 · cve.blacktree.nl