Full vulnerability report · 2026

CVE-2026-43046High confidence

btrfs: reject root items with drop_progress and zero drop_level

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

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.16% 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

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

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.

Canonical Ubuntu Security: 20 affected package states with no published fix

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 release	Source package	Vendor state	Fixed version	Evidence
Debian trixietrixie · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.12.85-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.1.170-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.19.12-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.19.12-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-fde`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-nvidia`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gke`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gkeop`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-ibm`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-lowlatency`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-tegra`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-xilinx`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

1 current

CVE-2026-43046 · CSAF 2.0 · revision 10 · interimSUSE Product Security TeamCVE-2026-43046

294 known affected

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

kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5

Summary: In the Linux kernel, the following vulnerability has been resolved: btrfs: reject root items with drop_progress and zero drop_level [BUG] When recovering relocation at mount time, merge_reloc_root() and btrfs_drop_snapshot() both use BUG_ON(level == 0) to guard against an impossible state: a non-zero drop_progress combined with a zero drop_level in a root_item, which can be triggered: ------------[ cut here ]------------ kernel BUG at fs/btrfs/relocation.c:1545! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI CPU: 1 UID: 0 PID: 283 ... Tainted: 6.18.0+ #16 PREEMPT(voluntary) Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: QEMU Ubuntu 24.04 PC v2, BIOS 1.16.3-debian-1.16.3-2 RIP: 0010:merge_reloc_root+0x1266/0x1650 fs/btrfs/relocation.c:1545 Code: ffff0000 00004589 d7e9acfa ffffe8a1 79bafebe 02000000 Call Trace: merge_reloc_roots+0x295/0x890 fs/btrfs/relocation.c:1861 btrfs_recover_relocation+0xd6e/0x11d0 fs/btrfs/relocation.c:4195 btrfs_start_pre_rw_mount+0xa4d/0x1810 fs/btrfs/disk-io.c:3130 open_ctree+0x5824/0x5fe0 fs/btrfs/disk-io.c:3640 btrfs_fill_super fs/btrfs/super.c:987 [inline] btrfs_get_tree_super fs/btrfs/super.c:1951 [inline] btrfs_get_tree_subvol fs/btrfs/super.c:2094 [inline] btrfs_get_tree+0x111c/0x2190 fs/btrfs/super.c:2128 vfs_get_tree+0x9a/0x370 fs/super.c:1758 fc_mount fs/namespace.c:1199 [inline] do_new_mount_fc fs/namespace.c:3642 [inline] do_new_mount fs/namespace.c:3718 [inline] path_mount+0x5b8/0x1ea0 fs/namespace.c:4028 do_mount fs/namespace.c:4041 [inline] __do_sys_mount fs/namespace.c:4229 [inline] __se_sys_mount fs/namespace.c:4206 [inline] __x64_sys_mount+0x282/0x320 fs/namespace.c:4206 ... RIP: 0033:0x7f969c9a8fde Code: 0f1f4000 48c7c2b0 fffffff7 d8648902 b8ffffff ffc3660f ---[ end trace 0000000000000000 ]--- The bug is reproducible on 7.0.0-rc2-next-20260310 with our dynamic metadata fuzzing tool that corrupts btrfs metadata at runtime. [CAUSE] A non-zero drop_progress.objectid means an interrupted btrfs_drop_snapshot() left a resume point on disk, and in that case drop_level must be greater than 0 because the checkpoint is only saved at internal node levels. Although this invariant is enforced when the kernel writes the root item, it is not validated when the root item is read back from disk. That allows on-disk corruption to provide an invalid state with drop_progress.objectid != 0 and drop_level == 0. When relocation recovery later processes such a root item, merge_reloc_root() reads drop_level and hits BUG_ON(level == 0). The same invalid metadata can also trigger the corresponding BUG_ON() in btrfs_drop_snapshot(). [FIX] Fix this by validating the root_item invariant in tree-checker when reading root items from disk: if drop_progress.objectid is non-zero, drop_level must also be non-zero. Reject such malformed metadata with -EUCLEAN before it reaches merge_reloc_root() or btrfs_drop_snapshot() and triggers the BUG_ON. After the fix, the same corruption is correctly rejected by tree-checker and the BUG_ON is no longer triggered.
Remediation: To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

