In the Linux kernel, the following vulnerability has been resolved: btrfs: lzo: reject compressed segment that overflows the compressed input lzo_decompress_bio() validates each on-disk segment length seg_len only against the workspace cbuf size, not against the compressed input size (compressed_len, the total folio bytes of the bio). A crafted extent can carry a segment whose seg_len passes the cbuf check but runs past the end of the bio, so copy_compressed_segment() walks off the last folio: get_current_folio() then returns the NULL folio from bio_next_folio(), and with CONFIG_BTRFS_ASSERT disabled (default) folio_size(NULL) faults. BUG: KASAN: null-ptr-deref in lzo_decompress_bio (fs/btrfs/lzo.c:383) Read of size 8 at addr 0000000000000000 by task kworker/u8:1/29 Workqueue: btrfs-endio simple_end_io_work kasan_report (mm/kasan/report.c:590) lzo_decompress_bio (fs/btrfs/lzo.c:383) end_bbio_compressed_read (fs/btrfs/compression.c:1065) btrfs_bio_end_io (fs/btrfs/bio.c:1
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-80631 is a buffer overflow vulnerability in the Linux kernel's btrfs LZO decompression function that allows a crafted extent to cause a read past the end of allocated memory. The vulnerability exists because lzo_decompress_bio() validates segment length (seg_len) only against the decompression workspace buffer size, not against the actual compressed input size. An attacker can craft a malicious btrfs filesystem with a segment whose length passes the workspace validation but extends beyond the compressed data, causing the copy_compressed_segment() function to read into adjacent memory. This affects any system using btrfs with LZO compression, particularly those processing untrusted filesystem images, and could lead to information disclosure or denial of service.
While CVE-2026-80631 lacks mapped MITRE ATT&CK techniques and CWE classification, Casky's AI-driven analysis would identify this as a memory safety violation pattern relevant to Exploitation of Vulnerability (T1190) and potentially Local Privilege Escalation (T1548) if chained with kernel exploitation techniques. Practitioners using Casky would observe detection signals around: (1) Anomalous buffer access patterns during filesystem decompression operations, (2) Crafted filesystem metadata that violates expected compression segment boundaries, and (3) Kernel memory access violations originating from btrfs subsystem calls. Security teams monitoring btrfs filesystem operations would see these patterns manifest as kernel warnings, out-of-bounds access attempts, or unexpected memory reads during LZO decompression processing—particularly when processing filesystems from untrusted sources.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-80631. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation