Vulnerability-Lookup

FKIE_CVE-2026-80853

Vulnerability from fkie_nvd - Published: 2026-09-04 16:18 - Updated: 2026-10-19 09:17

Severity

Summary

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

	URL	Tags
	416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/97f6402f5950ca3450541287c4b3664f3acda976
	416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/a33c40b93ccf5177e042253807d40e0b92e7f206

Impacted products

	Vendor	Product	Version

JSON

To clipboard

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/kvm/svm/sev.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "97f6402f5950ca3450541287c4b3664f3acda976",
              "status": "affected",
              "version": "4c735bf1bc22fd6ee66ab4bffe1d7599c3964781",
              "versionType": "git"
            },
            {
              "lessThan": "a33c40b93ccf5177e042253807d40e0b92e7f206",
              "status": "affected",
              "version": "4c735bf1bc22fd6ee66ab4bffe1d7599c3964781",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/kvm/svm/sev.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.2"
            },
            {
              "lessThan": "7.2",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.3",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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\u0027t\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   \u003cTASK\u003e\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   \u003c/TASK\u003e\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"
    }
  ],
  "id": "CVE-2026-80853",
  "lastModified": "2026-10-19T09:17:20.913",
  "metrics": {},
  "published": "2026-09-04T16:18:14.233",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/97f6402f5950ca3450541287c4b3664f3acda976"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/a33c40b93ccf5177e042253807d40e0b92e7f206"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}

CVE-2026-80853 (GCVE-0-2026-80853)

Vulnerability from cvelistv5 – Published: 2026-09-04 15:55 – Updated: 2026-10-19 08:44

Title

KVM: SEV: Allocate full pages for {DE,EN}CRYPT ops on SNP-enabled hosts

Summary

Severity

No CVSS data available.

Assigner

Linux CNA under the mitre root

CNA scorecard D 53/100 over 6641 records in the last 180 days details

References

2 references

URL	Tags
https://git.kernel.org/stable/c/97f6402f5950ca345…
https://git.kernel.org/stable/c/a33c40b93ccf5177e…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 4c735bf1bc22fd6ee66ab4bffe1d7599c3964781 , < 97f6402f5950ca3450541287c4b3664f3acda976 (git) Affected: 4c735bf1bc22fd6ee66ab4bffe1d7599c3964781 , < a33c40b93ccf5177e042253807d40e0b92e7f206 (git)
Linux	Linux	Affected: 7.2 Unaffected: 0 , < 7.2 (semver) Unaffected: 7.2.3 , ≤ 7.2.* (semver) Unaffected: 7.3 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/kvm/svm/sev.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "97f6402f5950ca3450541287c4b3664f3acda976",
              "status": "affected",
              "version": "4c735bf1bc22fd6ee66ab4bffe1d7599c3964781",
              "versionType": "git"
            },
            {
              "lessThan": "a33c40b93ccf5177e042253807d40e0b92e7f206",
              "status": "affected",
              "version": "4c735bf1bc22fd6ee66ab4bffe1d7599c3964781",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/kvm/svm/sev.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.2"
            },
            {
              "lessThan": "7.2",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.3",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.3",
                  "versionStartIncluding": "7.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "7.2",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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\u0027t\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   \u003cTASK\u003e\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   \u003c/TASK\u003e\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"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T08:44:47.327Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/97f6402f5950ca3450541287c4b3664f3acda976"
        },
        {
          "url": "https://git.kernel.org/stable/c/a33c40b93ccf5177e042253807d40e0b92e7f206"
        }
      ],
      "title": "KVM: SEV: Allocate full pages for {DE,EN}CRYPT ops on SNP-enabled hosts",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-80853",
    "datePublished": "2026-09-04T15:55:05.021Z",
    "dateReserved": "2026-08-26T14:34:25.797Z",
    "dateUpdated": "2026-10-19T08:44:47.327Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted