CVE-2026-68436: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-7q8m-jhfw-frrf
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-68436
GHSA Identifier GHSA-7q8m-jhfw-frrf
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-68436

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-68436, 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: drm/amd/display: use kvzalloc to allocate struct dc struct dc has grown large over time (most of it the two inlined dc_scratch_space copies) and now sits close to the page allocator's 4 MiB contiguous allocation limit. Its actual size is not fixed by the source alone, it also depends on the compiler and the .config, so it can easily cross 4 MiB, e.g. with a newer GCC or a config change. dc_create() allocates it with kzalloc(). Once struct dc exceeds 4 MiB the request is rounded up to order 11 (8 MiB), which is above MAX_PAGE_ORDER, so the page allocator warns and returns NULL. dc_create() then fails, DM init fails and amdgpu probe aborts with -EINVAL: WARNING: mm/page_alloc.c:5197 at __alloc_frozen_pages_noprof+0x2f9/0x380 dc_create+0x38/0x660 [amdgpu] amdgpu_dm_init+0x2d9/0x510 [amdgpu] dm_hw_init+0x1b/0x90 [amdgpu] amdgpu_device_init.cold+0x150d/0x1e13 [amdgpu] amdgpu_driver_load_kms+0x19/0x80 [amdgpu] amdgpu_pci_probe+0x1e2/0x4c0 [amdgpu] dc_create() then returns NULL and DM init fails, which aborts the whole GPU init and makes amdgpu probe fail with -EINVAL ("hw_init of IP block <dm> failed -22"), leaving the display unusable. The subsequent amdgpu_irq_put() warnings during teardown are just fallout of unwinding a half-initialized device. struct dc is a software-only bookkeeping structure that is never handed to hardware DMA and is only ever kept as an opaque pointer, so it does not require physically contiguous memory. Allocate it with kvzalloc() (and free it with kvfree()) so that the allocator can fall back to vmalloc() when a contiguous allocation of that size is not available, which also avoids the MAX_PAGE_ORDER warning entirely. v2: - Rebase to amd-staging-drm-next. (cherry picked from commit 991e0516a8072f2292681c6ae98a924ab0e32575)

References

NVD — CVE-2026-68436 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68436
git.kernel.org/stable/c/7505039015... WEB
https://git.kernel.org/stable/c/75050390151a14802be433c3856ddcb483cecd24
git.kernel.org/stable/c/c59a693fbd... WEB
https://git.kernel.org/stable/c/c59a693fbd213f8f27942509b48b1a4111fdd40d
git.kernel.org/stable/c/dbad70d40c... WEB
https://git.kernel.org/stable/c/dbad70d40cad9c5e7586953275287fe7531fb811

Frequently Asked Questions

What is CVE-2026-68436?
CVE-2026-68436 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-68436?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-68436?
CVE-2026-68436 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-68436?
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-7q8m-jhfw-frrf",
  "modified" : "2026-10-15T12:30:40Z",
  "published" : "2026-08-12T00:31:12Z",
  "aliases" : [ "CVE-2026-68436" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: use kvzalloc to allocate struct dc\n\nstruct dc has grown large over time (most of it the two inlined\ndc_scratch_space copies) and now sits close to the page allocator's 4 MiB\ncontiguous allocation limit. Its actual size is not fixed by the source\nalone, it also depends on the compiler and the .config, so it can easily\ncross 4 MiB, e.g. with a newer GCC or a config change.\n\ndc_create() allocates it with kzalloc(). Once struct dc exceeds 4 MiB the\nrequest is rounded up to order 11 (8 MiB), which is above MAX_PAGE_ORDER,\nso the page allocator warns and returns NULL. dc_create() then fails, DM\ninit fails and amdgpu probe aborts with -EINVAL:\n\n  WARNING: mm/page_alloc.c:5197 at __alloc_frozen_pages_noprof+0x2f9/0x380\n   dc_create+0x38/0x660 [amdgpu]\n   amdgpu_dm_init+0x2d9/0x510 [amdgpu]\n   dm_hw_init+0x1b/0x90 [amdgpu]\n   amdgpu_device_init.cold+0x150d/0x1e13 [amdgpu]\n   amdgpu_driver_load_kms+0x19/0x80 [amdgpu]\n   amdgpu_pci_probe+0x1e2/0x4c0 [amdgpu]\n\ndc_create() then returns NULL and DM init fails, which aborts the whole\nGPU init and makes amdgpu probe fail with -EINVAL (\"hw_init of IP block\n<dm> failed -22\"), leaving the display unusable. The subsequent\namdgpu_irq_put() warnings during teardown are just fallout of unwinding\na half-initialized device.\n\nstruct dc is a software-only bookkeeping structure that is never handed\nto hardware DMA and is only ever kept as an opaque pointer, so it does\nnot require physically contiguous memory. Allocate it with kvzalloc()\n(and free it with kvfree()) so that the allocator can fall back to\nvmalloc() when a contiguous allocation of that size is not available,\nwhich also avoids the MAX_PAGE_ORDER warning entirely.\n\nv2:\n - Rebase to amd-staging-drm-next.\n\n(cherry picked from commit 991e0516a8072f2292681c6ae98a924ab0e32575)",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68436"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/75050390151a14802be433c3856ddcb483cecd24"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c59a693fbd213f8f27942509b48b1a4111fdd40d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/dbad70d40cad9c5e7586953275287fe7531fb811"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-12T00:17:43Z"
  }
}