CVE-2026-74357: Software Security Vulnerability Vulnerability
HIGHCVE-2026-74357 is a HIGH (CVSS 7.8) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.
CVE-2026-74357 at a Glance
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).
How to Fix CVE-2026-74357
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.
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-74357, 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
References
Frequently Asked Questions
What is CVE-2026-74357?
Which Software versions are affected?
What version fixes CVE-2026-74357?
What is the CVSS score of CVE-2026-74357?
What CWE is associated with CVE-2026-74357?
How can I check Maven dependencies for CVE-2026-74357?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-rf2r-54vm-qv57",
"modified" : "2026-08-17T06:33:40Z",
"published" : "2026-08-15T06:32:31Z",
"aliases" : [ "CVE-2026-74357" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix KASAN slab-out-of-bounds in amdgpu_coredump ring dump\n\nThe ring content dump in amdgpu_coredump() uses two separate loops over\nadev->rings[]: the first counts rings with unsignalled fences to size\nthe allocation, and the second copies ring data into the allocated\nbuffers.\n\nBoth loops use the same condition to skip rings:\n\n atomic_read(&ring->fence_drv.last_seq) == ring->fence_drv.sync_seq\n\nBecause last_seq is an atomic that is updated concurrently by the fence\nsignalling path, additional rings may appear unsignalled in the second\nloop that were signalled during the first. When this happens, idx\nexceeds the allocated ring_count and the store to coredump->rings[idx]\nwrites past the end of the kcalloc-ed buffer.\n\nThis was found during IGT stressful test amd_queue_reset which\ntriggers random GPU resets. The OVERSIZE subtest\n(CMD_STREAM_EXEC_INVALID_PACKET_LENGTH_OVERSIZE on GFX ring) provokes\na ring timeout and subsequent coredump, which hits the race between\nthe counting and copying loops. The failure is non-deterministic and\ndepends on fence signalling timing during the reset.\n\nKASAN log:\n\n BUG: KASAN: slab-out-of-bounds in amdgpu_coredump+0x1274/0x12f0 [amdgpu]\n Write of size 4 at addr ffff888106154258 by task kworker/u128:5/23625\n CPU: 16 UID: 0 PID: 23625 Comm: kworker/u128:5 Not tainted 6.19.0+ #35\n Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched]\n Call Trace:\n <TASK>\n dump_stack_lvl+0xa5/0x110\n print_report+0xd1/0x660\n kasan_report+0xf3/0x130\n __asan_report_store4_noabort+0x17/0x30\n amdgpu_coredump+0x1274/0x12f0 [amdgpu]\n amdgpu_job_timedout+0xef0/0x16c0 [amdgpu]\n drm_sched_job_timedout+0x194/0x5c0 [gpu_sched]\n process_one_work+0x84b/0x1990\n worker_thread+0x6b8/0x11b0\n </TASK>\n\n Allocated by task 23625:\n kasan_save_stack+0x39/0x70\n __kasan_kmalloc+0xc3/0xd0\n __kmalloc_noprof+0x2ec/0x910\n amdgpu_coredump+0x5c5/0x12f0 [amdgpu]\n amdgpu_job_timedout+0xef0/0x16c0 [amdgpu]\n\n The buggy address belongs to the object at ffff888106154200\n which belongs to the cache kmalloc-rnd-09-96 of size 96\n The buggy address is located 16 bytes to the right of\n allocated 72-byte region [ffff888106154200, ffff888106154248)\n\n72 bytes = 3 * sizeof(struct amdgpu_coredump_ring), so ring_count was 3\nbut idx reached 3+, writing ring_index (at struct offset 16) 16 bytes\npast the allocation.\n\nFix by adding an idx < ring_count guard to the copy loop so it cannot\nexceed the allocated count even when the fence state changes between\nthe two passes.",
"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-74357"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/08ac3a7879d300302a1927ce2038629539a37f8b"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/efb1dadaeb897b22b9e118d398d0f41e70e9ccca"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : "HIGH",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-15T06:22:37Z"
}
}