dbcve.org
Linux KernelOperating system · Linux

CVE-2026-43359

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-08
Fix available
A fix is available. Upgrade to 6.1.167 / 6.6.130 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix transaction abort on set received ioctl due to item overflow If the set received ioctl fails due to an item overflow when attempting to add the BTRFS_UUID_KEY_RECEIVED_SUBVOL we have to abort the transaction since we did some metadata updates before. This means that if a user calls this ioctl with the same received UUID field for a lot of subvolumes, we will hit the overflow, trigger the transaction abort and turn the filesystem into RO mode. A malicious user could exploit this, and this ioctl does not even requires that a user has admin privileges (CAP_SYS_ADMIN), only that he/she owns the subvolume. Fix this by doing an early check for item overflow before starting a transaction. This is also race safe because we are holding the subvol_sem semaphore in exclusive (write) mode. A test case for fstests will follow soon.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 3.12, < 6.1.167>= 6.2, < 6.6.130>= 6.7, < 6.12.78>= 6.13, < 6.18.19>= 6.19, < 6.19.9= 7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.1.167 / 6.6.130 / 6.12.78 or later
Fixed in 6.1.1676.6.1306.12.78
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to Linux kernel 6.1.167+ (if on 6.1.x), 6.6.130+ (if on 6.2-6.5.x), 6.12.78+ (if on 6.6-6.11.x), or 6.18.19+ (if on 6.12-6.17.x)

  1. 1. Identify the current running kernel version using 'uname -r'
  2. 2. Check which stable kernel branch you are on (e.g., 6.1.x, 6.2.x-6.5.x, 6.6.x-6.11.x, 6.12.x-6.17.x)
  3. 3. Upgrade to a kernel version >= the first fixed version in your branch: for 6.1.x line upgrade to 6.1.167 or later, for 6.2-6.5.x upgrade to 6.6.130 or later, for 6.6-6.11.x upgrade to 6.12.78 or later, for 6.12-6.17.x upgrade to 6.18.19 or later
  4. 4. If using a distribution kernel (e.g., Ubuntu, RHEL, Debian), upgrade via the distribution's package manager (apt-get update && apt-get upgrade, or dnf update, etc.)
  5. 5. Reboot the system to load the new kernel
  6. 6. Verify the kernel version after reboot with 'uname -r' to confirm the fix is applied
  7. 7. For distributions that track upstream kernels, ensure you receive kernel updates that include commit 2e57b8cac2ba0d38aac76c1ecdfd8b899e3581a5
Caveat Standard kernel upgrade risks apply - ensure compatibility with existing system drivers and modules; distribution kernels may have different version numbering

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-43359 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-43359 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data