CVE-2026-80853: Software Security Vulnerability Vulnerability

UNKNOWN

Advisory Identifier: GHSA-g73p-24rg-vmh3

Published 2026-09-04

Advisory Summary

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

CVE Identifier CVE-2026-80853

GHSA Identifier GHSA-g73p-24rg-vmh3

Severity N/A

CVSS v3.1 Base Score N/A

CWE Classification General Security Weakness

Affected Product Software

Package Ecosystem Maven

Published Date 2026-09-04

Last Updated 2026-09-04

How to Fix CVE-2026-80853

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-80853, 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: KVM: SEV: Allocate full pages for {DE,EN}CRYPT ops on SNP-enabled hosts When {de,en}crypting memory of an SEV or SEV-ES guest on an SNP-enabled host via a temporary buffer, allocate a full 4KiB page for the buffer to ensure the page containing the buffer is wholly owned by KVM, i.e. won't be concurrently allocated and accessed by other kernel code while KVM is using the buffer to {de,en}crypt memory. On SNP-enabled platforms, when sending SEV/SEV-ES commands that trigger firmware writes to memory, the to-be-written page(s) must be (temporarily) assigned to Firmware (as required by the SNP architecture, to guard against using such commands as gadgets to attack SNP guests). See snp_map_cmd_buf_desc() and friends. Unfortunately, transferring ownership of a page to Firmware makes the page inaccessible to software, and thus writes generate RMP #PF violations. If KVM uses a sub-page allocation for its temporary buffer, some other actor in the kernel can allocate and use the other portions of the page, and thus trigger unexpected (and seemingly spurious) RMP #PF violations due to software attempting to access a Firmware-owned page. BUG: unable to handle page fault for address: ffff906ae30f0300 #PF: supervisor write access in kernel mode #PF: error_code(0x80000003) - RMP violation PGD 6b1b80d067 P4D 6b1b80d067 PUD 100231e2063 PMD 10055a88063 PTE 80000100630f0163 SEV-SNP: PFN 0x100630f0 unassigned, dumping non-zero entries in 2M PFN region: [0x10063000 - 0x10063200] Oops: Oops: 0003 [#1] SMP CPU: 70 UID: 0 PID: 10658 Comm: svw_WaiterThrea Tainted: G U W O 7.1.0-smp--c22293789940-seanjc-next #1 PREEMPTLAZY Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 34.86.0-102 01/25/2026 RIP: 0010:memset+0xf/0x20 Call Trace: <TASK> __kvmalloc_node_noprof+0x2a4/0x710 do_getxattr+0x4e/0x130 path_getxattrat+0x125/0x1b0 do_syscall_64+0x10a/0x480 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f3a22cb6daa </TASK> Modules linked in: kvm_amd kvm irqbypass vfat fat ccp k10temp sha3 libsha3 i2c_piix4 gq(O) cdc_acm xhci_pci xhci_hcd gsmi: Log Shutdown Reason 0x03 CR2: ffff906ae30f0300 ---[ end trace 0000000000000000 ]--- RIP: 0010:memset+0xf/0x20 Kernel panic - not syncing: Fatal exception Kernel Offset: 0x39e00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) gsmi: Log Shutdown Reason 0x02

References

NVD — CVE-2026-80853 NVD

https://nvd.nist.gov/vuln/detail/CVE-2026-80853

git.kernel.org/stable/c/97f6402f59... WEB

https://git.kernel.org/stable/c/97f6402f5950ca3450541287c4b3664f3acda976

git.kernel.org/stable/c/a33c40b93c... WEB

https://git.kernel.org/stable/c/a33c40b93ccf5177e042253807d40e0b92e7f206

Frequently Asked Questions

What is CVE-2026-80853?

CVE-2026-80853 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-80853?

Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.

What CWE is associated with CVE-2026-80853?

CVE-2026-80853 is classified under General Security Weakness.

How can I check Maven dependencies for CVE-2026-80853?

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-g73p-24rg-vmh3",
  "modified" : "2026-09-04T18:31:29Z",
  "published" : "2026-09-04T18:31:29Z",
  "aliases" : [ "CVE-2026-80853" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SEV: Allocate full pages for {DE,EN}CRYPT ops on SNP-enabled hosts\n\nWhen {de,en}crypting memory of an SEV or SEV-ES guest on an SNP-enabled\nhost via a temporary buffer, allocate a full 4KiB page for the buffer to\nensure the page containing the buffer is wholly owned by KVM, i.e. won't\nbe concurrently allocated and accessed by other kernel code while KVM is\nusing the buffer to {de,en}crypt memory.  On SNP-enabled platforms, when\nsending SEV/SEV-ES commands that trigger firmware writes to memory, the\nto-be-written page(s) must be (temporarily) assigned to Firmware (as\nrequired by the SNP architecture, to guard against using such commands as\ngadgets to attack SNP guests).  See snp_map_cmd_buf_desc() and friends.\n\nUnfortunately, transferring ownership of a page to Firmware makes the page\ninaccessible to software, and thus writes generate RMP #PF violations.  If\nKVM uses a sub-page allocation for its temporary buffer, some other actor\nin the kernel can allocate and use the other portions of the page, and thus\ntrigger unexpected (and seemingly spurious) RMP #PF violations due to\nsoftware attempting to access a Firmware-owned page.\n\n  BUG: unable to handle page fault for address: ffff906ae30f0300\n  #PF: supervisor write access in kernel mode\n  #PF: error_code(0x80000003) - RMP violation\n  PGD 6b1b80d067 P4D 6b1b80d067 PUD 100231e2063 PMD 10055a88063 PTE 80000100630f0163\n  SEV-SNP: PFN 0x100630f0 unassigned, dumping non-zero entries in 2M PFN region: [0x10063000 - 0x10063200]\n  Oops: Oops: 0003 [#1] SMP\n  CPU: 70 UID: 0 PID: 10658 Comm: svw_WaiterThrea Tainted: G     U  W  O        7.1.0-smp--c22293789940-seanjc-next #1 PREEMPTLAZY\n  Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE\n  Hardware name: Google, Inc.                                                       Arcadia_IT_80/Arcadia_IT_80, BIOS 34.86.0-102 01/25/2026\n  RIP: 0010:memset+0xf/0x20\n  Call Trace:\n   <TASK>\n   __kvmalloc_node_noprof+0x2a4/0x710\n   do_getxattr+0x4e/0x130\n   path_getxattrat+0x125/0x1b0\n   do_syscall_64+0x10a/0x480\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x7f3a22cb6daa\n   </TASK>\n  Modules linked in: kvm_amd kvm irqbypass vfat fat ccp k10temp sha3 libsha3 i2c_piix4 gq(O) cdc_acm xhci_pci xhci_hcd\n  gsmi: Log Shutdown Reason 0x03\n  CR2: ffff906ae30f0300\n  ---[ end trace 0000000000000000 ]---\n  RIP: 0010:memset+0xf/0x20\n  Kernel panic - not syncing: Fatal exception\n  Kernel Offset: 0x39e00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)\n  gsmi: Log Shutdown Reason 0x02",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-80853"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/97f6402f5950ca3450541287c4b3664f3acda976"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a33c40b93ccf5177e042253807d40e0b92e7f206"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-04T16:18:14Z"
  }
}

Advisory Metadata

Source ID: GHSA-g73p-24rg-vmh3
Schema Version: 1.4.0
Published: 2026-09-04 18:31
Last Modified: 2026-09-04 18:31
Database Record File: advisories/unreviewed/2026/09/GHSA-g73p-24rg-vmh3/GHSA-g73p-24rg-vmh3.json