CVE-2026-23141
Invalid Memory Access in Linux Kernel btrfs Inline Extents
Publication date: 2026-02-14
Last updated on: 2026-03-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.13 (inc) to 6.18.7 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.7 (inc) to 6.12.67 (exc) |
| linux | linux_kernel | From 4.11 (inc) to 6.6.122 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's btrfs filesystem, specifically in the send functionality. The issue arises because the code does not properly check if a file extent item is an inline extent before accessing its disk_bytenr field.
Inline extents store their data starting at the disk_bytenr field offset, so accessing this field without checking can lead to accessing inline data directly or, if the inline data is less than 8 bytes and the item is the first in the leaf, it can cause invalid memory access or access to metadata from other items.
How can this vulnerability impact me? :
This vulnerability can lead to invalid memory access when processing btrfs filesystem data. Such invalid memory access can cause system crashes, data corruption, or potentially allow an attacker to execute arbitrary code or cause denial of service.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know