{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68167 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68167 is a denial of service vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-68167 and fix it if it is affected.\n\nWhat it is: CVE-2026-68167 is a denial of service vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-68167 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-68167/ (Markdown: https://insights.sbomify.com/CVE-2026-68167/index.md)","id":"CVE-2026-68167","markdown":"https://insights.sbomify.com/CVE-2026-68167/index.md","name":"CVE-2026-68167","record":{"aliases":["DEBIAN-CVE-2026-68167","GHSA-rgmh-vxfr-qmw9","UBUNTU-CVE-2026-68167"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A flaw in the Linux kernel's Btrfs filesystem can cause a kernel panic during data relocation, leading to a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: do not try compression for data reloc inodes\n\n[BUG]\nThere is a syzbot report that the check inside get_new_location()\ntriggered:\n\n  BTRFS info (device loop0): found 31 extents, stage: move data extents\n  BTRFS info (device loop0): leaf 8908800 gen 16 total ptrs 28 free space 1676 owner 18446744073709551607\n         item 0 key (256 INODE_ITEM 0) itemoff 3835 itemsize 160\n                 inode generation 5 transid 0 size 0 nbytes 0\n                 block group 0 mode 40755 links 1 uid 0 gid 0\n                 rdev 0 sequence 0 flags 0x0\n                 atime 1669132761.0\n                 ctime 1669132761.0\n                 mtime 1669132761.0\n                 otime 0.0\n         item 1 key (256 INODE_REF 256) itemoff 3823 itemsize 12\n                 index 0 name_len 2\n         item 2 key (258 INODE_ITEM 0) itemoff 3663 itemsize 160\n                 inode generation 1 transid 16 size 733184 nbytes 106496\n                 block group 0 mode 100600 links 0 uid 0 gid 0\n                 rdev 0 sequence 24 flags 0x18\n         item 3 key (258 EXTENT_DATA 0) itemoff 3595 itemsize 68\n                 generation 16 type 0\n                 inline extent data size 47 ram_bytes 4096 compression 1\n  [...]\n         item 27 key (18446744073709551611 ORPHAN_ITEM 258) itemoff 2376 itemsize 0\n  BTRFS error (device loop0): unexpected non-zero offset in file extent item for data reloc inode 258 key offset 0 offset 9277520992061368337\n  ------------[ cut here ]------------\n  btrfs_abort_should_print_stack(__error)\n\n[CAUSE]\nThe above dump tree shows the first file extent item is inlined, which\nshould make no sense for data reloc inodes, as such inodes just\nrepresent where the data extents are in the relocation destination chunk.\n\nHowever the relocation path preallocates space for each block,\nthen dirties them, cluster by cluster.\nIt's possible to have a single block at the beginning of the block\ngroup, and no other block in the same cluster.\n\nSo relocation will preallocate a file extent for that block and dirty\nthe first block.  Then memory pressure forces the data reloc inode to be\nwritten back, before any other blocks are dirtied/allocated.\n\nFinally commit 3eaf5f082c4c (\"btrfs: extract inlined creation into a dedicated\ndelalloc helper\") changed the sequence of delalloc. Before that commit we\nalways tried NOCOW first, so that dirtied block would be written back into\nthe preallocated space, and appear as a regular extent.\n\nBut with that commit, we always try inline first, and since compression\nis forced, we try compressing the first block, and then inline the\ncompressed data, resulting in the above inlined file extent in the data\nreloc tree.\n\nThen the check in get_new_location() will check the file offset, without\nchecking if the file extent is inlined or not, resulting in the above\nfailure.\n\n[FIX]\nDo not allow compression for data reloc inodes.\n\nSince data reloc inode sizes are always block aligned, as long as we do\nnot compress, @data_len will always be at least one block, and\nthat will cause can_cow_file_range_inline() to return false, thus no\ninlined extent will be created.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"btrfs: do not try compression for data reloc inodes","id":"CVE-2026-68167","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"afs: Fix afs_edit_dir_remove() to get, not find, block 0","id":"CVE-2026-68168"},"packages":[],"prev":{"headline":"userfaultfd: prevent registration of special VMAs","id":"CVE-2026-68166"},"products":["Linux"],"published":"2026-08-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A flaw in the Linux kernel's Btrfs filesystem can cause a kernel panic during data relocation, leading to a denial of service.","url":"https://insights.sbomify.com/CVE-2026-68167/"}