CVE-2026-43299 Linux CVE debrief

Who should care

Linux administrators and users with Btrfs file systems, as well as security teams monitoring for potential file system issues, should be aware of this vulnerability. They should apply patches and monitor file system health to prevent potential read-only issues in Btrfs.

Why it matters

This vulnerability can cause a Linux kernel panic when a file system is flipped to read-only and a read repair is attempted. Defenders should apply patches and monitor file system health.

• Verify file system health to prevent potential read-only issues
• Monitor for ENOSPC errors during critical operations
• Apply patches to prevent assertion failures in `btrfs_repair_io_failure()`

Technical summary

The vulnerability occurs in the Btrfs file system within the Linux kernel. When the file system flips to read-only due to a critical error, a pending read repair can cause an assertion failure in `btrfs_repair_io_failure()`. The fix involves replacing the ASSERT() with a proper return if the fs is already read-only, preventing the kernel panic. This vulnerability can cause a Linux kernel panic when a file system is flipped to read-only and a read repair is attempted. Defenders should apply patches and monitor file system health.

Defensive priority

Apply patches to prevent potential read-only file system issues in Btrfs.

Recommended defensive actions

• Apply available patches from Linux kernel maintainers
• Monitor for potential ENOSPC errors during critical operations
• Verify file system health and perform regular maintenance
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The issue arises when the file system flips to RO due to a critical error, such as an ENOSPC error during a balance operation. If a read repair is pending, it can trigger an assertion failure in `btrfs_repair_io_failure()`. The fix involves replacing the ASSERT() with a proper return if the fs is already read-only. Defenders should verify file system health and monitor for ENOSPC errors during critical operations.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.