CVE-2026-31507: Software Security Vulnerability Vulnerability

HIGH

Advisory Identifier: GHSA-xf3q-f592-rmgx

CVSS 7.8

Published 2026-04-22

Advisory Summary

CVE-2026-31507 is a HIGH (CVSS 7.8) security vulnerability vulnerability (CWE-415: Double Free) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product calls free() twice on the same memory address.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-31507 at a Glance

CVE Identifier CVE-2026-31507

GHSA Identifier GHSA-xf3q-f592-rmgx

Severity HIGH

CVSS v3.1 Base Score 7.8

CWE Classification CWE-415: Double Free

Affected Product Software

Package Ecosystem Maven

Published Date 2026-04-22

Last Updated 2026-10-15

Security Impact

CVSS: 7.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)

Attack Complexity Low (AC:L)

Privileges Required Low (PR:L)

User Interaction None (UI:N)

Scope Unchanged (S:U)

Confidentiality High (C:H)

Integrity High (I:H)

Availability High (A:H)

How to Fix CVE-2026-31507

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-31507, 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 CWE-415: Double Free, where the product calls free() twice on the same memory address. 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: net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer smc_rx_splice() allocates one smc_spd_priv per pipe_buffer and stores the pointer in pipe_buffer.private. The pipe_buf_operations for these buffers used .get = generic_pipe_buf_get, which only increments the page reference count when tee(2) duplicates a pipe buffer. The smc_spd_priv pointer itself was not handled, so after tee() both the original and the cloned pipe_buffer share the same smc_spd_priv *. When both pipes are subsequently released, smc_rx_pipe_buf_release() is called twice against the same object: 1st call: kfree(priv) sock_put(sk) smc_rx_update_cons() [correct] 2nd call: kfree(priv) sock_put(sk) smc_rx_update_cons() [UAF] KASAN reports a slab-use-after-free in smc_rx_pipe_buf_release(), which then escalates to a NULL-pointer dereference and kernel panic via smc_rx_update_consumer() when it chases the freed priv->smc pointer: BUG: KASAN: slab-use-after-free in smc_rx_pipe_buf_release+0x78/0x2a0 Read of size 8 at addr ffff888004a45740 by task smc_splice_tee_/74 Call Trace: <TASK> dump_stack_lvl+0x53/0x70 print_report+0xce/0x650 kasan_report+0xc6/0x100 smc_rx_pipe_buf_release+0x78/0x2a0 free_pipe_info+0xd4/0x130 pipe_release+0x142/0x160 __fput+0x1c6/0x490 __x64_sys_close+0x4f/0x90 do_syscall_64+0xa6/0x1a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f </TASK> BUG: kernel NULL pointer dereference, address: 0000000000000020 RIP: 0010:smc_rx_update_consumer+0x8d/0x350 Call Trace: <TASK> smc_rx_pipe_buf_release+0x121/0x2a0 free_pipe_info+0xd4/0x130 pipe_release+0x142/0x160 __fput+0x1c6/0x490 __x64_sys_close+0x4f/0x90 do_syscall_64+0xa6/0x1a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f </TASK> Kernel panic - not syncing: Fatal exception Beyond the memory-safety problem, duplicating an SMC splice buffer is semantically questionable: smc_rx_update_cons() would advance the consumer cursor twice for the same data, corrupting receive-window accounting. A refcount on smc_spd_priv could fix the double-free, but the cursor-accounting issue would still need to be addressed separately. The .get callback is invoked by both tee(2) and splice_pipe_to_pipe() for partial transfers; both will now return -EFAULT. Users who need to duplicate SMC socket data must use a copy-based read path.

References

NVD — CVE-2026-31507 NVD

https://nvd.nist.gov/vuln/detail/CVE-2026-31507

cert-portal.siemens.com/productcert/html/ss... WEB

https://cert-portal.siemens.com/productcert/html/ssa-019113.html

cert-portal.siemens.com/productcert/html/ss... WEB

https://cert-portal.siemens.com/productcert/html/ssa-082556.html

cert-portal.siemens.com/productcert/html/ss... WEB

https://cert-portal.siemens.com/productcert/html/ssa-457936.html

git.kernel.org/stable/c/24dd586bb4... WEB

https://git.kernel.org/stable/c/24dd586bb4cbba1889a50abe74143817a095c1c9

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

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

git.kernel.org/stable/c/54c87a7301... WEB

https://git.kernel.org/stable/c/54c87a730157868543ebdfa0ecb21b4590ed23a5

git.kernel.org/stable/c/7bcb974c77... WEB

https://git.kernel.org/stable/c/7bcb974c771c863e8588cea0012ac204443a7126

git.kernel.org/stable/c/7e8916f46c... WEB

https://git.kernel.org/stable/c/7e8916f46c2f48607f907fd401590093753a6bc5

git.kernel.org/stable/c/81acbd345d... WEB

https://git.kernel.org/stable/c/81acbd345d405994875d419d43b319fee0b9ad62

git.kernel.org/stable/c/98ba5cb274... WEB

https://git.kernel.org/stable/c/98ba5cb274768146e25ffbfde47753652c1c20d3

git.kernel.org/stable/c/ae5575e660... WEB

