Full vulnerability report · 2026

CVE-2026-31592High confidence

KVM: SEV: Protect all of sev_mem_enc_register_region() with kvm->lock

Linux · Linux

5.5MediumCVSS 3.1

Recommended action

Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 22 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product

Operational reassessment

Published severity in operational context

Open reassessment dashboard →

Published severityMediumOperational priority:Low, lowered one band.downgradedsince 14 Jun 2026

Evidence used

No CISA KEV confirmation is currently recorded.
Exploitation requires an existing local or physical foothold with privileges.
EPSS is 0.16% 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

Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.

Cross-source reconciliation

Remediation availability differs by product scope

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

Debian Security Tracker, Canonical Ubuntu Security: 22 affected package states with no published fix

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 22 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 release	Source package	Vendor state	Fixed version	Evidence
Debian trixietrixie · source	`linux`	Affected, no fix publishedDebian currently tracks this release as open.	`Not published in this feed`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`linux`	Affected, no fix publishedDebian currently tracks this release as open.	`Not published in this feed`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.19.14-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.19.14-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-fde`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-nvidia`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gke`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gkeop`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-ibm`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-lowlatency`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-tegra`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-xilinx`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 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.

1 current

CVE-2026-31592 · CSAF 2.0 · revision 21 · interimSUSE Product Security TeamCVE-2026-31592

284 known affected

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

kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
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

Summary: In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm->lock Take and hold kvm->lock for before checking sev_guest() in sev_mem_enc_register_region(), as sev_guest() isn't stable unless kvm->lock is held (or KVM can guarantee KVM_SEV_INIT{2} has completed and can't rollack state). If KVM_SEV_INIT{2} fails, KVM can end up trying to add to a not-yet-initialized sev->regions_list, e.g. triggering a #GP Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 110 UID: 0 PID: 72717 Comm: syz.15.11462 Tainted: G U W O 6.16.0-smp-DEV #1 NONE Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.52.0-0 10/28/2024 RIP: 0010:sev_mem_enc_register_region+0x3f0/0x4f0 ../include/linux/list.h:83 Code: 80 3c 04 00 74 08 4c 89 ff e8 f1 c7 a2 00 49 39 ed 0f 84 c6 00 RSP: 0018:ffff88838647fbb8 EFLAGS: 00010256 RAX: dffffc0000000000 RBX: 1ffff92015cf1e0b RCX: dffffc0000000000 RDX: 0000000000000000 RSI: 0000000000001000 RDI: ffff888367870000 RBP: ffffc900ae78f050 R08: ffffea000d9e0007 R09: 1ffffd4001b3c000 R10: dffffc0000000000 R11: fffff94001b3c001 R12: 0000000000000000 R13: ffff8982ab0bde00 R14: ffffc900ae78f058 R15: 0000000000000000 FS: 00007f34e9dc66c0(0000) GS:ffff89ee64d33000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fe180adef98 CR3: 000000047210e000 CR4: 0000000000350ef0 Call Trace: kvm_arch_vm_ioctl+0xa72/0x1240 ../arch/x86/kvm/x86.c:7371 kvm_vm_ioctl+0x649/0x990 ../virt/kvm/kvm_main.c:5363 __se_sys_ioctl+0x101/0x170 ../fs/ioctl.c:51 do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x6f/0x1f0 ../arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f34e9f7e9a9 Code: 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f34e9dc6038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f34ea1a6080 RCX: 00007f34e9f7e9a9 RDX: 0000200000000280 RSI: 000000008010aebb RDI: 0000000000000007 RBP: 00007f34ea000d69 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f34ea1a6080 R15: 00007ffce77197a8 with a syzlang reproducer that looks like: syz_kvm_add_vcpu$x86(0x0, &(0x7f0000000040)={0x0, &(0x7f0000000180)=ANY=[], 0x70}) (async) syz_kvm_add_vcpu$x86(0x0, &(0x7f0000000080)={0x0, &(0x7f0000000180)=ANY=[@ANYBLOB="..."], 0x4f}) (async) r0 = openat$kvm(0xffffffffffffff9c, &(0x7f0000000200), 0x0, 0x0) r1 = ioctl$KVM_CREATE_VM(r0, 0xae01, 0x0) r2 = openat$kvm(0xffffffffffffff9c, &(0x7f0000000240), 0x0, 0x0) r3 = ioctl$KVM_CREATE_VM(r2, 0xae01, 0x0) ioctl$KVM_SET_CLOCK(r3, 0xc008aeba, &(0x7f0000000040)={0x1, 0x8, 0x0, 0x5625e9b0}) (async) ioctl$KVM_SET_PIT2(r3, 0x8010aebb, &(0x7f0000000280)={[...], 0x5}) (async) ioctl$KVM_SET_PIT2(r1, 0x4070aea0, 0x0) (async) r4 = ioctl$KVM_CREATE_VM(0xffffffffffffffff, 0xae01, 0x0) openat$kvm(0xffffffffffffff9c, 0x0, 0x0, 0x0) (async) ioctl$KVM_SET_USER_MEMORY_REGION(r4, 0x4020ae46, &(0x7f0000000400)={0x0, 0x0, 0x0, 0x2000, &(0x7f0000001000/0x2000)=nil}) (async) r5 = ioctl$KVM_CREATE_VCPU(r4, 0xae41, 0x2) close(r0) (async) openat$kvm(0xffffffffffffff9c, &(0x7f0000000000), 0x8000, 0x0) (async) ioctl$KVM_SET_GUEST_DEBUG(r5, 0x4048ae9b, &(0x7f0000000300)={0x4376ea830d46549b, 0x0, [0x46, 0x0, 0x0, 0x0, 0x0, 0x1000]}) (async) ioctl$KVM_RUN(r5, 0xae80, 0x0) Opportunistically use guard() to avoid having to define a new error label and goto usage.
Remediation: To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