Recommended actionPatch only the product branches with a verified fix

Fix availability varies by product

What, why and how

In the Linux kernel, the following vulnerability has been resolved: btrfs: reject root items with drop_progress and zero drop_level [BUG] When recovering relocation at mount time, merge_reloc_root() and btrfs_drop_snapshot() both use BUG_ON(level == 0) to guard against an impossible state: a non-zero drop_progress combined with a zero drop_level in a root_item, which can be triggered: ------------[ cut here ]------------ kernel BUG at fs/btrfs/relocation.c:1545! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI CPU: 1 UID: 0 PID: 283 ... Tainted: 6.18.0+ #16 PREEMPT(voluntary) Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: QEMU Ubuntu 24.04 PC v2, BIOS 1.16.3-debian-1.16.3-2 RIP: 0010:merge_reloc_root+0x1266/0x1650 fs/btrfs/relocation.c:1545 Code: ffff0000 00004589 d7e9acfa ffffe8a1 79bafebe 02000000 Call Trace: merge_reloc_roots+0x295/0x890 fs/btrfs/relocation.c:1861 btrfs_recover_relocation+0xd6e/0x11d0 fs/btrfs/relocation.c:4195 btrfs_start_pre_rw_mount+0xa4d/0x1810 fs/btrfs/disk-io.c:3130 open_ctree+0x5824/0x5fe0 fs/btrfs/disk-io.c:3640 btrfs_fill_super fs/btrfs/super.c:987 [inline] btrfs_get_tree_super fs/btrfs/super.c:1951 [inline] btrfs_get_tree_subvol fs/btrfs/super.c:2094 [inline] btrfs_get_tree+0x111c/0x2190 fs/btrfs/super.c:2128 vfs_get_tree+0x9a/0x370 fs/super.c:1758 fc_mount fs/namespace.c:1199 [inline] do_new_mount_fc fs/namespace.c:3642 [inline] do_new_mount fs/namespace.c:3718 [inline] path_mount+0x5b8/0x1ea0 fs/namespace.c:4028 do_mount fs/namespace.c:4041 [inline] __do_sys_mount fs/namespace.c:4229 [inline] __se_sys_mount fs/namespace.c:4206 [inline] __x64_sys_mount+0x282/0x320 fs/namespace.c:4206 ... RIP: 0033:0x7f969c9a8fde Code: 0f1f4000 48c7c2b0 fffffff7 d8648902 b8ffffff ffc3660f ---[ end trace 0000000000000000 ]--- The bug is reproducible on 7.0.0-rc2-next-20260310 with our dynamic metadata fuzzing tool that corrupts btrfs metadata at runtime. [CAUSE] A non-zero drop_progress.objectid means an interrupted btrfs_drop_snapshot() left a resume point on disk, and in that case drop_level must be greater than 0 because the checkpoint is only saved at internal node levels. Although this invariant is enforced when the kernel writes the root item, it is not validated when the root item is read back from disk. That allows on-disk corruption to provide an invalid state with drop_progress.objectid != 0 and drop_level == 0. When relocation recovery later processes such a root item, merge_reloc_root() reads drop_level and hits BUG_ON(level == 0). The same invalid metadata can also trigger the corresponding BUG_ON() in btrfs_drop_snapshot(). [FIX] Fix this by validating the root_item invariant in tree-checker when reading root items from disk: if drop_progress.objectid is non-zero, drop_level must also be non-zero. Reject such malformed metadata with -EUCLEAN before it reaches merge_reloc_root() or btrfs_drop_snapshot() and triggers the BUG_ON. After the fix, the same corruption is correctly rejected by tree-checker and the BUG_ON is no longer triggered.

What

Why

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

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

Why

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

How

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 → Reachable Assertion → 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: a standard category for the underlying weakness.: CWE-617 ↗
CWE-617: Reachable Assertion. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
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.

