CVE-2025-40128: Software Security Vulnerability Vulnerability

UNKNOWN

Advisory Identifier: GHSA-7vqf-5393-q6gv

Published 2025-11-12

Advisory Summary

CVE-2025-40128 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-2025-40128 at a Glance

CVE Identifier CVE-2025-40128

GHSA Identifier GHSA-7vqf-5393-q6gv

Severity N/A

CVSS v3.1 Base Score N/A

CWE Classification General Security Weakness

Affected Product Software

Package Ecosystem Maven

Published Date 2025-11-12

Last Updated 2025-11-12

How to Fix CVE-2025-40128

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-2025-40128, 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: fix symbolic link reading when bs > ps [BUG DURING BS > PS TEST] When running the following script on a btrfs whose block size is larger than page size, e.g. 8K block size and 4K page size, it will trigger a kernel BUG: # mkfs.btrfs -s 8k $dev # mount $dev $mnt # mkdir $mnt/dir # ln -s dir $mnt/link # ls $mnt/link The call trace looks like this: BTRFS warning (device dm-2): support for block size 8192 with page size 4096 is experimental, some features may be missing BTRFS info (device dm-2): checking UUID tree BTRFS info (device dm-2): enabling ssd optimizations BTRFS info (device dm-2): enabling free space tree ------------[ cut here ]------------ kernel BUG at /home/adam/linux/include/linux/highmem.h:275! Oops: invalid opcode: 0000 [#1] SMP CPU: 8 UID: 0 PID: 667 Comm: ls Tainted: G OE 6.17.0-rc4-custom+ #283 PREEMPT(full) Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS unknown 02/02/2022 RIP: 0010:zero_user_segments.constprop.0+0xdc/0xe0 [btrfs] Call Trace: <TASK> btrfs_get_extent.cold+0x85/0x101 [btrfs 7453c70c03e631c8d8bfdd4264fa62d3e238da6f] btrfs_do_readpage+0x244/0x750 [btrfs 7453c70c03e631c8d8bfdd4264fa62d3e238da6f] btrfs_read_folio+0x9c/0x100 [btrfs 7453c70c03e631c8d8bfdd4264fa62d3e238da6f] filemap_read_folio+0x37/0xe0 do_read_cache_folio+0x94/0x3e0 __page_get_link.isra.0+0x20/0x90 page_get_link+0x16/0x40 step_into+0x69b/0x830 path_lookupat+0xa7/0x170 filename_lookup+0xf7/0x200 ? set_ptes.isra.0+0x36/0x70 vfs_statx+0x7a/0x160 do_statx+0x63/0xa0 __x64_sys_statx+0x90/0xe0 do_syscall_64+0x82/0xae0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 </TASK> Please note bs > ps support is still under development and the enablement patch is not even in btrfs development branch. [CAUSE] Btrfs reuses its data folio read path to handle symbolic links, as the symbolic link target is stored as an inline data extent. But for newly created inodes, btrfs only set the minimal order if the target inode is a regular file. Thus for above newly created symbolic link, it doesn't properly respect the minimal folio order, and triggered the above crash. [FIX] Call btrfs_set_inode_mapping_order() unconditionally inside btrfs_create_new_inode(). For symbolic links this will fix the crash as now the folio will meet the minimal order. For regular files this brings no change. For directory/bdev/char and all the other types of inodes, they won't go through the data read path, thus no effect either.

References

NVD — CVE-2025-40128 NVD

https://nvd.nist.gov/vuln/detail/CVE-2025-40128

git.kernel.org/stable/c/3ea252a5c4... WEB

https://git.kernel.org/stable/c/3ea252a5c48dd3a4e1f7d0c53d3b0f7b648becc9

git.kernel.org/stable/c/67378b7546... WEB

https://git.kernel.org/stable/c/67378b754608a3524d125bfa5744508a49fe48be

Frequently Asked Questions

What is CVE-2025-40128?

CVE-2025-40128 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-2025-40128?

Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.

What CWE is associated with CVE-2025-40128?