Recommended actionPatch only the product branches with a verified fix

Fix availability varies by product

What, why and how

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm->lock Take and hold kvm->lock for before checking sev_guest() in sev_mem_enc_register_region(), as sev_guest() isn't stable unless kvm->lock is held (or KVM can guarantee KVM_SEV_INIT{2} has completed and can't rollack state). If KVM_SEV_INIT{2} fails, KVM can end up trying to add to a not-yet-initialized sev->regions_list, e.g. triggering a #GP Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 110 UID: 0 PID: 72717 Comm: syz.15.11462 Tainted: G U W O 6.16.0-smp-DEV #1 NONE Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.52.0-0 10/28/2024 RIP: 0010:sev_mem_enc_register_region+0x3f0/0x4f0 ../include/linux/list.h:83 Code: <41> 80 3c 04 00 74 08 4c 89 ff e8 f1 c7 a2 00 49 39 ed 0f 84 c6 00 RSP: 0018:ffff88838647fbb8 EFLAGS: 00010256 RAX: dffffc0000000000 RBX: 1ffff92015cf1e0b RCX: dffffc0000000000 RDX: 0000000000000000 RSI: 0000000000001000 RDI: ffff888367870000 RBP: ffffc900ae78f050 R08: ffffea000d9e0007 R09: 1ffffd4001b3c000 R10: dffffc0000000000 R11: fffff94001b3c001 R12: 0000000000000000 R13: ffff8982ab0bde00 R14: ffffc900ae78f058 R15: 0000000000000000 FS: 00007f34e9dc66c0(0000) GS:ffff89ee64d33000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fe180adef98 CR3: 000000047210e000 CR4: 0000000000350ef0 Call Trace: <TASK> kvm_arch_vm_ioctl+0xa72/0x1240 ../arch/x86/kvm/x86.c:7371 kvm_vm_ioctl+0x649/0x990 ../virt/kvm/kvm_main.c:5363 __se_sys_ioctl+0x101/0x170 ../fs/ioctl.c:51 do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x6f/0x1f0 ../arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f34e9f7e9a9 Code: <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f34e9dc6038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f34ea1a6080 RCX: 00007f34e9f7e9a9 RDX: 0000200000000280 RSI: 000000008010aebb RDI: 0000000000000007 RBP: 00007f34ea000d69 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f34ea1a6080 R15: 00007ffce77197a8 </TASK> with a syzlang reproducer that looks like: syz_kvm_add_vcpu$x86(0x0, &(0x7f0000000040)={0x0, &(0x7f0000000180)=ANY=[], 0x70}) (async) syz_kvm_add_vcpu$x86(0x0, &(0x7f0000000080)={0x0, &(0x7f0000000180)=ANY=[@ANYBLOB="..."], 0x4f}) (async) r0 = openat$kvm(0xffffffffffffff9c, &(0x7f0000000200), 0x0, 0x0) r1 = ioctl$KVM_CREATE_VM(r0, 0xae01, 0x0) r2 = openat$kvm(0xffffffffffffff9c, &(0x7f0000000240), 0x0, 0x0) r3 = ioctl$KVM_CREATE_VM(r2, 0xae01, 0x0) ioctl$KVM_SET_CLOCK(r3, 0xc008aeba, &(0x7f0000000040)={0x1, 0x8, 0x0, 0x5625e9b0}) (async) ioctl$KVM_SET_PIT2(r3, 0x8010aebb, &(0x7f0000000280)={[...], 0x5}) (async) ioctl$KVM_SET_PIT2(r1, 0x4070aea0, 0x0) (async) r4 = ioctl$KVM_CREATE_VM(0xffffffffffffffff, 0xae01, 0x0) openat$kvm(0xffffffffffffff9c, 0x0, 0x0, 0x0) (async) ioctl$KVM_SET_USER_MEMORY_REGION(r4, 0x4020ae46, &(0x7f0000000400)={0x0, 0x0, 0x0, 0x2000, &(0x7f0000001000/0x2000)=nil}) (async) r5 = ioctl$KVM_CREATE_VCPU(r4, 0xae41, 0x2) close(r0) (async) openat$kvm(0xffffffffffffff9c, &(0x7f0000000000), 0x8000, 0x0) (async) ioctl$KVM_SET_GUEST_DEBUG(r5, 0x4048ae9b, &(0x7f0000000300)={0x4376ea830d46549b, 0x0, [0x46, 0x0, 0x0, 0x0, 0x0, 0x1000]}) (async) ioctl$KVM_RUN(r5, 0xae80, 0x0) Opportunistically use guard() to avoid having to define a new error label and goto usage.

