BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-63794High confidence

KVM: SVM: Fix page overflow in sev_dbg_crypt() for ENCRYPT path

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 17 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.14% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.95-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.177-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-63794 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: KVM: SVM: Fix page overflow in sev_dbg_crypt() for ENCRYPT path
99 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's Kernel-based Virtual Machine (KVM) module, specifically within the Secure Virtual Machine (SVM) component. The `sev_dbg_crypt()` function, when handling encryption, incorrectly calculates the transfer length, leading to a page overflow. This memory corruption can result in a use-after-free condition. A local attacker could exploit this vulnerability to cause a denial of service or potentially escalate privileges.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
CVE-2026-63794 · CSAF 2.0 · revision 23 · interimSUSE Product Security TeamCVE-2026-63794
114 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Fix page overflow in sev_dbg_crypt() for ENCRYPT path In sev_dbg_crypt(), the per-iteration transfer length is bounded by the source page offset (PAGE_SIZE - s_off) but not by the destination page offset (PAGE_SIZE - d_off). When d_off > s_off, the encrypt path (__sev_dbg_encrypt_user) performs a read-modify-write using a single-page intermediate buffer (dst_tpage): 1. __sev_dbg_decrypt() expands the size to round_up(len + (d_off & 15), 16) before issuing the PSP command. If len + (d_off & 15) > PAGE_SIZE, the PSP writes beyond the end of the 4096-byte dst_tpage allocation. 2. The subsequent memcpy()/copy_from_user() into page_address(dst_tpage) + (d_off & 15) of 'len' bytes overflows by up to 15 bytes under the same condition. Trigger example: s_off = 0, d_off = 1, debug.len = PAGE_SIZE - the PSP is instructed to write round_up(4097, 16) = 4112 bytes to a 4096-byte buffer. Fix by also bounding len by (PAGE_SIZE - d_off), the same check that sev_send_update_data() already performs for its single-page guest region. ================================================================== BUG: KASAN: slab-use-after-free in sev_dbg_crypt+0x993/0xd10 [kvm_amd] Write of size 4095 at addr ff110062293bb009 by task sev_dbg_test/228214 CPU: 96 UID: 0 PID: 228214 Comm: sev_dbg_test Tainted: G U W 7.0.0-smp--5ce9b0c48211-dbg #156 PREEMPTLAZY Tainted: [U]=USER, [W]=WARN Hardware name: Google Astoria/astoria, BIOS 0.20250817.1-0 08/25/2025 Call Trace: dump_stack_lvl+0x54/0x70 print_report+0xbc/0x260 kasan_report+0xa2/0xd0 kasan_check_range+0x25f/0x2c0 __asan_memcpy+0x40/0x70 sev_dbg_crypt+0x993/0xd10 [kvm_amd] sev_mem_enc_ioctl+0x33c/0x450 [kvm_amd] kvm_vm_ioctl+0x65d/0x6d0 [kvm] __se_sys_ioctl+0xb2/0x100 do_syscall_64+0xe8/0x870 entry_SYSCALL_64_after_hwframe+0x4b/0x53 The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x7fe72b6a0 pfn:0x62293bb memcg:ff11000112827d82 flags: 0x1400000000000000(node=1|zone=1) raw: 1400000000000000 0000000000000000 dead000000000122 0000000000000000 raw: 00000007fe72b6a0 0000000000000000 00000001ffffffff ff11000112827d82 page dumped because: kasan: bad access detected Memory state around the buggy address: ff110062293bbf00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff110062293bbf80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ff110062293bc000: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ^ ff110062293bc080: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ff110062293bc100: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ================================================================== Disabling lock debugging due to kernel taint [sean: add sample KASAN splat, Fixes, and stable@]
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-45460

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Fix page overflow in sev_dbg_crypt() for ENCRYPT path In sev_dbg_crypt(), the per-iteration transfer length is bounded by the source page offset (PAGE_SIZE - s_off) but not by the destination page offset (PAGE_SIZE - d_off). When d_off > s_off, the encrypt path (__sev_dbg_encrypt_user) performs a read-modify-write using a single-page intermediate buffer (dst_tpage): 1. __sev_dbg_decrypt() expands the size to round_up(len + (d_off & 15), 16) before issuing the PSP command. If len + (d_off & 15) > PAGE_SIZE, the PSP writes beyond the end of the 4096-byte dst_tpage allocation. 2. The subsequent memcpy()/copy_from_user() into page_address(dst_tpage) + (d_off & 15) of 'len' bytes overflows by up to 15 bytes under the same condition. Trigger example: s_off = 0, d_off = 1, debug.len = PAGE_SIZE - the PSP is instructed to write round_up(4097, 16) = 4112 bytes to a 4096-byte buffer. Fix by also bounding len by (PAGE_SIZE - d_off), the same check that sev_send_update_data() already performs for its single-page guest region. ================================================================== BUG: KASAN: slab-use-after-free in sev_dbg_crypt+0x993/0xd10 [kvm_amd] Write of size 4095 at addr ff110062293bb009 by task sev_dbg_test/228214 CPU: 96 UID: 0 PID: 228214 Comm: sev_dbg_test Tainted: G U W 7.0.0-smp--5ce9b0c48211-dbg #156 PREEMPTLAZY Tainted: [U]=USER, [W]=WARN Hardware name: Google Astoria/astoria, BIOS 0.20250817.1-0 08/25/2025 Call Trace: <TASK> dump_stack_lvl+0x54/0x70 print_report+0xbc/0x260 kasan_report+0xa2/0xd0 kasan_check_range+0x25f/0x2c0 __asan_memcpy+0x40/0x70 sev_dbg_crypt+0x993/0xd10 [kvm_amd] sev_mem_enc_ioctl+0x33c/0x450 [kvm_amd] kvm_vm_ioctl+0x65d/0x6d0 [kvm] __se_sys_ioctl+0xb2/0x100 do_syscall_64+0xe8/0x870 entry_SYSCALL_64_after_hwframe+0x4b/0x53 </TASK> The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x7fe72b6a0 pfn:0x62293bb memcg:ff11000112827d82 flags: 0x1400000000000000(node=1|zone=1) raw: 1400000000000000 0000000000000000 dead000000000122 0000000000000000 raw: 00000007fe72b6a0 0000000000000000 00000001ffffffff ff11000112827d82 page dumped because: kasan: bad access detected Memory state around the buggy address: ff110062293bbf00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff110062293bbf80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ff110062293bc000: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ^ ff110062293bc080: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ff110062293bc100: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ================================================================== Disabling lock debugging due to kernel taint [sean: add sample KASAN splat, Fixes, and stable@]