CWE-617

Official authority intelligence

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

ENISA EUVD · EUVD-2026-26645Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

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

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Root-Rechte zu erlangen, um Sicherheitsmechanismen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder Auswirkungen unbestimmter Art zu erzielen.

Official advisory ↗

Cyber Security Agency of Singapore · English · CSA-SB-20260506Security Bulletin 06 May 2026

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

Official advisory ↗

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

d?id=CVE-2026-43026 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43030 https://www.cve.org/CVERecord?id=CVE-2026-43030 Référence CVE CVE-2026-43032 https://www.cve.org/CVERecord?id=CVE-2026-43032 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43041 https://www.cve.org/CVERecord?id=CVE-2026-43041 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43046 https://www.cve.org/CVERecord?id=CVE-2026-43046 Référence CVE CVE-2026-43047 https://www.cve.org/CVERecord?id=CVE-2026-43047 Référence CVE CVE-2026-43050 https://www.cve.org/CVERecord?id=CVE-2026-43050 Référence CVE CVE-2026-43051 https://www.cve.org/CVERecord?id=CVE-2026-43051 Référence CVE CVE-2026-43052 https://www.cve.org/CVERecord?id=CVE-2026-43052 Référence CVE CVE-2026-43054 https://www.cve.org/CVERecord?id=CVE-2026-43054 Référence CVE CVE-2026-43058 https://www.cve.org/CVERecord?id=CVE-2026-43058 Référence CVE CVE-2026-43060 https://www.cve.org/CVERecord?id=CVE-2026-43060 Référence CVE CVE-2026-43061 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-2026-43028 Référence CVE CVE-2026-43030 https://www.cve.org/CVERecord?id=CVE-2026-43030 Référence CVE CVE-2026-43032 https://www.cve.org/CVERecord?id=CVE-2026-43032 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43041 https://www.cve.org/CVERecord?id=CVE-2026-43041 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43046 https://www.cve.org/CVERecord?id=CVE-2026-43046 Référence CVE CVE-2026-43047 https://www.cve.org/CVERecord?id=CVE-2026-43047 Référence CVE CVE-2026-43050 https://www.cve.org/CVERecord?id=CVE-2026-43050 Référence CVE CVE-2026-43051 https://www.cve.org/CVERecord?id=CVE-2026-43051 Référence CVE CVE-2026-43052 https://www.cve.org/CVERecord?id=CVE-2026-43052 Référence CVE CVE-2026-43054 https://www.cve.org/CVERecord?id=CVE-2026-43054 Référence CVE CVE-2026-43058 https://www.cve.org/CVERecord?id=CVE-2026-43058 Référence CVE CVE-2026-43060 https://www.cve.org/CVERecord?id=CVE-2026-43060 Référence CVE CVE-2026-43061 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1091Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-31482 Référence CVE CVE-2026-31483 https://www.cve.org/CVERecord?id=CVE-2026-31483 Référence CVE CVE-2026-31542 https://www.cve.org/CVERecord?id=CVE-2026-31542 Référence CVE CVE-2026-31598 https://www.cve.org/CVERecord?id=CVE-2026-31598 Référence CVE CVE-2026-31628 https://www.cve.org/CVERecord?id=CVE-2026-31628 Référence CVE CVE-2026-31629 https://www.cve.org/CVERecord?id=CVE-2026-31629 Référence CVE CVE-2026-31759 https://www.cve.org/CVERecord?id=CVE-2026-31759 Référence CVE CVE-2026-43016 https://www.cve.org/CVERecord?id=CVE-2026-43016 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43046 https://www.cve.org/CVERecord?id=CVE-2026-43046 Référence CVE CVE-2026-43056 https://www.cve.org/CVERecord?id=CVE-2026-43056 Référence CVE CVE-2026-43059 https://www.cve.org/CVERecord?id=CVE-2026-43059 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43109 https://www.cve.org/CVERecord?id=CVE-2026-43109 Référence CVE CVE-2026-43110 https://www.cve.org/CVERecord?id=CVE-2026-43110 Référence CVE CVE-2026-43114 https://www.cve.org/CVERecord?id=CVE-2026-43114 Référence CVE CVE-2026-43130 https://www.cve.org/CVERecord?id=CVE-2026-43130 Référence CVE CVE-2026-43161 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