What

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

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 → NULL Pointer Dereference → 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-476 ↗
CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.
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:N/I:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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-476

Official authority intelligence

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

ENISA EUVD · EUVD-2026-25485Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

BSI · German · WID-SEC-2026-1279Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, welche zu einem Denial-of-Service-Zustand, einer Rechteausweitung, der Ausführung von Code oder einer Speicherbeschädigung führen könnten.

Official advisory ↗

Cyber Security Agency of Singapore · English · CSA-SB-20260429Security Bulletin 29 Apr 2026

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

Official advisory ↗

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

d?id=CVE-2026-31576 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31582 https://www.cve.org/CVERecord?id=CVE-2026-31582 Référence CVE CVE-2026-31583 https://www.cve.org/CVERecord?id=CVE-2026-31583 Référence CVE CVE-2026-31585 https://www.cve.org/CVERecord?id=CVE-2026-31585 Référence CVE CVE-2026-31587 https://www.cve.org/CVERecord?id=CVE-2026-31587 Référence CVE CVE-2026-31590 https://www.cve.org/CVERecord?id=CVE-2026-31590 Référence CVE CVE-2026-31591 https://www.cve.org/CVERecord?id=CVE-2026-31591 Référence CVE CVE-2026-31592 https://www.cve.org/CVERecord?id=CVE-2026-31592 Référence CVE CVE-2026-31593 https://www.cve.org/CVERecord?id=CVE-2026-31593 Référence CVE CVE-2026-31595 https://www.cve.org/CVERecord?id=CVE-2026-31595 Référence CVE CVE-2026-31598 https://www.cve.org/CVERecord?id=CVE-2026-31598 Référence CVE CVE-2026-31599 https://www.cve.org/CVERecord?id=CVE-2026-31599 Référence CVE CVE-2026-31602 https://www.cve.org/CVERecord?id=CVE-2026-31602 Référence CVE CVE-2026-31603 https://www.cve.org/CVERecord?id=CVE-2026-31603 Référence CVE CVE-2026-31604 https://www.cve.org/CVERecord?id=CVE-2026-31604 Référence CVE CVE-2026-31605 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