What

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Fix page overflow in sev_dbg_crypt() for ENCRYPT path In sev_dbg_crypt(), the per-iteration transfer length is bounded by the source page offset (PAGE_SIZE - s_off) but not by the destination page offset (PAGE_SIZE - d_off). When d_off > s_off, the encrypt path (__sev_dbg_encrypt_user) performs a read-modify-write using a single-page intermediate buffer (dst_tpage): 1. __sev_dbg_decrypt() expands the size to round_up(len + (d_off & 15), 16) before issuing the PSP command. If len + (d_off & 15) > PAGE_SIZE, the PSP writes beyond the end of the 4096-byte dst_tpage allocation. 2. The subsequent memcpy()/copy_from_user() into page_address(dst_tpage) + (d_off & 15) of 'len' bytes overflows by up to 15 bytes under the same condition. Trigger example: s_off = 0, d_off = 1, debug.len = PAGE_SIZE - the PSP is instructed to write round_up(4097, 16) = 4112 bytes to a 4096-byte buffer. Fix by also bounding len by (PAGE_SIZE - d_off), the same check that sev_send_update_data() already performs for its single-page guest region. ================================================================== BUG: KASAN: slab-use-after-free in sev_dbg_crypt+0x993/0xd10 [kvm_amd] Write of size 4095 at addr ff110062293bb009 by task sev_dbg_test/228214 CPU: 96 UID: 0 PID: 228214 Comm: sev_dbg_test Tainted: G U W 7.0.0-smp--5ce9b0c48211-dbg #156 PREEMPTLAZY Tainted: [U]=USER, [W]=WARN Hardware name: Google Astoria/astoria, BIOS 0.20250817.1-0 08/25/2025 Call Trace: <TASK> dump_stack_lvl+0x54/0x70 print_report+0xbc/0x260 kasan_report+0xa2/0xd0 kasan_check_range+0x25f/0x2c0 __asan_memcpy+0x40/0x70 sev_dbg_crypt+0x993/0xd10 [kvm_amd] sev_mem_enc_ioctl+0x33c/0x450 [kvm_amd] kvm_vm_ioctl+0x65d/0x6d0 [kvm] __se_sys_ioctl+0xb2/0x100 do_syscall_64+0xe8/0x870 entry_SYSCALL_64_after_hwframe+0x4b/0x53 </TASK> The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x7fe72b6a0 pfn:0x62293bb memcg:ff11000112827d82 flags: 0x1400000000000000(node=1|zone=1) raw: 1400000000000000 0000000000000000 dead000000000122 0000000000000000 raw: 00000007fe72b6a0 0000000000000000 00000001ffffffff ff11000112827d82 page dumped because: kasan: bad access detected Memory state around the buggy address: ff110062293bbf00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff110062293bbf80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ff110062293bc000: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ^ ff110062293bc080: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ff110062293bc100: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ================================================================== Disabling lock debugging due to kernel taint [sean: add sample KASAN splat, Fixes, and stable@]

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Fix page overflow in sev_dbg_crypt() for ENCRYPT path In sev_dbg_crypt(), the per-iteration transfer length is bounded by the source page offset (PAGE_SIZE - s_off) but not by the destination page offset (PAGE_SIZE - d_off). When d_off > s_off, the encrypt path (__sev_dbg_encrypt_user) performs a read-modify-write using a single-page intermediate buffer (dst_tpage): 1. __sev_dbg_decrypt() expands the size to round_up(len + (d_off & 15), 16) before issuing the PSP command. If len + (d_off & 15) > PAGE_SIZE, the PSP writes beyond the end of the 4096-byte dst_tpage allocation. 2. The subsequent memcpy()/copy_from_user() into page_address(dst_tpage) + (d_off & 15) of 'len' bytes overflows by up to 15 bytes under the same condition. Trigger example: s_off = 0, d_off = 1, debug.len = PAGE_SIZE - the PSP is instructed to write round_up(4097, 16) = 4112 bytes to a 4096-byte buffer. Fix by also bounding len by (PAGE_SIZE - d_off), the same check that sev_send_update_data() already performs for its single-page guest region. ================================================================== BUG: KASAN: slab-use-after-free in sev_dbg_crypt+0x993/0xd10 [kvm_amd] Write of size 4095 at addr ff110062293bb009 by task sev_dbg_test/228214 CPU: 96 UID: 0 PID: 228214 Comm: sev_dbg_test Tainted: G U W 7.0.0-smp--5ce9b0c48211-dbg #156 PREEMPTLAZY Tainted: [U]=USER, [W]=WARN Hardware name: Google Astoria/astoria, BIOS 0.20250817.1-0 08/25/2025 Call Trace: <TASK> dump_stack_lvl+0x54/0x70 print_report+0xbc/0x260 kasan_report+0xa2/0xd0 kasan_check_range+0x25f/0x2c0 __asan_memcpy+0x40/0x70 sev_dbg_crypt+0x993/0xd10 [kvm_amd] sev_mem_enc_ioctl+0x33c/0x450 [kvm_amd] kvm_vm_ioctl+0x65d/0x6d0 [kvm] __se_sys_ioctl+0xb2/0x100 do_syscall_64+0xe8/0x870 entry_SYSCALL_64_after_hwframe+0x4b/0x53 </TASK> The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x7fe72b6a0 pfn:0x62293bb memcg:ff11000112827d82 flags: 0x1400000000000000(node=1|zone=1) raw: 1400000000000000 0000000000000000 dead000000000122 0000000000000000 raw: 00000007fe72b6a0 0000000000000000 00000001ffffffff ff11000112827d82 page dumped because: kasan: bad access detected Memory state around the buggy address: ff110062293bbf00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff110062293bbf80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ff110062293bc000: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ^ ff110062293bc080: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ff110062293bc100: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ================================================================== Disabling lock debugging due to kernel taint [sean: add sample KASAN splat, Fixes, and stable@]

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Out-of-bounds Write → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-787 ↗

CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-787
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2403Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260722Security Bulletin 22 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jul 2026, published on 22 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53395 Référence CVE CVE-2026-53396 https://www.cve.org/CVERecord?id=CVE-2026-53396 Référence CVE CVE-2026-53397 https://www.cve.org/CVERecord?id=CVE-2026-53397 Référence CVE CVE-2026-53398 https://www.cve.org/CVERecord?id=CVE-2026-53398 Référence CVE CVE-2026-53399 https://www.cve.org/CVERecord?id=CVE-2026-53399 Référence CVE CVE-2026-53400 https://www.cve.org/CVERecord?id=CVE-2026-53400 Référence CVE CVE-2026-53401 https://www.cve.org/CVERecord?id=CVE-2026-53401 Référence CVE CVE-2026-53402 https://www.cve.org/CVERecord?id=CVE-2026-53402 Référence CVE CVE-2026-53403 https://www.cve.org/CVERecord?id=CVE-2026-53403 Référence CVE CVE-2026-63794 https://www.cve.org/CVERecord?id=CVE-2026-63794 Référence CVE CVE-2026-63795 https://www.cve.org/CVERecord?id=CVE-2026-63795 Référence CVE CVE-2026-63796 https://www.cve.org/CVERecord?id=CVE-2026-63796 Référence CVE CVE-2026-63797 https://www.cve.org/CVERecord?id=CVE-2026-63797 Référence CVE CVE-2026-63798 https://www.cve.org/CVERecord?id=CVE-2026-63798 Référence CVE CVE-2026-63799 https://www.cve.org/CVERecord?id=CVE-2026-63799 Référence CVE CVE-2026-63800 https://www.cve.org/CVERecord?id=CVE-2026-63800 Référence CVE CVE-2026-63801 https://www.cve.org/CVERecord?id=CVE-2026-63801 Référence CVE CVE-2026-63802 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1254Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2026-53002 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53091 https://www.cve.org/CVERecord?id=CVE-2026-53091 Référence CVE CVE-2026-53166 https://www.cve.org/CVERecord?id=CVE-2026-53166 Référence CVE CVE-2026-53185 https://www.cve.org/CVERecord?id=CVE-2026-53185 Référence CVE CVE-2026-53239 https://www.cve.org/CVERecord?id=CVE-2026-53239 Référence CVE CVE-2026-53266 https://www.cve.org/CVERecord?id=CVE-2026-53266 Référence CVE CVE-2026-53341 https://www.cve.org/CVERecord?id=CVE-2026-53341 Référence CVE CVE-2026-63794 https://www.cve.org/CVERecord?id=CVE-2026-63794 Référence CVE CVE-2026-63823 https://www.cve.org/CVERecord?id=CVE-2026-63823 Référence CVE CVE-2026-63875 https://www.cve.org/CVERecord?id=CVE-2026-63875 Référence CVE CVE-2026-63917 https://www.cve.org/CVERecord?id=CVE-2026-63917 Référence CVE CVE-2026-63919 https://www.cve.org/CVERecord?id=CVE-2026-63919 Référence CVE CVE-2026-63921 https://www.cve.org/CVERecord?id=CVE-2026-63921 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=CVE-2026-64102 Référence CVE CVE-2026-64191 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53395 Référence CVE CVE-2026-53396 https://www.cve.org/CVERecord?id=CVE-2026-53396 Référence CVE CVE-2026-53397 https://www.cve.org/CVERecord?id=CVE-2026-53397 Référence CVE CVE-2026-53398 https://www.cve.org/CVERecord?id=CVE-2026-53398 Référence CVE CVE-2026-53399 https://www.cve.org/CVERecord?id=CVE-2026-53399 Référence CVE CVE-2026-53400 https://www.cve.org/CVERecord?id=CVE-2026-53400 Référence CVE CVE-2026-53401 https://www.cve.org/CVERecord?id=CVE-2026-53401 Référence CVE CVE-2026-53402 https://www.cve.org/CVERecord?id=CVE-2026-53402 Référence CVE CVE-2026-53403 https://www.cve.org/CVERecord?id=CVE-2026-53403 Référence CVE CVE-2026-63794 https://www.cve.org/CVERecord?id=CVE-2026-63794 Référence CVE CVE-2026-63795 https://www.cve.org/CVERecord?id=CVE-2026-63795 Référence CVE CVE-2026-63796 https://www.cve.org/CVERecord?id=CVE-2026-63796 Référence CVE CVE-2026-63797 https://www.cve.org/CVERecord?id=CVE-2026-63797 Référence CVE CVE-2026-63798 https://www.cve.org/CVERecord?id=CVE-2026-63798 Référence CVE CVE-2026-63799 https://www.cve.org/CVERecord?id=CVE-2026-63799 Référence CVE CVE-2026-63800 https://www.cve.org/CVERecord?id=CVE-2026-63800 Référence CVE CVE-2026-63801 https://www.cve.org/CVERecord?id=CVE-2026-63801 Référence CVE CVE-2026-63802 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53395 Référence CVE CVE-2026-53396 https://www.cve.org/CVERecord?id=CVE-2026-53396 Référence CVE CVE-2026-53397 https://www.cve.org/CVERecord?id=CVE-2026-53397 Référence CVE CVE-2026-53398 https://www.cve.org/CVERecord?id=CVE-2026-53398 Référence CVE CVE-2026-53399 https://www.cve.org/CVERecord?id=CVE-2026-53399 Référence CVE CVE-2026-53400 https://www.cve.org/CVERecord?id=CVE-2026-53400 Référence CVE CVE-2026-53401 https://www.cve.org/CVERecord?id=CVE-2026-53401 Référence CVE CVE-2026-53402 https://www.cve.org/CVERecord?id=CVE-2026-53402 Référence CVE CVE-2026-53403 https://www.cve.org/CVERecord?id=CVE-2026-53403 Référence CVE CVE-2026-63794 https://www.cve.org/CVERecord?id=CVE-2026-63794 Référence CVE CVE-2026-63795 https://www.cve.org/CVERecord?id=CVE-2026-63795 Référence CVE CVE-2026-63796 https://www.cve.org/CVERecord?id=CVE-2026-63796 Référence CVE CVE-2026-63797 https://www.cve.org/CVERecord?id=CVE-2026-63797 Référence CVE CVE-2026-63798 https://www.cve.org/CVERecord?id=CVE-2026-63798 Référence CVE CVE-2026-63799 https://www.cve.org/CVERecord?id=CVE-2026-63799 Référence CVE CVE-2026-63800 https://www.cve.org/CVERecord?id=CVE-2026-63800 Référence CVE CVE-2026-63801 https://www.cve.org/CVERecord?id=CVE-2026-63801 Référence CVE CVE-2026-63802 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53395 Référence CVE CVE-2026-53396 https://www.cve.org/CVERecord?id=CVE-2026-53396 Référence CVE CVE-2026-53397 https://www.cve.org/CVERecord?id=CVE-2026-53397 Référence CVE CVE-2026-53398 https://www.cve.org/CVERecord?id=CVE-2026-53398 Référence CVE CVE-2026-53399 https://www.cve.org/CVERecord?id=CVE-2026-53399 Référence CVE CVE-2026-53400 https://www.cve.org/CVERecord?id=CVE-2026-53400 Référence CVE CVE-2026-53401 https://www.cve.org/CVERecord?id=CVE-2026-53401 Référence CVE CVE-2026-53402 https://www.cve.org/CVERecord?id=CVE-2026-53402 Référence CVE CVE-2026-53403 https://www.cve.org/CVERecord?id=CVE-2026-53403 Référence CVE CVE-2026-63794 https://www.cve.org/CVERecord?id=CVE-2026-63794 Référence CVE CVE-2026-63795 https://www.cve.org/CVERecord?id=CVE-2026-63795 Référence CVE CVE-2026-63796 https://www.cve.org/CVERecord?id=CVE-2026-63796 Référence CVE CVE-2026-63797 https://www.cve.org/CVERecord?id=CVE-2026-63797 Référence CVE CVE-2026-63798 https://www.cve.org/CVERecord?id=CVE-2026-63798 Référence CVE CVE-2026-63799 https://www.cve.org/CVERecord?id=CVE-2026-63799 Référence CVE CVE-2026-63800 https://www.cve.org/CVERecord?id=CVE-2026-63800 Référence CVE CVE-2026-63801 https://www.cve.org/CVERecord?id=CVE-2026-63801 Référence CVE CVE-2026-63802 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1091Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53388 Référence CVE CVE-2026-53391 https://www.cve.org/CVERecord?id=CVE-2026-53391 Référence CVE CVE-2026-53392 https://www.cve.org/CVERecord?id=CVE-2026-53392 Référence CVE CVE-2026-53393 https://www.cve.org/CVERecord?id=CVE-2026-53393 Référence CVE CVE-2026-53397 https://www.cve.org/CVERecord?id=CVE-2026-53397 Référence CVE CVE-2026-53398 https://www.cve.org/CVERecord?id=CVE-2026-53398 Référence CVE CVE-2026-53399 https://www.cve.org/CVERecord?id=CVE-2026-53399 Référence CVE CVE-2026-53402 https://www.cve.org/CVERecord?id=CVE-2026-53402 Référence CVE CVE-2026-53403 https://www.cve.org/CVERecord?id=CVE-2026-53403 Référence CVE CVE-2026-63794 https://www.cve.org/CVERecord?id=CVE-2026-63794 Référence CVE CVE-2026-63795 https://www.cve.org/CVERecord?id=CVE-2026-63795 Référence CVE CVE-2026-63802 https://www.cve.org/CVERecord?id=CVE-2026-63802 Référence CVE CVE-2026-63806 https://www.cve.org/CVERecord?id=CVE-2026-63806 Référence CVE CVE-2026-63807 https://www.cve.org/CVERecord?id=CVE-2026-63807 Référence CVE CVE-2026-63809 https://www.cve.org/CVERecord?id=CVE-2026-63809 Référence CVE CVE-2026-63821 https://www.cve.org/CVERecord?id=CVE-2026-63821 Référence CVE CVE-2026-63822 https://www.cve.org/CVERecord?id=CVE-2026-63822 Référence CVE CVE-2026-63824 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1064Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53392 Référence CVE CVE-2026-53393 https://www.cve.org/CVERecord?id=CVE-2026-53393 Référence CVE CVE-2026-53394 https://www.cve.org/CVERecord?id=CVE-2026-53394 Référence CVE CVE-2026-53397 https://www.cve.org/CVERecord?id=CVE-2026-53397 Référence CVE CVE-2026-53398 https://www.cve.org/CVERecord?id=CVE-2026-53398 Référence CVE CVE-2026-53399 https://www.cve.org/CVERecord?id=CVE-2026-53399 Référence CVE CVE-2026-53400 https://www.cve.org/CVERecord?id=CVE-2026-53400 Référence CVE CVE-2026-53402 https://www.cve.org/CVERecord?id=CVE-2026-53402 Référence CVE CVE-2026-53403 https://www.cve.org/CVERecord?id=CVE-2026-53403 Référence CVE CVE-2026-63794 https://www.cve.org/CVERecord?id=CVE-2026-63794 Référence CVE CVE-2026-63795 https://www.cve.org/CVERecord?id=CVE-2026-63795 Référence CVE CVE-2026-63802 https://www.cve.org/CVERecord?id=CVE-2026-63802 Référence CVE CVE-2026-63806 https://www.cve.org/CVERecord?id=CVE-2026-63806 Référence CVE CVE-2026-63807 https://www.cve.org/CVERecord?id=CVE-2026-63807 Référence CVE CVE-2026-63809 https://www.cve.org/CVERecord?id=CVE-2026-63809 Référence CVE CVE-2026-63821 https://www.cve.org/CVERecord?id=CVE-2026-63821 Référence CVE CVE-2026-63822 https://www.cve.org/CVERecord?id=CVE-2026-63822 Référence CVE CVE-2026-63824 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1029Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53374 Référence CVE CVE-2026-53375 https://www.cve.org/CVERecord?id=CVE-2026-53375 Référence CVE CVE-2026-53376 https://www.cve.org/CVERecord?id=CVE-2026-53376 Référence CVE CVE-2026-53388 https://www.cve.org/CVERecord?id=CVE-2026-53388 Référence CVE CVE-2026-53391 https://www.cve.org/CVERecord?id=CVE-2026-53391 Référence CVE CVE-2026-53392 https://www.cve.org/CVERecord?id=CVE-2026-53392 Référence CVE CVE-2026-53397 https://www.cve.org/CVERecord?id=CVE-2026-53397 Référence CVE CVE-2026-53399 https://www.cve.org/CVERecord?id=CVE-2026-53399 Référence CVE CVE-2026-53402 https://www.cve.org/CVERecord?id=CVE-2026-53402 Référence CVE CVE-2026-63794 https://www.cve.org/CVERecord?id=CVE-2026-63794 Référence CVE CVE-2026-63802 https://www.cve.org/CVERecord?id=CVE-2026-63802 Référence CVE CVE-2026-63806 https://www.cve.org/CVERecord?id=CVE-2026-63806 Référence CVE CVE-2026-63807 https://www.cve.org/CVERecord?id=CVE-2026-63807 Référence CVE CVE-2026-63824 https://www.cve.org/CVERecord?id=CVE-2026-63824 Référence CVE CVE-2026-63826 https://www.cve.org/CVERecord?id=CVE-2026-63826 Référence CVE CVE-2026-63829 https://www.cve.org/CVERecord?id=CVE-2026-63829 Référence CVE CVE-2026-63884 https://www.cve.org/CVERecord?id=CVE-2026-63884 Référence CVE CVE-2026-63893 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0982Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-53385 Référence CVE CVE-2026-53392 https://www.cve.org/CVERecord?id=CVE-2026-53392 Référence CVE CVE-2026-53393 https://www.cve.org/CVERecord?id=CVE-2026-53393 Référence CVE CVE-2026-53397 https://www.cve.org/CVERecord?id=CVE-2026-53397 Référence CVE CVE-2026-53398 https://www.cve.org/CVERecord?id=CVE-2026-53398 Référence CVE CVE-2026-53399 https://www.cve.org/CVERecord?id=CVE-2026-53399 Référence CVE CVE-2026-53400 https://www.cve.org/CVERecord?id=CVE-2026-53400 Référence CVE CVE-2026-53402 https://www.cve.org/CVERecord?id=CVE-2026-53402 Référence CVE CVE-2026-53403 https://www.cve.org/CVERecord?id=CVE-2026-53403 Référence CVE CVE-2026-63794 https://www.cve.org/CVERecord?id=CVE-2026-63794 Référence CVE CVE-2026-63796 https://www.cve.org/CVERecord?id=CVE-2026-63796 Référence CVE CVE-2026-63797 https://www.cve.org/CVERecord?id=CVE-2026-63797 Référence CVE CVE-2026-63798 https://www.cve.org/CVERecord?id=CVE-2026-63798 Référence CVE CVE-2026-63800 https://www.cve.org/CVERecord?id=CVE-2026-63800 Référence CVE CVE-2026-63801 https://www.cve.org/CVERecord?id=CVE-2026-63801 Référence CVE CVE-2026-63803 https://www.cve.org/CVERecord?id=CVE-2026-63803 Référence CVE CVE-2026-63806 https://www.cve.org/CVERecord?id=CVE-2026-63806 Référence CVE CVE-2026-63808 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0957Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-53383 Référence CVE CVE-2026-53384 https://www.cve.org/CVERecord?id=CVE-2026-53384 Référence CVE CVE-2026-53385 https://www.cve.org/CVERecord?id=CVE-2026-53385 Référence CVE CVE-2026-53388 https://www.cve.org/CVERecord?id=CVE-2026-53388 Référence CVE CVE-2026-53390 https://www.cve.org/CVERecord?id=CVE-2026-53390 Référence CVE CVE-2026-53391 https://www.cve.org/CVERecord?id=CVE-2026-53391 Référence CVE CVE-2026-53397 https://www.cve.org/CVERecord?id=CVE-2026-53397 Référence CVE CVE-2026-53398 https://www.cve.org/CVERecord?id=CVE-2026-53398 Référence CVE CVE-2026-53403 https://www.cve.org/CVERecord?id=CVE-2026-53403 Référence CVE CVE-2026-63794 https://www.cve.org/CVERecord?id=CVE-2026-63794 Référence CVE CVE-2026-63795 https://www.cve.org/CVERecord?id=CVE-2026-63795 Référence CVE CVE-2026-63796 https://www.cve.org/CVERecord?id=CVE-2026-63796 Référence CVE CVE-2026-63798 https://www.cve.org/CVERecord?id=CVE-2026-63798 Référence CVE CVE-2026-63800 https://www.cve.org/CVERecord?id=CVE-2026-63800 Référence CVE CVE-2026-63801 https://www.cve.org/CVERecord?id=CVE-2026-63801 Référence CVE CVE-2026-63803 https://www.cve.org/CVERecord?id=CVE-2026-63803 Référence CVE CVE-2026-63807 https://www.cve.org/CVERecord?id=CVE-2026-63807 Référence CVE CVE-2026-63808 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-026114LinuxのLinux Kernelにおける境界外書き込みに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。KVM: SVM: ENCRYPTパスのsev_dbg_crypt()におけるページオーバーフローの修正について説明します。sev_dbg_crypt()内では、反復ごとの転送長は送信元ページのオフセット（PAGE_SIZE - s_off）によって制限されていますが、送信先ページのオフセット（PAGE_SIZE - d_off）によっては制限されていません。d_offがs_offより大きい場合、暗号化パス（__sev_dbg_encrypt_user）は単一ページの中間バッファ（dst_tpage）を使用して読み取り・修正・書き込みを行います。具体的には以下の通りです。 1. __sev_dbg_decrypt()はPSPコマンド発行前にサイズをround_up(len + (d_off & 15), 16)に拡張します。ここで、もしlen + (d_off & 15)がPAGE_SIZEを超えた場合、PSPは4096バイトのdst_tpage割り当ての末尾を越えて書き込みを行います。 2. その後のmemcpy()やcopy_from_user()でpage_address(dst_tpage) + (d_off & 15)へlenバイトを書き込む際、同様の条件下で最大15バイトのオーバーフローが発生します。 トリガー例として、s_off = 0、d_off = 1、debug.len = PAGE_SIZEの場合、PSPは4097バイトを16の倍数に切り上げた4112バイト分を4096バイトのバッファに書き込むよう指示されます。 この問題はlenを(PAGE_SIZE - d_off)で制限することで修正されました。これはsev_send_update_data()が単一ページのゲスト領域に対して行っているチェックと同じです。==================================================================バグ内容の詳細は以下の通りです。KASAN: slab-use-after-freeがsev_dbg_crypt+0x993/0xd10 [kvm_amd]内で発生しました。4095バイトの書き込みがアドレスff110062293bb009に対してtask sev_dbg_test/228214によって実行されています。CPU: 96 UID: 0 PID: 228214 コマンド: sev_dbg_test カーネル状態: Tainted (ユーザーコードと警告)ハードウェア名: Google Astoria/astoria, BIOS 0.20250817.1-0 2025/08/25 コールトレースは以下の通りです。 ＜TASK＞ dump_stack_lvl+0x54/0x70 print_report+0xbc/0x260 kasan_report+0xa2/0xd0 kasan_check_range+0x25f/0x2c0 __asan_memcpy+0x40/0x70 sev_dbg_crypt+0x993/0xd10 [kvm_amd] sev_mem_enc_ioctl+0x33c/0x450 [kvm_amd] kvm_vm_ioctl+0x65d/0x6d0 [kvm] __se_sys_ioctl+0xb2/0x100 do_syscall_64+0xe8/0x870 entry_SYSCALL_64_after_hwframe+0x4b/0x53 ＜/TASK＞ 問題のアドレスは以下の物理ページに属しています。 ページ: refcount:1 mapcount:0 mapping:0000000000000000 index:0x7fe72b6a0 pfn:0x62293bb memcg:ff11000112827d82 flags: 0x1400000000000000 (node=1|zone=1) ページはkasanによる不正アクセス検知のためダンプされました。問題のアドレス周辺のメモリ状態は以下の通りです。 ff110062293bbf00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff110062293bbf80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ＞ff110062293bc000: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ^ ff110062293bc080: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ff110062293bc100: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ================================================================== カーネルが汚染されている状態のためロックデバッグは無効化されています。[sean: KASANスプラットフォームの例、修正内容およびstable@が追加されました]

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 19 Jul 2026 · Last source change 17 Aug 2026, 04:50 UTC · CWE-787 · Out-of-bounds Write

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-45460
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    kernel as a component of Red Hat Enterprise Linux 10; kernel-64k as a component of Red Hat Enterprise Linux 10; kernel-64k-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-64k-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 116 more · Fixed: kernel-64k-debug-debuginfo-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-debug-devel-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-debug-devel-matched-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-debuginfo-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-devel-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-devel-matched-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-687.54.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-687.54.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-687.54.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-687.54.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-687.54.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-687.54.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-687.54.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-687.54.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-687.54.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-687.54.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-687.54.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-687.54.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-aarch64-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-ppc64le-0:5.14.0-687.54.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-s390x-0:5.14.0-687.54.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-x86_64-0:5.14.0-687.54.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-687.54.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-687.54.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-687.54.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); and 273 more
    After
    kernel as a component of Red Hat Enterprise Linux 10; kernel-64k as a component of Red Hat Enterprise Linux 10; kernel-64k-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-64k-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 69 more · Fixed: kernel-64k-debug-debuginfo-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-debug-devel-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-debug-devel-matched-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-debuginfo-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-devel-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-devel-matched-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-687.54.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-687.54.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-687.54.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-687.54.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-687.54.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-687.54.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-687.54.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-687.54.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-687.54.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-687.54.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-687.54.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-687.54.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-aarch64-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-ppc64le-0:5.14.0-687.54.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-s390x-0:5.14.0-687.54.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-x86_64-0:5.14.0-687.54.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-687.54.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-687.54.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-687.54.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-687.54.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); and 423 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-45460↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-63794 · cve.blacktree.nl