CVE-2026-46050: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-7v6r-2w32-rrq7
Share
CVSS 5.5
CWE-667
Published
Advisory Summary

CVE-2026-46050 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (CWE-667: Improper Locking) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-46050 at a Glance

CVE Identifier CVE-2026-46050
GHSA Identifier GHSA-7v6r-2w32-rrq7
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-667: Improper Locking
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

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:N/I:N/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 None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-46050

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-46050, 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-667: Improper Locking, where the product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. 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: md/raid10: fix deadlock with check operation and nowait requests When an array check is running it will raise the barrier at which point normal requests will become blocked and increment the nr_pending value to signal there is work pending inside of wait_barrier(). NOWAIT requests do not block and so will return immediately with an error, and additionally do not increment nr_pending in wait_barrier(). Upstream change commit 43806c3d5b9b ("raid10: cleanup memleak at raid10_make_request") added a call to raid_end_bio_io() to fix a memory leak when NOWAIT requests hit this condition. raid_end_bio_io() eventually calls allow_barrier() and it will unconditionally do an atomic_dec_and_test(&conf->nr_pending) even though the corresponding increment on nr_pending didn't happen in the NOWAIT case. This can be easily seen by starting a check operation while an application is doing nowait IO on the same array. This results in a deadlocked state due to nr_pending value underflowing and so the md resync thread gets stuck waiting for nr_pending to == 0. Output of r10conf state of the array when we hit this condition: crash> struct r10conf barrier = 1, nr_pending = { counter = -41 }, nr_waiting = 15, nr_queued = 0, Example of md_sync thread stuck waiting on raise_barrier() and other requests stuck in wait_barrier(): md1_resync [<0>] raise_barrier+0xce/0x1c0 [<0>] raid10_sync_request+0x1ca/0x1ed0 [<0>] md_do_sync+0x779/0x1110 [<0>] md_thread+0x90/0x160 [<0>] kthread+0xbe/0xf0 [<0>] ret_from_fork+0x34/0x50 [<0>] ret_from_fork_asm+0x1a/0x30 kworker/u1040:2+flush-253:4 [<0>] wait_barrier+0x1de/0x220 [<0>] regular_request_wait+0x30/0x180 [<0>] raid10_make_request+0x261/0x1000 [<0>] md_handle_request+0x13b/0x230 [<0>] __submit_bio+0x107/0x1f0 [<0>] submit_bio_noacct_nocheck+0x16f/0x390 [<0>] ext4_io_submit+0x24/0x40 [<0>] ext4_do_writepages+0x254/0xc80 [<0>] ext4_writepages+0x84/0x120 [<0>] do_writepages+0x7a/0x260 [<0>] __writeback_single_inode+0x3d/0x300 [<0>] writeback_sb_inodes+0x1dd/0x470 [<0>] __writeback_inodes_wb+0x4c/0xe0 [<0>] wb_writeback+0x18b/0x2d0 [<0>] wb_workfn+0x2a1/0x400 [<0>] process_one_work+0x149/0x330 [<0>] worker_thread+0x2d2/0x410 [<0>] kthread+0xbe/0xf0 [<0>] ret_from_fork+0x34/0x50 [<0>] ret_from_fork_asm+0x1a/0x30

References

NVD — CVE-2026-46050 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-46050
cert-portal.siemens.com/productcert/html/ss... WEB
https://cert-portal.siemens.com/productcert/html/ssa-784472.html
git.kernel.org/stable/c/1cdff2937c... WEB
https://git.kernel.org/stable/c/1cdff2937c618f81058422bbdc4974a3e7ec9379
git.kernel.org/stable/c/2249983d97... WEB
https://git.kernel.org/stable/c/2249983d971e6839b36284e6610390b2c217dfa1
git.kernel.org/stable/c/42fe37c901... WEB
https://git.kernel.org/stable/c/42fe37c90184cd1568838b84b488934c3671c963
git.kernel.org/stable/c/7d96f3120a... WEB
https://git.kernel.org/stable/c/7d96f3120a7fb7210d21b520c5b6f495da6ba436
git.kernel.org/stable/c/965d6162dd... WEB
https://git.kernel.org/stable/c/965d6162dd88cc7cc193cf7f5bfc132d8bbf0523
git.kernel.org/stable/c/ae356d5eb1... WEB
https://git.kernel.org/stable/c/ae356d5eb1331d678985799f893e436314834a87
git.kernel.org/stable/c/cac2106bb9... WEB
https://git.kernel.org/stable/c/cac2106bb9a2180b288079b49ed626414fb5bc45

