CVE-2026-53283: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-gv9j-3945-3x3r
Share
CVSS 5.5
CWE-476
Published
Advisory Summary

CVE-2026-53283 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (CWE-476: NULL Pointer Dereference) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product dereferences a pointer that it expects to be valid but is null.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-53283 at a Glance

CVE Identifier CVE-2026-53283
GHSA Identifier GHSA-gv9j-3945-3x3r
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-476: NULL Pointer Dereference
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-53283

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-53283, 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-476: NULL Pointer Dereference, where the product dereferences a pointer that it expects to be valid but is null. 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: iommu/amd: Bounds-check devid in __rlookup_amd_iommu() iommu_device_register() walks every device on the PCI bus via bus_for_each_dev() and calls amd_iommu_probe_device() for each. The inlined check_device() path computes the device's sbdf, calls rlookup_amd_iommu() to find the owning IOMMU, and only afterwards verifies devid <= pci_seg->last_bdf. __rlookup_amd_iommu() indexes rlookup_table[devid] with no bounds check of its own, so for a PCI device whose BDF is not described by the IVRS, the lookup reads past the end of the allocation before the caller's bounds check can run. This was harmless before commit e874c666b15b ("iommu/amd: Change rlookup, irq_lookup, and alias to use kvalloc()"): the table was a zeroed page-order allocation, so the over-read returned NULL and the caller's NULL check skipped the device. After that commit the table is a tight kvcalloc() and the over-read returns adjacent slab contents, which check_device() then dereferences as a struct amd_iommu *, causing a boot-time GPF. Seen on Google Compute Engine ct6e VMs, where the virtualized IVRS describes only the four TPU endpoints 00:04.0-07.0; the gVNIC at 00:08.0 (devid 0x40) indexes 56 bytes past the 456-byte allocation, into the adjacent kmalloc-512 slab object: pci 0000:00:04.0: Adding to iommu group 0 pci 0000:00:05.0: Adding to iommu group 1 pci 0000:00:06.0: Adding to iommu group 2 pci 0000:00:07.0: Adding to iommu group 3 Oops: general protection fault, probably for non-canonical address 0x3a64695f78746382: 0000 [#1] SMP NOPTI CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.22 #1 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/06/2025 RIP: 0010:amd_iommu_probe_device+0x54/0x3a0 Call Trace: __iommu_probe_device+0x107/0x520 probe_iommu_group+0x29/0x50 bus_for_each_dev+0x7e/0xe0 iommu_device_register+0xc9/0x240 iommu_go_to_state+0x9c0/0x1c60 amd_iommu_init+0x14/0x40 pci_iommu_init+0x16/0x60 do_one_initcall+0x47/0x2f0 Guard the array access in __rlookup_amd_iommu(). With the fix applied on 6.18.22, the gVNIC at 00:08.0 is skipped cleanly and the VM boots.

References

NVD — CVE-2026-53283 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-53283
git.kernel.org/stable/c/07d0f496fe... WEB
https://git.kernel.org/stable/c/07d0f496fe7ec5abe3bee7e38be709521567bb33
git.kernel.org/stable/c/79db4cbab8... WEB
https://git.kernel.org/stable/c/79db4cbab81f07ce69a93d379ebd40d3709ecfb2
git.kernel.org/stable/c/f0a0f01787... WEB
https://git.kernel.org/stable/c/f0a0f01787ecece814414b0665df879b69849d09

Frequently Asked Questions

What is CVE-2026-53283?
CVE-2026-53283 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-476: NULL Pointer Dereference.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-53283?
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-53283?
CVE-2026-53283 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-53283?
CVE-2026-53283 is classified under CWE-476: NULL Pointer Dereference (The product dereferences a pointer that it expects to be valid but is NULL.).
How can I check Maven dependencies for CVE-2026-53283?
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-gv9j-3945-3x3r",
  "modified" : "2026-07-08T06:31:35Z",
  "published" : "2026-06-26T21:32:16Z",
  "aliases" : [ "CVE-2026-53283" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd: Bounds-check devid in __rlookup_amd_iommu()\n\niommu_device_register() walks every device on the PCI bus via\nbus_for_each_dev() and calls amd_iommu_probe_device() for each. The\ninlined check_device() path computes the device's sbdf, calls\nrlookup_amd_iommu() to find the owning IOMMU, and only afterwards\nverifies devid <= pci_seg->last_bdf. __rlookup_amd_iommu() indexes\nrlookup_table[devid] with no bounds check of its own, so for a PCI\ndevice whose BDF is not described by the IVRS, the lookup reads past\nthe end of the allocation before the caller's bounds check can run.\n\nThis was harmless before commit e874c666b15b (\"iommu/amd: Change\nrlookup, irq_lookup, and alias to use kvalloc()\"): the table was a\nzeroed page-order allocation, so the over-read returned NULL and the\ncaller's NULL check skipped the device. After that commit the table is\na tight kvcalloc() and the over-read returns adjacent slab contents,\nwhich check_device() then dereferences as a struct amd_iommu *,\ncausing a boot-time GPF.\n\nSeen on Google Compute Engine ct6e VMs, where the virtualized IVRS\ndescribes only the four TPU endpoints 00:04.0-07.0; the gVNIC at\n00:08.0 (devid 0x40) indexes 56 bytes past the 456-byte allocation,\ninto the adjacent kmalloc-512 slab object:\n\n  pci 0000:00:04.0: Adding to iommu group 0\n  pci 0000:00:05.0: Adding to iommu group 1\n  pci 0000:00:06.0: Adding to iommu group 2\n  pci 0000:00:07.0: Adding to iommu group 3\n  Oops: general protection fault, probably for non-canonical address 0x3a64695f78746382: 0000 [#1] SMP NOPTI\n  CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.22 #1\n  Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/06/2025\n  RIP: 0010:amd_iommu_probe_device+0x54/0x3a0\n  Call Trace:\n   __iommu_probe_device+0x107/0x520\n   probe_iommu_group+0x29/0x50\n   bus_for_each_dev+0x7e/0xe0\n   iommu_device_register+0xc9/0x240\n   iommu_go_to_state+0x9c0/0x1c60\n   amd_iommu_init+0x14/0x40\n   pci_iommu_init+0x16/0x60\n   do_one_initcall+0x47/0x2f0\n\nGuard the array access in __rlookup_amd_iommu(). With the fix applied\non 6.18.22, the gVNIC at 00:08.0 is skipped cleanly and the VM boots.",
  "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-53283"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/07d0f496fe7ec5abe3bee7e38be709521567bb33"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/79db4cbab81f07ce69a93d379ebd40d3709ecfb2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f0a0f01787ecece814414b0665df879b69849d09"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-476" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-06-26T20:17:20Z"
  }
}