CVE-2026-43285: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-v2vh-p96v-7cc2
Share
CVSS 5.5
Published
Advisory Summary

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

CVE-2026-43285 at a Glance

CVE Identifier CVE-2026-43285
GHSA Identifier GHSA-v2vh-p96v-7cc2
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification General Security Weakness
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-43285

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-43285, 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: mm/slab: do not access current->mems_allowed_seq if !allow_spin Lockdep complains when get_from_any_partial() is called in an NMI context, because current->mems_allowed_seq is seqcount_spinlock_t and not NMI-safe: ================================ WARNING: inconsistent lock state 6.19.0-rc5-kfree-rcu+ #315 Tainted: G N -------------------------------- inconsistent {INITIAL USE} -> {IN-NMI} usage. kunit_try_catch/9989 [HC1[1]:SC0[0]:HE0:SE1] takes: ffff889085799820 (&____s->seqcount#3){.-.-}-{0:0}, at: ___slab_alloc+0x58f/0xc00 {INITIAL USE} state was registered at: lock_acquire+0x185/0x320 kernel_init_freeable+0x391/0x1150 kernel_init+0x1f/0x220 ret_from_fork+0x736/0x8f0 ret_from_fork_asm+0x1a/0x30 irq event stamp: 56 hardirqs last enabled at (55): [<ffffffff850a68d7>] _raw_spin_unlock_irq+0x27/0x70 hardirqs last disabled at (56): [<ffffffff850858ca>] __schedule+0x2a8a/0x6630 softirqs last enabled at (0): [<ffffffff81536711>] copy_process+0x1dc1/0x6a10 softirqs last disabled at (0): [<0000000000000000>] 0x0 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&____s->seqcount#3); <Interrupt> lock(&____s->seqcount#3); *** DEADLOCK *** According to Documentation/locking/seqlock.rst, seqcount_t is not NMI-safe and seqcount_latch_t should be used when read path can interrupt the write-side critical section. In this case, do not access current->mems_allowed_seq and avoid retry.

References

NVD — CVE-2026-43285 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-43285
git.kernel.org/stable/c/144080a582... WEB
https://git.kernel.org/stable/c/144080a5823b2dbd635acb6decf7ab23182664f3
git.kernel.org/stable/c/353dd99344... WEB
https://git.kernel.org/stable/c/353dd9934447b9193643ae1afd938607a74d4915
git.kernel.org/stable/c/efd767ddce... WEB
https://git.kernel.org/stable/c/efd767ddcef0669bbd33c6a823ea0a88f06d4b29

Frequently Asked Questions

What is CVE-2026-43285?
CVE-2026-43285 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-43285?
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-43285?
CVE-2026-43285 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-43285?
CVE-2026-43285 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-43285?
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-v2vh-p96v-7cc2",
  "modified" : "2026-05-14T21:30:37Z",
  "published" : "2026-05-08T15:31:22Z",
  "aliases" : [ "CVE-2026-43285" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/slab: do not access current->mems_allowed_seq if !allow_spin\n\nLockdep complains when get_from_any_partial() is called in an NMI\ncontext, because current->mems_allowed_seq is seqcount_spinlock_t and\nnot NMI-safe:\n\n  ================================\n  WARNING: inconsistent lock state\n  6.19.0-rc5-kfree-rcu+ #315 Tainted: G                 N\n  --------------------------------\n  inconsistent {INITIAL USE} -> {IN-NMI} usage.\n  kunit_try_catch/9989 [HC1[1]:SC0[0]:HE0:SE1] takes:\n  ffff889085799820 (&____s->seqcount#3){.-.-}-{0:0}, at: ___slab_alloc+0x58f/0xc00\n  {INITIAL USE} state was registered at:\n    lock_acquire+0x185/0x320\n    kernel_init_freeable+0x391/0x1150\n    kernel_init+0x1f/0x220\n    ret_from_fork+0x736/0x8f0\n    ret_from_fork_asm+0x1a/0x30\n  irq event stamp: 56\n  hardirqs last  enabled at (55): [<ffffffff850a68d7>] _raw_spin_unlock_irq+0x27/0x70\n  hardirqs last disabled at (56): [<ffffffff850858ca>] __schedule+0x2a8a/0x6630\n  softirqs last  enabled at (0): [<ffffffff81536711>] copy_process+0x1dc1/0x6a10\n  softirqs last disabled at (0): [<0000000000000000>] 0x0\n\n  other info that might help us debug this:\n   Possible unsafe locking scenario:\n\n         CPU0\n         ----\n    lock(&____s->seqcount#3);\n    <Interrupt>\n      lock(&____s->seqcount#3);\n\n   *** DEADLOCK ***\n\nAccording to Documentation/locking/seqlock.rst, seqcount_t is not\nNMI-safe and seqcount_latch_t should be used when read path can interrupt\nthe write-side critical section. In this case, do not access\ncurrent->mems_allowed_seq and avoid retry.",
  "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-43285"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/144080a5823b2dbd635acb6decf7ab23182664f3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/353dd9934447b9193643ae1afd938607a74d4915"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/efd767ddcef0669bbd33c6a823ea0a88f06d4b29"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-05-08T14:16:35Z"
  }
}