d?id=CVE-2026-31583 Référence CVE CVE-2026-31584 https://www.cve.org/CVERecord?id=CVE-2026-31584 Référence CVE CVE-2026-31585 https://www.cve.org/CVERecord?id=CVE-2026-31585 Référence CVE CVE-2026-31586 https://www.cve.org/CVERecord?id=CVE-2026-31586 Référence CVE CVE-2026-31587 https://www.cve.org/CVERecord?id=CVE-2026-31587 Référence CVE CVE-2026-31588 https://www.cve.org/CVERecord?id=CVE-2026-31588 Référence CVE CVE-2026-31589 https://www.cve.org/CVERecord?id=CVE-2026-31589 Référence CVE CVE-2026-31590 https://www.cve.org/CVERecord?id=CVE-2026-31590 Référence CVE CVE-2026-31591 https://www.cve.org/CVERecord?id=CVE-2026-31591 Référence CVE CVE-2026-31592 https://www.cve.org/CVERecord?id=CVE-2026-31592 Référence CVE CVE-2026-31593 https://www.cve.org/CVERecord?id=CVE-2026-31593 Référence CVE CVE-2026-31594 https://www.cve.org/CVERecord?id=CVE-2026-31594 Référence CVE CVE-2026-31595 https://www.cve.org/CVERecord?id=CVE-2026-31595 Référence CVE CVE-2026-31596 https://www.cve.org/CVERecord?id=CVE-2026-31596 Référence CVE CVE-2026-31597 https://www.cve.org/CVERecord?id=CVE-2026-31597 Référence CVE CVE-2026-31598 https://www.cve.org/CVERecord?id=CVE-2026-31598 Référence CVE CVE-2026-31599 https://www.cve.org/CVERecord?id=CVE-2026-31599 Référence CVE CVE-2026-31600 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0900Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-23451 Référence CVE CVE-2026-31462 https://www.cve.org/CVERecord?id=CVE-2026-31462 Référence CVE CVE-2026-31499 https://www.cve.org/CVERecord?id=CVE-2026-31499 Référence CVE CVE-2026-31502 https://www.cve.org/CVERecord?id=CVE-2026-31502 Référence CVE CVE-2026-31505 https://www.cve.org/CVERecord?id=CVE-2026-31505 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=CVE-2026-31533 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=CVE-2026-31580 Référence CVE CVE-2026-31586 https://www.cve.org/CVERecord?id=CVE-2026-31586 Référence CVE CVE-2026-31592 https://www.cve.org/CVERecord?id=CVE-2026-31592 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31677 https://www.cve.org/CVERecord?id=CVE-2026-31677 Référence CVE CVE-2026-31680 https://www.cve.org/CVERecord?id=CVE-2026-31680 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 Référence CVE CVE-2026-31758 https://www.cve.org/CVERecord?id=CVE-2026-31758 Référence CVE CVE-2026-31771 https://www.cve.org/CVERecord?id=CVE-2026-31771 Référence CVE CVE-2026-31773 https://www.cve.org/CVERecord?id=CVE-2026-31773 Référence CVE CVE-2026-31781 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0864Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-31502 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31554 https://www.cve.org/CVERecord?id=CVE-2026-31554 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31560 https://www.cve.org/CVERecord?id=CVE-2026-31560 Référence CVE CVE-2026-31590 https://www.cve.org/CVERecord?id=CVE-2026-31590 Référence CVE CVE-2026-31592 https://www.cve.org/CVERecord?id=CVE-2026-31592 Référence CVE CVE-2026-31593 https://www.cve.org/CVERecord?id=CVE-2026-31593 Référence CVE CVE-2026-31596 https://www.cve.org/CVERecord?id=CVE-2026-31596 Référence CVE CVE-2026-31613 https://www.cve.org/CVERecord?id=CVE-2026-31613 Référence CVE CVE-2026-31614 https://www.cve.org/CVERecord?id=CVE-2026-31614 Référence CVE CVE-2026-31629 https://www.cve.org/CVERecord?id=CVE-2026-31629 Référence CVE CVE-2026-31647 https://www.cve.org/CVERecord?id=CVE-2026-31647 Référence CVE CVE-2026-31655 https://www.cve.org/CVERecord?id=CVE-2026-31655 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0833Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-31500 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31554 https://www.cve.org/CVERecord?id=CVE-2026-31554 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31560 https://www.cve.org/CVERecord?id=CVE-2026-31560 Référence CVE CVE-2026-31590 https://www.cve.org/CVERecord?id=CVE-2026-31590 Référence CVE CVE-2026-31592 https://www.cve.org/CVERecord?id=CVE-2026-31592 Référence CVE CVE-2026-31593 https://www.cve.org/CVERecord?id=CVE-2026-31593 Référence CVE CVE-2026-31596 https://www.cve.org/CVERecord?id=CVE-2026-31596 Référence CVE CVE-2026-31613 https://www.cve.org/CVERecord?id=CVE-2026-31613 Référence CVE CVE-2026-31614 https://www.cve.org/CVERecord?id=CVE-2026-31614 Référence CVE CVE-2026-31629 https://www.cve.org/CVERecord?id=CVE-2026-31629 Référence CVE CVE-2026-31655 https://www.cve.org/CVERecord?id=CVE-2026-31655 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2026-013215LinuxのLinux KernelにおけるNULL ポインタデリファレンスに関する脆弱性

