CVE-2026-43012: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-x4q9-gx2x-rgxq
Share
CVSS 5.5
Published
Advisory Summary

CVE-2026-43012 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-43012 at a Glance

CVE Identifier CVE-2026-43012
GHSA Identifier GHSA-x4q9-gx2x-rgxq
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-43012

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-43012, 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: net/mlx5: Fix switchdev mode rollback in case of failure If for some internal reason switchdev mode fails, we rollback to legacy mode, before this patch, rollback will unregister the uplink netdev and leave it unregistered causing the below kernel bug. To fix this, we need to avoid netdev unregister by setting the proper rollback flag 'MLX5_PRIV_FLAGS_SWITCH_LEGACY' to indicate legacy mode. devlink (431) used greatest stack depth: 11048 bytes left mlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), \ necvfs(0), active vports(0) mlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload mlx5_core 0000:00:03.0: Loading uplink representor for vport 65535 mlx5_core 0000:00:03.0: mlx5_cmd_out_err:816:(pid 456): \ QUERY_HCA_CAP(0x100) op_mod(0x0) failed, \ status bad parameter(0x3), syndrome (0x3a3846), err(-22) mlx5_core 0000:00:03.0 enp0s3np0 (unregistered): Unloading uplink \ representor for vport 65535 ------------[ cut here ]------------ kernel BUG at net/core/dev.c:12070! Oops: invalid opcode: 0000 [#1] SMP NOPTI CPU: 2 UID: 0 PID: 456 Comm: devlink Not tainted 6.16.0-rc3+ \ #9 PREEMPT(voluntary) RIP: 0010:unregister_netdevice_many_notify+0x123/0xae0 ... Call Trace: [ 90.923094] unregister_netdevice_queue+0xad/0xf0 [ 90.923323] unregister_netdev+0x1c/0x40 [ 90.923522] mlx5e_vport_rep_unload+0x61/0xc6 [ 90.923736] esw_offloads_enable+0x8e6/0x920 [ 90.923947] mlx5_eswitch_enable_locked+0x349/0x430 [ 90.924182] ? is_mp_supported+0x57/0xb0 [ 90.924376] mlx5_devlink_eswitch_mode_set+0x167/0x350 [ 90.924628] devlink_nl_eswitch_set_doit+0x6f/0xf0 [ 90.924862] genl_family_rcv_msg_doit+0xe8/0x140 [ 90.925088] genl_rcv_msg+0x18b/0x290 [ 90.925269] ? __pfx_devlink_nl_pre_doit+0x10/0x10 [ 90.925506] ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10 [ 90.925766] ? __pfx_devlink_nl_post_doit+0x10/0x10 [ 90.926001] ? __pfx_genl_rcv_msg+0x10/0x10 [ 90.926206] netlink_rcv_skb+0x52/0x100 [ 90.926393] genl_rcv+0x28/0x40 [ 90.926557] netlink_unicast+0x27d/0x3d0 [ 90.926749] netlink_sendmsg+0x1f7/0x430 [ 90.926942] __sys_sendto+0x213/0x220 [ 90.927127] ? __sys_recvmsg+0x6a/0xd0 [ 90.927312] __x64_sys_sendto+0x24/0x30 [ 90.927504] do_syscall_64+0x50/0x1c0 [ 90.927687] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 90.927929] RIP: 0033:0x7f7d0363e047

References

NVD — CVE-2026-43012 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-43012
git.kernel.org/stable/c/2ebb13f3e8... WEB
https://git.kernel.org/stable/c/2ebb13f3e8be0b61f72425b34cce60c8b6ad1891
git.kernel.org/stable/c/403186400a... WEB
https://git.kernel.org/stable/c/403186400a1a6166efe7031edc549c15fee4723f
git.kernel.org/stable/c/4363698838... WEB
https://git.kernel.org/stable/c/4363698838b7ec6e8d85b179495889aa7e522f91
git.kernel.org/stable/c/e27153b2bd... WEB
https://git.kernel.org/stable/c/e27153b2bd6e6699b544ac4dfa35d167bed5e642

Frequently Asked Questions

What is CVE-2026-43012?
CVE-2026-43012 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-43012?
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-43012?
CVE-2026-43012 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-43012?
CVE-2026-43012 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-43012?
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-x4q9-gx2x-rgxq",
  "modified" : "2026-05-07T21:30:24Z",
  "published" : "2026-05-01T15:30:36Z",
  "aliases" : [ "CVE-2026-43012" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Fix switchdev mode rollback in case of failure\n\nIf for some internal reason switchdev mode fails, we rollback to legacy\nmode, before this patch, rollback will unregister the uplink netdev and\nleave it unregistered causing the below kernel bug.\n\nTo fix this, we need to avoid netdev unregister by setting the proper\nrollback flag 'MLX5_PRIV_FLAGS_SWITCH_LEGACY' to indicate legacy mode.\n\ndevlink (431) used greatest stack depth: 11048 bytes left\nmlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), \\\n\tnecvfs(0), active vports(0)\nmlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload\nmlx5_core 0000:00:03.0: Loading uplink representor for vport 65535\nmlx5_core 0000:00:03.0: mlx5_cmd_out_err:816:(pid 456): \\\n\tQUERY_HCA_CAP(0x100) op_mod(0x0) failed, \\\n\tstatus bad parameter(0x3), syndrome (0x3a3846), err(-22)\nmlx5_core 0000:00:03.0 enp0s3np0 (unregistered): Unloading uplink \\\n\trepresentor for vport 65535\n ------------[ cut here ]------------\nkernel BUG at net/core/dev.c:12070!\nOops: invalid opcode: 0000 [#1] SMP NOPTI\nCPU: 2 UID: 0 PID: 456 Comm: devlink Not tainted 6.16.0-rc3+ \\\n\t#9 PREEMPT(voluntary)\nRIP: 0010:unregister_netdevice_many_notify+0x123/0xae0\n...\nCall Trace:\n[   90.923094]  unregister_netdevice_queue+0xad/0xf0\n[   90.923323]  unregister_netdev+0x1c/0x40\n[   90.923522]  mlx5e_vport_rep_unload+0x61/0xc6\n[   90.923736]  esw_offloads_enable+0x8e6/0x920\n[   90.923947]  mlx5_eswitch_enable_locked+0x349/0x430\n[   90.924182]  ? is_mp_supported+0x57/0xb0\n[   90.924376]  mlx5_devlink_eswitch_mode_set+0x167/0x350\n[   90.924628]  devlink_nl_eswitch_set_doit+0x6f/0xf0\n[   90.924862]  genl_family_rcv_msg_doit+0xe8/0x140\n[   90.925088]  genl_rcv_msg+0x18b/0x290\n[   90.925269]  ? __pfx_devlink_nl_pre_doit+0x10/0x10\n[   90.925506]  ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10\n[   90.925766]  ? __pfx_devlink_nl_post_doit+0x10/0x10\n[   90.926001]  ? __pfx_genl_rcv_msg+0x10/0x10\n[   90.926206]  netlink_rcv_skb+0x52/0x100\n[   90.926393]  genl_rcv+0x28/0x40\n[   90.926557]  netlink_unicast+0x27d/0x3d0\n[   90.926749]  netlink_sendmsg+0x1f7/0x430\n[   90.926942]  __sys_sendto+0x213/0x220\n[   90.927127]  ? __sys_recvmsg+0x6a/0xd0\n[   90.927312]  __x64_sys_sendto+0x24/0x30\n[   90.927504]  do_syscall_64+0x50/0x1c0\n[   90.927687]  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n[   90.927929] RIP: 0033:0x7f7d0363e047",
  "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-43012"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2ebb13f3e8be0b61f72425b34cce60c8b6ad1891"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/403186400a1a6166efe7031edc549c15fee4723f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4363698838b7ec6e8d85b179495889aa7e522f91"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e27153b2bd6e6699b544ac4dfa35d167bed5e642"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-05-01T15:16:45Z"
  }
}