CVE-2023-52569

btrfs: remove BUG() after failure to insert delayed dir index item

MEDIUM
5.5
CVSS Score
Published: March 2, 2024 at 09:59 PM UTC
Updated: June 17, 2026 at 06:43 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: remove BUG() after failure to insert delayed dir index item Instead of calling BUG() when we fail to insert a delayed dir index item into the delayed node's tree, we can just release all the resources we have allocated/acquired before and return the error to the caller. This is fine because all existing call chains undo anything they have done before calling btrfs_insert_delayed_dir_index() or BUG_ON (when creating pending snapshots in the transaction commit path). So remove the BUG() call and do proper error handling. This relates to a syzbot report linked below, but does not fix it because it only prevents hitting a BUG(), it does not fix the issue where somehow we attempt to use twice the same index number for different index items.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.15.149v ≥ 6.4.12v < 6.1.565.15.149 ≤ v < 5.166.2 ≤ v < 6.5.66.4.12 ≤ v < 6.56.5 ≤ v < 6.5.66.5 ≤ v < 6.65.15.1495441532ffc9c8c9f7cab0f8722e6d60a0b5e12596.4.126.6 rc179cf35e16dd5b8639909d4df957503b84de304069b378f6ad48cfa195ed868db9123c09ee7ec5ea2
Vendor states this is fixed in 2c58c3931ede7cd08cbecf1f1a4acaf0a04a41a9 (fixed)
Vendor states this is fixed in d10fd53393cc5de4b9cf1a4b8f9984f0a037aa51 (fixed)
Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.56, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.5 (unaffected)
Vendor states this is fixed in 6.5.6 (unaffected)
Vendor states this is fixed in 6.6 (unaffected)

References (3)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2c58c3931ede7cd08cbecf1f1a4acaf0a04a41a9
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d10fd53393cc5de4b9cf1a4b8f9984f0a037aa51
Patch
Source: af854a3a-2127-422b-91ae-364da2661108
https://git.kernel.org/stable/c/39c4a9522db0072570d602e9b365119e17fb9f4f

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-617

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card