CVE-2025-40128 is classified under General Security Weakness.

How can I check Maven dependencies for CVE-2025-40128?

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-7vqf-5393-q6gv",
  "modified" : "2025-11-12T12:30:27Z",
  "published" : "2025-11-12T12:30:27Z",
  "aliases" : [ "CVE-2025-40128" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix symbolic link reading when bs > ps\n\n[BUG DURING BS > PS TEST]\nWhen running the following script on a btrfs whose block size is larger\nthan page size, e.g. 8K block size and 4K page size, it will trigger a\nkernel BUG:\n\n  # mkfs.btrfs -s 8k $dev\n  # mount $dev $mnt\n  # mkdir $mnt/dir\n  # ln -s dir $mnt/link\n  # ls $mnt/link\n\nThe call trace looks like this:\n\n  BTRFS warning (device dm-2): support for block size 8192 with page size 4096 is experimental, some features may be missing\n  BTRFS info (device dm-2): checking UUID tree\n  BTRFS info (device dm-2): enabling ssd optimizations\n  BTRFS info (device dm-2): enabling free space tree\n  ------------[ cut here ]------------\n  kernel BUG at /home/adam/linux/include/linux/highmem.h:275!\n  Oops: invalid opcode: 0000 [#1] SMP\n  CPU: 8 UID: 0 PID: 667 Comm: ls Tainted: G           OE       6.17.0-rc4-custom+ #283 PREEMPT(full)\n  Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS unknown 02/02/2022\n  RIP: 0010:zero_user_segments.constprop.0+0xdc/0xe0 [btrfs]\n  Call Trace:\n   <TASK>\n   btrfs_get_extent.cold+0x85/0x101 [btrfs 7453c70c03e631c8d8bfdd4264fa62d3e238da6f]\n   btrfs_do_readpage+0x244/0x750 [btrfs 7453c70c03e631c8d8bfdd4264fa62d3e238da6f]\n   btrfs_read_folio+0x9c/0x100 [btrfs 7453c70c03e631c8d8bfdd4264fa62d3e238da6f]\n   filemap_read_folio+0x37/0xe0\n   do_read_cache_folio+0x94/0x3e0\n   __page_get_link.isra.0+0x20/0x90\n   page_get_link+0x16/0x40\n   step_into+0x69b/0x830\n   path_lookupat+0xa7/0x170\n   filename_lookup+0xf7/0x200\n   ? set_ptes.isra.0+0x36/0x70\n   vfs_statx+0x7a/0x160\n   do_statx+0x63/0xa0\n   __x64_sys_statx+0x90/0xe0\n   do_syscall_64+0x82/0xae0\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   </TASK>\n\nPlease note bs > ps support is still under development and the\nenablement patch is not even in btrfs development branch.\n\n[CAUSE]\nBtrfs reuses its data folio read path to handle symbolic links, as the\nsymbolic link target is stored as an inline data extent.\n\nBut for newly created inodes, btrfs only set the minimal order if the\ntarget inode is a regular file.\n\nThus for above newly created symbolic link, it doesn't properly respect\nthe minimal folio order, and triggered the above crash.\n\n[FIX]\nCall btrfs_set_inode_mapping_order() unconditionally inside\nbtrfs_create_new_inode().\n\nFor symbolic links this will fix the crash as now the folio will meet\nthe minimal order.\n\nFor regular files this brings no change.\n\nFor directory/bdev/char and all the other types of inodes, they won't\ngo through the data read path, thus no effect either.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-40128"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3ea252a5c48dd3a4e1f7d0c53d3b0f7b648becc9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/67378b754608a3524d125bfa5744508a49fe48be"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2025-11-12T11:15:42Z"
  }
}

Advisory Metadata

Source ID: GHSA-7vqf-5393-q6gv
Schema Version: 1.4.0
Published: 2025-11-12 12:30
Last Modified: 2025-11-12 12:30
Database Record File: advisories/unreviewed/2025/11/GHSA-7vqf-5393-q6gv/GHSA-7vqf-5393-q6gv.json