LinuxカーネルにおけるKVMのSEV機能に関する脆弱性が修正されました。具体的には、sev_mem_enc_register_region()関数内でkvm-lockを適切に保持し、sev_guest()の呼び出しを安全にしています。この修正により、KVM_SEV_INITの失敗時に初期化されていない領域リストへの不正アクセスによって引き起こされる一般保護違反などのクラッシュを防止します。

Official advisory ↗

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: kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
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
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP2
reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP3
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP3
reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
and 254 more
Fixed: Linux: < 4.16, 6.18.24 ≤ 6.18.*, 6.19.14 ≤ 6.19.*, 7.0.1 ≤ 7.0.*, 7.1 ≤ *
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.

Evidence and provenance

Published 24 Apr 2026 · Last source change 14 Jun 2026, 17:42 UTC · CWE-476 · NULL Pointer Dereference

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-25485

Product sourceVendor CSAF · SUSE Product Security Team

Remediation sourceVendor CSAF · SUSE Product Security Team

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 ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

2026-04-24CVE published

2026-06-14Fixed release or patch reference recorded

ENISA EUVD · EUVD-2026-25485↗Vendor CSAF · SUSE Product Security Team↗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.

KVM: SEV: Protect all of sev_mem_enc_register_region() with kvm->lock

Published severity in operational context

Evidence used

Compensating controls

Verification

Remediation availability differs by product scope

Release-specific package status

Authoritative vendor CSAF and VEX advisories

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

ENISA European Vulnerability Database

EUVD-2026-25485

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication