CVE-2026-68167: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-rgmh-vxfr-qmw9
Share
Published
Advisory Summary

CVE-2026-68167 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-68167 at a Glance

CVE Identifier CVE-2026-68167
GHSA Identifier GHSA-rgmh-vxfr-qmw9
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-68167

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-68167, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In the Linux kernel, the following vulnerability has been resolved: btrfs: do not try compression for data reloc inodes [BUG] There is a syzbot report that the check inside get_new_location() triggered: BTRFS info (device loop0): found 31 extents, stage: move data extents BTRFS info (device loop0): leaf 8908800 gen 16 total ptrs 28 free space 1676 owner 18446744073709551607 item 0 key (256 INODE_ITEM 0) itemoff 3835 itemsize 160 inode generation 5 transid 0 size 0 nbytes 0 block group 0 mode 40755 links 1 uid 0 gid 0 rdev 0 sequence 0 flags 0x0 atime 1669132761.0 ctime 1669132761.0 mtime 1669132761.0 otime 0.0 item 1 key (256 INODE_REF 256) itemoff 3823 itemsize 12 index 0 name_len 2 item 2 key (258 INODE_ITEM 0) itemoff 3663 itemsize 160 inode generation 1 transid 16 size 733184 nbytes 106496 block group 0 mode 100600 links 0 uid 0 gid 0 rdev 0 sequence 24 flags 0x18 item 3 key (258 EXTENT_DATA 0) itemoff 3595 itemsize 68 generation 16 type 0 inline extent data size 47 ram_bytes 4096 compression 1 [...] item 27 key (18446744073709551611 ORPHAN_ITEM 258) itemoff 2376 itemsize 0 BTRFS error (device loop0): unexpected non-zero offset in file extent item for data reloc inode 258 key offset 0 offset 9277520992061368337 ------------[ cut here ]------------ btrfs_abort_should_print_stack(__error) [CAUSE] The above dump tree shows the first file extent item is inlined, which should make no sense for data reloc inodes, as such inodes just represent where the data extents are in the relocation destination chunk. However the relocation path preallocates space for each block, then dirties them, cluster by cluster. It's possible to have a single block at the beginning of the block group, and no other block in the same cluster. So relocation will preallocate a file extent for that block and dirty the first block. Then memory pressure forces the data reloc inode to be written back, before any other blocks are dirtied/allocated. Finally commit 3eaf5f082c4c ("btrfs: extract inlined creation into a dedicated delalloc helper") changed the sequence of delalloc. Before that commit we always tried NOCOW first, so that dirtied block would be written back into the preallocated space, and appear as a regular extent. But with that commit, we always try inline first, and since compression is forced, we try compressing the first block, and then inline the compressed data, resulting in the above inlined file extent in the data reloc tree. Then the check in get_new_location() will check the file offset, without checking if the file extent is inlined or not, resulting in the above failure. [FIX] Do not allow compression for data reloc inodes. Since data reloc inode sizes are always block aligned, as long as we do not compress, @data_len will always be at least one block, and that will cause can_cow_file_range_inline() to return false, thus no inlined extent will be created.

References

NVD — CVE-2026-68167 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68167
git.kernel.org/stable/c/31a62e4ad6... WEB
https://git.kernel.org/stable/c/31a62e4ad66313cf1ebaa00c2a17d644a4b87d22
git.kernel.org/stable/c/ae4316f332... WEB
https://git.kernel.org/stable/c/ae4316f332e03e628712e9dfb89f2b7d3c70c21a

Frequently Asked Questions

What is CVE-2026-68167?
CVE-2026-68167 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-68167?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-68167?
CVE-2026-68167 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-68167?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rgmh-vxfr-qmw9",
  "modified" : "2026-08-10T15:33:39Z",
  "published" : "2026-08-10T15:33:38Z",
  "aliases" : [ "CVE-2026-68167" ],
  "details" : "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.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68167"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/31a62e4ad66313cf1ebaa00c2a17d644a4b87d22"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ae4316f332e03e628712e9dfb89f2b7d3c70c21a"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-10T13:20:03Z"
  }
}