https://git.kernel.org/stable/c/ae5575e660410c8d2c5d38fb28a0f37aea945676

Frequently Asked Questions

What is CVE-2026-31507?

CVE-2026-31507 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-415: Double Free.

Which Software versions are affected?

Affected versions include releases prior to current release patches.

What version fixes CVE-2026-31507?

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

What is the CVSS score of CVE-2026-31507?

CVE-2026-31507 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

What CWE is associated with CVE-2026-31507?

CVE-2026-31507 is classified under CWE-415: Double Free (The product calls free() twice on the same memory address.).

How can I check Maven dependencies for CVE-2026-31507?

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-xf3q-f592-rmgx",
  "modified" : "2026-10-15T03:35:37Z",
  "published" : "2026-04-22T15:31:43Z",
  "aliases" : [ "CVE-2026-31507" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer\n\nsmc_rx_splice() allocates one smc_spd_priv per pipe_buffer and stores\nthe pointer in pipe_buffer.private.  The pipe_buf_operations for these\nbuffers used .get = generic_pipe_buf_get, which only increments the page\nreference count when tee(2) duplicates a pipe buffer.  The smc_spd_priv\npointer itself was not handled, so after tee() both the original and the\ncloned pipe_buffer share the same smc_spd_priv *.\n\nWhen both pipes are subsequently released, smc_rx_pipe_buf_release() is\ncalled twice against the same object:\n\n  1st call: kfree(priv)  sock_put(sk)  smc_rx_update_cons()  [correct]\n  2nd call: kfree(priv)  sock_put(sk)  smc_rx_update_cons()  [UAF]\n\nKASAN reports a slab-use-after-free in smc_rx_pipe_buf_release(), which\nthen escalates to a NULL-pointer dereference and kernel panic via\nsmc_rx_update_consumer() when it chases the freed priv->smc pointer:\n\n  BUG: KASAN: slab-use-after-free in smc_rx_pipe_buf_release+0x78/0x2a0\n  Read of size 8 at addr ffff888004a45740 by task smc_splice_tee_/74\n  Call Trace:\n   <TASK>\n   dump_stack_lvl+0x53/0x70\n   print_report+0xce/0x650\n   kasan_report+0xc6/0x100\n   smc_rx_pipe_buf_release+0x78/0x2a0\n   free_pipe_info+0xd4/0x130\n   pipe_release+0x142/0x160\n   __fput+0x1c6/0x490\n   __x64_sys_close+0x4f/0x90\n   do_syscall_64+0xa6/0x1a0\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n   </TASK>\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000020\n  RIP: 0010:smc_rx_update_consumer+0x8d/0x350\n  Call Trace:\n   <TASK>\n   smc_rx_pipe_buf_release+0x121/0x2a0\n   free_pipe_info+0xd4/0x130\n   pipe_release+0x142/0x160\n   __fput+0x1c6/0x490\n   __x64_sys_close+0x4f/0x90\n   do_syscall_64+0xa6/0x1a0\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n   </TASK>\n  Kernel panic - not syncing: Fatal exception\n\nBeyond the memory-safety problem, duplicating an SMC splice buffer is\nsemantically questionable: smc_rx_update_cons() would advance the\nconsumer cursor twice for the same data, corrupting receive-window\naccounting.  A refcount on smc_spd_priv could fix the double-free, but\nthe cursor-accounting issue would still need to be addressed separately.\n\nThe .get callback is invoked by both tee(2) and splice_pipe_to_pipe()\nfor partial transfers; both will now return -EFAULT.  Users who need\nto duplicate SMC socket data must use a copy-based read path.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-31507"
  }, {
    "type" : "WEB",
    "url" : "https://cert-portal.siemens.com/productcert/html/ssa-019113.html"
  }, {
    "type" : "WEB",
    "url" : "https://cert-portal.siemens.com/productcert/html/ssa-082556.html"
  }, {
    "type" : "WEB",
    "url" : "https://cert-portal.siemens.com/productcert/html/ssa-457936.html"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/24dd586bb4cbba1889a50abe74143817a095c1c9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3cc76380fea749280c026f410af56a28aaac388a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/54c87a730157868543ebdfa0ecb21b4590ed23a5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7bcb974c771c863e8588cea0012ac204443a7126"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7e8916f46c2f48607f907fd401590093753a6bc5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/81acbd345d405994875d419d43b319fee0b9ad62"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/98ba5cb274768146e25ffbfde47753652c1c20d3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ae5575e660410c8d2c5d38fb28a0f37aea945676"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-415" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-04-22T14:16:49Z"
  }
}

CVSS V3

7.8 HIGH

Attack Vector Local (AV:L)

Attack Complexity Low (AC:L)

Privileges Required Low (PR:L)

User Interaction None (UI:N)

Scope Unchanged (S:U)

Confidentiality High (C:H)

Integrity High (I:H)

Availability High (A:H)

Vector String

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Advisory Metadata

Source ID: GHSA-xf3q-f592-rmgx
Schema Version: 1.4.0
Published: 2026-04-22 15:31
Last Modified: 2026-10-15 03:35
Database Record File: advisories/unreviewed/2026/04/GHSA-xf3q-f592-rmgx/GHSA-xf3q-f592-rmgx.json