Frequently Asked Questions

What is CVE-2026-46050?
CVE-2026-46050 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-667: Improper Locking.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-46050?
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-46050?
CVE-2026-46050 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-46050?
CVE-2026-46050 is classified under CWE-667: Improper Locking (The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.).
How can I check Maven dependencies for CVE-2026-46050?
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-7v6r-2w32-rrq7",
  "modified" : "2026-10-15T03:35:58Z",
  "published" : "2026-05-27T15:33:22Z",
  "aliases" : [ "CVE-2026-46050" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmd/raid10: fix deadlock with check operation and nowait requests\n\nWhen an array check is running it will raise the barrier at which point\nnormal requests will become blocked and increment the nr_pending value to\nsignal there is work pending inside of wait_barrier(). NOWAIT requests\ndo not block and so will return immediately with an error, and additionally\ndo not increment nr_pending in wait_barrier(). Upstream change commit\n43806c3d5b9b (\"raid10: cleanup memleak at raid10_make_request\") added a\ncall to raid_end_bio_io() to fix a memory leak when NOWAIT requests hit\nthis condition. raid_end_bio_io() eventually calls allow_barrier() and\nit will unconditionally do an atomic_dec_and_test(&conf->nr_pending) even\nthough the corresponding increment on nr_pending didn't happen in the\nNOWAIT case.\n\nThis can be easily seen by starting a check operation while an application\nis doing nowait IO on the same array. This results in a deadlocked state\ndue to nr_pending value underflowing and so the md resync thread gets stuck\nwaiting for nr_pending to == 0.\n\nOutput of r10conf state of the array when we hit this condition:\n\ncrash> struct r10conf\n\tbarrier = 1,\n        nr_pending = {\n          counter = -41\n        },\n        nr_waiting = 15,\n        nr_queued = 0,\n\nExample of md_sync thread stuck waiting on raise_barrier() and other\nrequests stuck in wait_barrier():\n\nmd1_resync\n[<0>] raise_barrier+0xce/0x1c0\n[<0>] raid10_sync_request+0x1ca/0x1ed0\n[<0>] md_do_sync+0x779/0x1110\n[<0>] md_thread+0x90/0x160\n[<0>] kthread+0xbe/0xf0\n[<0>] ret_from_fork+0x34/0x50\n[<0>] ret_from_fork_asm+0x1a/0x30\n\nkworker/u1040:2+flush-253:4\n[<0>] wait_barrier+0x1de/0x220\n[<0>] regular_request_wait+0x30/0x180\n[<0>] raid10_make_request+0x261/0x1000\n[<0>] md_handle_request+0x13b/0x230\n[<0>] __submit_bio+0x107/0x1f0\n[<0>] submit_bio_noacct_nocheck+0x16f/0x390\n[<0>] ext4_io_submit+0x24/0x40\n[<0>] ext4_do_writepages+0x254/0xc80\n[<0>] ext4_writepages+0x84/0x120\n[<0>] do_writepages+0x7a/0x260\n[<0>] __writeback_single_inode+0x3d/0x300\n[<0>] writeback_sb_inodes+0x1dd/0x470\n[<0>] __writeback_inodes_wb+0x4c/0xe0\n[<0>] wb_writeback+0x18b/0x2d0\n[<0>] wb_workfn+0x2a1/0x400\n[<0>] process_one_work+0x149/0x330\n[<0>] worker_thread+0x2d2/0x410\n[<0>] kthread+0xbe/0xf0\n[<0>] ret_from_fork+0x34/0x50\n[<0>] ret_from_fork_asm+0x1a/0x30",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-46050"
  }, {
    "type" : "WEB",
    "url" : "https://cert-portal.siemens.com/productcert/html/ssa-784472.html"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1cdff2937c618f81058422bbdc4974a3e7ec9379"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2249983d971e6839b36284e6610390b2c217dfa1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/42fe37c90184cd1568838b84b488934c3671c963"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7d96f3120a7fb7210d21b520c5b6f495da6ba436"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/965d6162dd88cc7cc193cf7f5bfc132d8bbf0523"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ae356d5eb1331d678985799f893e436314834a87"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cac2106bb9a2180b288079b49ed626414fb5bc45"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-667" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-05-27T14:17:24Z"
  }
}