d?id=CVE-2026-43028 Référence CVE CVE-2026-43030 https://www.cve.org/CVERecord?id=CVE-2026-43030 Référence CVE CVE-2026-43032 https://www.cve.org/CVERecord?id=CVE-2026-43032 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43036 https://www.cve.org/CVERecord?id=CVE-2026-43036 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43041 https://www.cve.org/CVERecord?id=CVE-2026-43041 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43044 https://www.cve.org/CVERecord?id=CVE-2026-43044 Référence CVE CVE-2026-43046 https://www.cve.org/CVERecord?id=CVE-2026-43046 Référence CVE CVE-2026-43047 https://www.cve.org/CVERecord?id=CVE-2026-43047 Référence CVE CVE-2026-43049 https://www.cve.org/CVERecord?id=CVE-2026-43049 Référence CVE CVE-2026-43050 https://www.cve.org/CVERecord?id=CVE-2026-43050 Référence CVE CVE-2026-43051 https://www.cve.org/CVERecord?id=CVE-2026-43051 Référence CVE CVE-2026-43052 https://www.cve.org/CVERecord?id=CVE-2026-43052 Référence CVE CVE-2026-43054 https://www.cve.org/CVERecord?id=CVE-2026-43054 Référence CVE CVE-2026-43056 https://www.cve.org/CVERecord?id=CVE-2026-43056 Référence CVE CVE-2026-43057 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1064Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-43018 Référence CVE CVE-2026-43019 https://www.cve.org/CVERecord?id=CVE-2026-43019 Référence CVE CVE-2026-43020 https://www.cve.org/CVERecord?id=CVE-2026-43020 Référence CVE CVE-2026-43023 https://www.cve.org/CVERecord?id=CVE-2026-43023 Référence CVE CVE-2026-43032 https://www.cve.org/CVERecord?id=CVE-2026-43032 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43044 https://www.cve.org/CVERecord?id=CVE-2026-43044 Référence CVE CVE-2026-43046 https://www.cve.org/CVERecord?id=CVE-2026-43046 Référence CVE CVE-2026-43047 https://www.cve.org/CVERecord?id=CVE-2026-43047 Référence CVE CVE-2026-43049 https://www.cve.org/CVERecord?id=CVE-2026-43049 Référence CVE CVE-2026-43051 https://www.cve.org/CVERecord?id=CVE-2026-43051 Référence CVE CVE-2026-43052 https://www.cve.org/CVERecord?id=CVE-2026-43052 Référence CVE CVE-2026-43056 https://www.cve.org/CVERecord?id=CVE-2026-43056 Référence CVE CVE-2026-43058 https://www.cve.org/CVERecord?id=CVE-2026-43058 Référence CVE CVE-2026-43059 https://www.cve.org/CVERecord?id=CVE-2026-43059 Référence CVE CVE-2026-43061 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1029Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-31542 Référence CVE CVE-2026-31598 https://www.cve.org/CVERecord?id=CVE-2026-31598 Référence CVE CVE-2026-31624 https://www.cve.org/CVERecord?id=CVE-2026-31624 Référence CVE CVE-2026-31628 https://www.cve.org/CVERecord?id=CVE-2026-31628 Référence CVE CVE-2026-31678 https://www.cve.org/CVERecord?id=CVE-2026-31678 Référence CVE CVE-2026-31738 https://www.cve.org/CVERecord?id=CVE-2026-31738 Référence CVE CVE-2026-31759 https://www.cve.org/CVERecord?id=CVE-2026-31759 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43046 https://www.cve.org/CVERecord?id=CVE-2026-43046 Référence CVE CVE-2026-43056 https://www.cve.org/CVERecord?id=CVE-2026-43056 Référence CVE CVE-2026-43068 https://www.cve.org/CVERecord?id=CVE-2026-43068 Référence CVE CVE-2026-43069 https://www.cve.org/CVERecord?id=CVE-2026-43069 Référence CVE CVE-2026-43123 https://www.cve.org/CVERecord?id=CVE-2026-43123 Référence CVE CVE-2026-43124 https://www.cve.org/CVERecord?id=CVE-2026-43124 Référence CVE CVE-2026-43156 https://www.cve.org/CVERecord?id=CVE-2026-43156 Référence CVE CVE-2026-43168 https://www.cve.org/CVERecord?id=CVE-2026-43168 Référence CVE CVE-2026-43180 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

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

d?id=CVE-2026-43032 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43036 https://www.cve.org/CVERecord?id=CVE-2026-43036 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43041 https://www.cve.org/CVERecord?id=CVE-2026-43041 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43044 https://www.cve.org/CVERecord?id=CVE-2026-43044 Référence CVE CVE-2026-43046 https://www.cve.org/CVERecord?id=CVE-2026-43046 Référence CVE CVE-2026-43047 https://www.cve.org/CVERecord?id=CVE-2026-43047 Référence CVE CVE-2026-43049 https://www.cve.org/CVERecord?id=CVE-2026-43049 Référence CVE CVE-2026-43050 https://www.cve.org/CVERecord?id=CVE-2026-43050 Référence CVE CVE-2026-43051 https://www.cve.org/CVERecord?id=CVE-2026-43051 Référence CVE CVE-2026-43052 https://www.cve.org/CVERecord?id=CVE-2026-43052 Référence CVE CVE-2026-43054 https://www.cve.org/CVERecord?id=CVE-2026-43054 Référence CVE CVE-2026-43056 https://www.cve.org/CVERecord?id=CVE-2026-43056 Référence CVE CVE-2026-43057 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

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

d?id=CVE-2026-43030 Référence CVE CVE-2026-43032 https://www.cve.org/CVERecord?id=CVE-2026-43032 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43041 https://www.cve.org/CVERecord?id=CVE-2026-43041 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43046 https://www.cve.org/CVERecord?id=CVE-2026-43046 Référence CVE CVE-2026-43047 https://www.cve.org/CVERecord?id=CVE-2026-43047 Référence CVE CVE-2026-43050 https://www.cve.org/CVERecord?id=CVE-2026-43050 Référence CVE CVE-2026-43051 https://www.cve.org/CVERecord?id=CVE-2026-43051 Référence CVE CVE-2026-43054 https://www.cve.org/CVERecord?id=CVE-2026-43054 Référence CVE CVE-2026-43057 https://www.cve.org/CVERecord?id=CVE-2026-43057 Gestion détaillée du document le 07 mai 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0548Multiples vulnérabilités dans le noyau Linux de Debian

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2026-014762LinuxのLinux Kernelにおける到達可能なアサーションに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。btrfsのdrop_progressが非ゼロでdrop_levelがゼロのroot itemsを拒否します。マウント時のリロケーション復旧処理では、merge_reloc_root()とbtrfs_drop_snapshot()の両方がBUG_ON(level == 0)を使用して、root_item内でdrop_progressが非ゼロかつdrop_levelがゼロというありえない状態が発生しないように防止しています。この状態は以下のようにトリガーされる可能性があります。------------[ここから切り取り]------------kernel BUG at fs/btrfs/relocation.c:1545!Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTICPU: 1 UID: 0 PID: 283 ... Tainted: 6.18.0+ #16 PREEMPT(voluntary)Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULEHardware name: QEMU Ubuntu 24.04 PC v2, BIOS 1.16.3-debian-1.16.3-2RIP: 0010:merge_reloc_root+0x1266/0x1650 fs/btrfs/relocation.c:1545Code: ffff0000 00004589 d7e9acfa ffffe8a1 79bafebe 02000000Call Trace: merge_reloc_roots+0x295/0x890 fs/btrfs/relocation.c:1861 btrfs_recover_relocation+0xd6e/0x11d0 fs/btrfs/relocation.c:4195 btrfs_start_pre_rw_mount+0xa4d/0x1810 fs/btrfs/disk-io.c:3130 open_ctree+0x5824/0x5fe0 fs/btrfs/disk-io.c:3640 btrfs_fill_super fs/btrfs/super.c:987 [inline] btrfs_get_tree_super fs/btrfs/super.c:1951 [inline] btrfs_get_tree_subvol fs/btrfs/super.c:2094 [inline] btrfs_get_tree+0x111c/0x2190 fs/btrfs/super.c:2128 vfs_get_tree+0x9a/0x370 fs/super.c:1758 fc_mount fs/namespace.c:1199 [inline] do_new_mount_fc fs/namespace.c:3642 [inline] do_new_mount fs/namespace.c:3718 [inline] path_mount+0x5b8/0x1ea0 fs/namespace.c:4028 do_mount fs/namespace.c:4041 [inline] __do_sys_mount fs/namespace.c:4229 [inline] __se_sys_mount fs/namespace.c:4206 [inline] __x64_sys_mount+0x282/0x320 fs/namespace.c:4206 ...RIP: 0033:0x7f969c9a8fdeCode: 0f1f4000 48c7c2b0 fffffff7 d8648902 b8ffffff ffc3660f---[ end trace 0000000000000000 ]---このバグは、我々の動的メタデータファジングツールを使用した7.0.0-rc2-next-20260310環境で再現可能であり、実行時にbtrfsメタデータを破損させます。[原因]drop_progress.objectidが非ゼロの場合、btrfs_drop_snapshot()が中断されてディスク上に再開ポイントが残っていることを意味し、その場合はdrop_levelが0より大きくなければなりません。なぜなら、チェックポイントは内部ノードレベルでのみ保存されるためです。この不変条件はカーネルがroot itemを書き込む際に適用されますが、root itemをディスクから読み込む際には検証されません。そのため、ディスク上の破損によりdrop_progress.objectidが非ゼロかつdrop_levelがゼロという不正な状態が発生します。リロケーション復旧処理がこのようなroot itemを処理するとき、merge_reloc_root()がdrop_levelを読み取りBUG_ON(level == 0)をトリガーします。同じ不正なメタデータはbtrfs_drop_snapshot()内の対応するBUG_ON()も引き起こします。[修正]root itemsをディスクから読み込む際にtree-checkerでroot_itemの不変条件を検証し、drop_progress.objectidが非ゼロの場合はdrop_levelも非ゼロであることを確認するよう修正しました。そのような不正なメタデータはmerge_reloc_root()やbtrfs_drop_snapshot()に到達してBUG_ONを引き起こす前に-EUCLEANで拒否されます。修正後は同じ破損がtree-checkerにより正しく拒否され、BUG_ONは発生しなくなりました。

Official advisory ↗

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: kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP5
ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1
reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2
and 264 more
Fixed: Linux: < 2.6.29, 5.15.203 ≤ 5.15.*, 6.1.168 ≤ 6.1.*, 6.6.134 ≤ 6.6.*, 6.12.81 ≤ 6.12.*, 6.18.22 ≤ 6.18.*, 6.19.12 ≤ 6.19.*, 7.0 ≤ *
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.

Evidence and provenance

Published 1 May 2026 · Last source change 11 May 2026, 22:16 UTC · CWE-617 · Reachable Assertion

CVE recordCVE.org · 5.2

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2026-26645

Product sourceVendor CSAF · SUSE Product Security Team

Remediation sourceVendor CSAF · SUSE Product Security Team

CWE sourceNIST NVD

NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

2026-05-01CVE published

2026-05-11Fixed release or patch reference recorded

ENISA EUVD · EUVD-2026-26645↗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.

btrfs: reject root items with drop_progress and zero drop_level

Published severity in operational context

Evidence used

Compensating controls

Verification

Remediation availability differs by product scope

Release-specific package status

Authoritative vendor CSAF and VEX advisories

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

ENISA European Vulnerability Database

EUVD-2026-26645

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication