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

KVM: SVM: Update x2APIC MSR intercepts if AVIC is inhibited while L2 is active

Linux · Linux

8.2HighCVSS 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.

25 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.105-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.107-1~deb12u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.8-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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 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.

2 current
CVE-2026-74516 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: KVM: SVM: Update x2APIC MSR intercepts if AVIC is inhibited while L2 is active
185 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 KVM (Kernel-based Virtual Machine). When the Advanced Virtual Interrupt Controller (AVIC) is inhibited while a nested guest (L2) is active, KVM fails to properly update x2APIC MSR intercepts for the primary guest (L1). This allows the L1 guest to read the host's APIC state, send arbitrary interrupts, and change task priority, ultimately leading to a Denial of Service (DoS) of the host system.
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-74516 · CSAF 2.0 · revision 13 · interimSUSE Product Security TeamCVE-2026-74516
42 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP7
  • kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP7
  • kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Update x2APIC MSR intercepts if AVIC is inhibited while L2 is active Always update x2APIC MSR intercepts for L1 when AVIC is deactivated, even if L2 is active and KVM is using a separate MSR bitmap to run L2. If AVIC is fully enabled prior to running L2, and is then inhibited while L2 is active (for a VM-scoped inhibit), then KVM will run L1 with AVIC disabled, but with x2APIC MSR intercepts disabled, i.e. will allow L1 to read most of the host's APIC state, send arbitrary interrupts, change task priority, and ultimately trivially DoS the host. E.g. sending a self-IPI in L1 on HYPERV_REENLIGHTENMENT_VECTOR, 0xee, with CONFIG_HYPERV=n in the host kernel as a "safe" PoC, yields: Spurious interrupt (vector 0xee) on CPU#425. Acked And hacking KVM to abuse kvm_set_posted_intr_wakeup_handler() to register a handler and WARN on POSTED_INTR_WAKEUP_VECTOR yields: ------------[ cut here ]------------ WARNING: arch/x86/kvm/svm/svm.c:5594 at pi_wakeup_handler+0x9/0x10 [kvm_amd], CPU#156: nested_x2apic_t/316940 CPU: 156 UID: 0 PID: 316940 Comm: nested_x2apic_t Tainted: G S U Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER Hardware name: Google Astoria-Turin/astoria, BIOS 0.20260209.0-0 02/09/2026 RIP: 0010:pi_wakeup_handler+0x9/0x10 [kvm_amd] Call Trace: sysvec_kvm_posted_intr_wakeup_ipi+0x64/0x80 asm_sysvec_kvm_posted_intr_wakeup_ipi+0x1a/0x20 RIP: 0010:vcpu_run+0x1430/0x1e40 [kvm] kvm_arch_vcpu_ioctl_run+0x2c1/0x600 [kvm] kvm_vcpu_ioctl+0x580/0x6b0 [kvm] __se_sys_ioctl+0x6d/0xb0 do_syscall_64+0x10a/0x480 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x46ff4b ---[ end trace 0000000000000000 ]---
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-59709

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Update x2APIC MSR intercepts if AVIC is inhibited while L2 is active Always update x2APIC MSR intercepts for L1 when AVIC is deactivated, even if L2 is active and KVM is using a separate MSR bitmap to run L2. If AVIC is fully enabled prior to running L2, and is then inhibited while L2 is active (for a VM-scoped inhibit), then KVM will run L1 with AVIC disabled, but with x2APIC MSR intercepts disabled, i.e. will allow L1 to read most of the host's APIC state, send arbitrary interrupts, change task priority, and ultimately trivially DoS the host. E.g. sending a self-IPI in L1 on HYPERV_REENLIGHTENMENT_VECTOR, 0xee, with CONFIG_HYPERV=n in the host kernel as a "safe" PoC, yields: Spurious interrupt (vector 0xee) on CPU#425. Acked And hacking KVM to abuse kvm_set_posted_intr_wakeup_handler() to register a handler and WARN on POSTED_INTR_WAKEUP_VECTOR yields: ------------[ cut here ]------------ WARNING: arch/x86/kvm/svm/svm.c:5594 at pi_wakeup_handler+0x9/0x10 [kvm_amd], CPU#156: nested_x2apic_t/316940 CPU: 156 UID: 0 PID: 316940 Comm: nested_x2apic_t Tainted: G S U Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER Hardware name: Google Astoria-Turin/astoria, BIOS 0.20260209.0-0 02/09/2026 RIP: 0010:pi_wakeup_handler+0x9/0x10 [kvm_amd] Call Trace: <IRQ> sysvec_kvm_posted_intr_wakeup_ipi+0x64/0x80 </IRQ> <TASK> asm_sysvec_kvm_posted_intr_wakeup_ipi+0x1a/0x20 RIP: 0010:vcpu_run+0x1430/0x1e40 [kvm] kvm_arch_vcpu_ioctl_run+0x2c1/0x600 [kvm] kvm_vcpu_ioctl+0x580/0x6b0 [kvm] __se_sys_ioctl+0x6d/0xb0 do_syscall_64+0x10a/0x480 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x46ff4b </TASK> ---[ end trace 0000000000000000 ]---

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
8.2 · CVSS 3.1
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: Update x2APIC MSR intercepts if AVIC is inhibited while L2 is active Always update x2APIC MSR intercepts for L1 when AVIC is deactivated, even if L2 is active and KVM is using a separate MSR bitmap to run L2. If AVIC is fully enabled prior to running L2, and is then inhibited while L2 is active (for a VM-scoped inhibit), then KVM will run L1 with AVIC disabled, but with x2APIC MSR intercepts disabled, i.e. will allow L1 to read most of the host's APIC state, send arbitrary interrupts, change task priority, and ultimately trivially DoS the host. E.g. sending a self-IPI in L1 on HYPERV_REENLIGHTENMENT_VECTOR, 0xee, with CONFIG_HYPERV=n in the host kernel as a "safe" PoC, yields: Spurious interrupt (vector 0xee) on CPU#425. Acked And hacking KVM to abuse kvm_set_posted_intr_wakeup_handler() to register a handler and WARN on POSTED_INTR_WAKEUP_VECTOR yields: ------------[ cut here ]------------ WARNING: arch/x86/kvm/svm/svm.c:5594 at pi_wakeup_handler+0x9/0x10 [kvm_amd], CPU#156: nested_x2apic_t/316940 CPU: 156 UID: 0 PID: 316940 Comm: nested_x2apic_t Tainted: G S U Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER Hardware name: Google Astoria-Turin/astoria, BIOS 0.20260209.0-0 02/09/2026 RIP: 0010:pi_wakeup_handler+0x9/0x10 [kvm_amd] Call Trace: <IRQ> sysvec_kvm_posted_intr_wakeup_ipi+0x64/0x80 </IRQ> <TASK> asm_sysvec_kvm_posted_intr_wakeup_ipi+0x1a/0x20 RIP: 0010:vcpu_run+0x1430/0x1e40 [kvm] kvm_arch_vcpu_ioctl_run+0x2c1/0x600 [kvm] kvm_vcpu_ioctl+0x580/0x6b0 [kvm] __se_sys_ioctl+0x6d/0xb0 do_syscall_64+0x10a/0x480 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x46ff4b </TASK> ---[ end trace 0000000000000000 ]---

What

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Update x2APIC MSR intercepts if AVIC is inhibited while L2 is active Always update x2APIC MSR intercepts for L1 when AVIC is deactivated, even if L2 is active and KVM is using a separate MSR bitmap to run L2. If AVIC is fully enabled prior to running L2, and is then inhibited while L2 is active (for a VM-scoped inhibit), then KVM will run L1 with AVIC disabled, but with x2APIC MSR intercepts disabled, i.e. will allow L1 to read most of the host's APIC state, send arbitrary interrupts, change task priority, and ultimately trivially DoS the host. E.g. sending a self-IPI in L1 on HYPERV_REENLIGHTENMENT_VECTOR, 0xee, with CONFIG_HYPERV=n in the host kernel as a "safe" PoC, yields: Spurious interrupt (vector 0xee) on CPU#425. Acked And hacking KVM to abuse kvm_set_posted_intr_wakeup_handler() to register a handler and WARN on POSTED_INTR_WAKEUP_VECTOR yields: ------------[ cut here ]------------ WARNING: arch/x86/kvm/svm/svm.c:5594 at pi_wakeup_handler+0x9/0x10 [kvm_amd], CPU#156: nested_x2apic_t/316940 CPU: 156 UID: 0 PID: 316940 Comm: nested_x2apic_t Tainted: G S U Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER Hardware name: Google Astoria-Turin/astoria, BIOS 0.20260209.0-0 02/09/2026 RIP: 0010:pi_wakeup_handler+0x9/0x10 [kvm_amd] Call Trace: <IRQ> sysvec_kvm_posted_intr_wakeup_ipi+0x64/0x80 </IRQ> <TASK> asm_sysvec_kvm_posted_intr_wakeup_ipi+0x1a/0x20 RIP: 0010:vcpu_run+0x1430/0x1e40 [kvm] kvm_arch_vcpu_ioctl_run+0x2c1/0x600 [kvm] kvm_vcpu_ioctl+0x580/0x6b0 [kvm] __se_sys_ioctl+0x6d/0xb0 do_syscall_64+0x10a/0x480 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x46ff4b </TASK> ---[ end trace 0000000000000000 ]---

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with elevated 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: Update x2APIC MSR intercepts if AVIC is inhibited while L2 is active Always update x2APIC MSR intercepts for L1 when AVIC is deactivated, even if L2 is active and KVM is using a separate MSR bitmap to run L2. If AVIC is fully enabled prior to running L2, and is then inhibited while L2 is active (for a VM-scoped inhibit), then KVM will run L1 with AVIC disabled, but with x2APIC MSR intercepts disabled, i.e. will allow L1 to read most of the host's APIC state, send arbitrary interrupts, change task priority, and ultimately trivially DoS the host. E.g. sending a self-IPI in L1 on HYPERV_REENLIGHTENMENT_VECTOR, 0xee, with CONFIG_HYPERV=n in the host kernel as a "safe" PoC, yields: Spurious interrupt (vector 0xee) on CPU#425. Acked And hacking KVM to abuse kvm_set_posted_intr_wakeup_handler() to register a handler and WARN on POSTED_INTR_WAKEUP_VECTOR yields: ------------[ cut here ]------------ WARNING: arch/x86/kvm/svm/svm.c:5594 at pi_wakeup_handler+0x9/0x10 [kvm_amd], CPU#156: nested_x2apic_t/316940 CPU: 156 UID: 0 PID: 316940 Comm: nested_x2apic_t Tainted: G S U Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER Hardware name: Google Astoria-Turin/astoria, BIOS 0.20260209.0-0 02/09/2026 RIP: 0010:pi_wakeup_handler+0x9/0x10 [kvm_amd] Call Trace: <IRQ> sysvec_kvm_posted_intr_wakeup_ipi+0x64/0x80 </IRQ> <TASK> asm_sysvec_kvm_posted_intr_wakeup_ipi+0x1a/0x20 RIP: 0010:vcpu_run+0x1430/0x1e40 [kvm] kvm_arch_vcpu_ioctl_run+0x2c1/0x600 [kvm] kvm_vcpu_ioctl+0x580/0x6b0 [kvm] __se_sys_ioctl+0x6d/0xb0 do_syscall_64+0x10a/0x480 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x46ff4b </TASK> ---[ end trace 0000000000000000 ]---

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with elevated 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 → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
High: elevated access is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
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:H/UI:N/S:C/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.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security 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.
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-59709Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Update x2APIC MSR intercepts if AVIC is inhibited while L2 is active Always update x2APIC MSR intercepts for L1 when AVIC is deactivated, even if L2 is active and KVM is using a separate MSR bitmap to run L2. If AVIC is fully enabled prior to running L2, and is then inhibited while L2 is active (for a VM-scoped inhibit), then KVM will run L1 with AVIC disabled, but with x2APIC MSR intercepts disabled, i.e. will allow L1 to read most of the host's APIC state, send arbitrary interrupts, change task priority, and ultimately trivially DoS the host. E.g. sending a self-IPI in L1 on HYPERV_REENLIGHTENMENT_VECTOR, 0xee, with CONFIG_HYPERV=n in the host kernel as a "safe" PoC, yields: Spurious interrupt (vector 0xee) on CPU#425. Acked And hacking KVM to abuse kvm_set_posted_intr_wakeup_handler() to register a handler and WARN on POSTED_INTR_WAKEUP_VECTOR yields: ------------[ cut here ]------------ WARNING: arch/x86/kvm/svm/svm.c:5594 at pi_wakeup_handler+0x9/0x10 [kvm_amd], CPU#156: nested_x2apic_t/316940 CPU: 156 UID: 0 PID: 316940 Comm: nested_x2apic_t Tainted: G S U Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER Hardware name: Google Astoria-Turin/astoria, BIOS 0.20260209.0-0 02/09/2026 RIP: 0010:pi_wakeup_handler+0x9/0x10 [kvm_amd] Call Trace: <IRQ> sysvec_kvm_posted_intr_wakeup_ipi+0x64/0x80 </IRQ> <TASK> asm_sysvec_kvm_posted_intr_wakeup_ipi+0x1a/0x20 RIP: 0010:vcpu_run+0x1430/0x1e40 [kvm] kvm_arch_vcpu_ioctl_run+0x2c1/0x600 [kvm] kvm_vcpu_ioctl+0x580/0x6b0 [kvm] __se_sys_ioctl+0x6d/0xb0 do_syscall_64+0x10a/0x480 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x46ff4b </TASK> ---[ end trace 0000000000000000 ]---

Official EUVD record ↗
BSI · German · WID-SEC-2026-2852Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.

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

d?id=CVE-2026-74504 Référence CVE CVE-2026-74505 https://www.cve.org/CVERecord?id=CVE-2026-74505 Référence CVE CVE-2026-74507 https://www.cve.org/CVERecord?id=CVE-2026-74507 Référence CVE CVE-2026-74508 https://www.cve.org/CVERecord?id=CVE-2026-74508 Référence CVE CVE-2026-74509 https://www.cve.org/CVERecord?id=CVE-2026-74509 Référence CVE CVE-2026-74510 https://www.cve.org/CVERecord?id=CVE-2026-74510 Référence CVE CVE-2026-74512 https://www.cve.org/CVERecord?id=CVE-2026-74512 Référence CVE CVE-2026-74514 https://www.cve.org/CVERecord?id=CVE-2026-74514 Référence CVE CVE-2026-74515 https://www.cve.org/CVERecord?id=CVE-2026-74515 Référence CVE CVE-2026-74516 https://www.cve.org/CVERecord?id=CVE-2026-74516 Référence CVE CVE-2026-74517 https://www.cve.org/CVERecord?id=CVE-2026-74517 Référence CVE CVE-2026-74518 https://www.cve.org/CVERecord?id=CVE-2026-74518 Référence CVE CVE-2026-74519 https://www.cve.org/CVERecord?id=CVE-2026-74519 Référence CVE CVE-2026-74522 https://www.cve.org/CVERecord?id=CVE-2026-74522 Référence CVE CVE-2026-74523 https://www.cve.org/CVERecord?id=CVE-2026-74523 Référence CVE CVE-2026-74524 https://www.cve.org/CVERecord?id=CVE-2026-74524 Référence CVE CVE-2026-74525 https://www.cve.org/CVERecord?id=CVE-2026-74525 Référence CVE CVE-2026-74531 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-74474 Référence CVE CVE-2026-74481 https://www.cve.org/CVERecord?id=CVE-2026-74481 Référence CVE CVE-2026-74482 https://www.cve.org/CVERecord?id=CVE-2026-74482 Référence CVE CVE-2026-74488 https://www.cve.org/CVERecord?id=CVE-2026-74488 Référence CVE CVE-2026-74495 https://www.cve.org/CVERecord?id=CVE-2026-74495 Référence CVE CVE-2026-74496 https://www.cve.org/CVERecord?id=CVE-2026-74496 Référence CVE CVE-2026-74509 https://www.cve.org/CVERecord?id=CVE-2026-74509 Référence CVE CVE-2026-74510 https://www.cve.org/CVERecord?id=CVE-2026-74510 Référence CVE CVE-2026-74512 https://www.cve.org/CVERecord?id=CVE-2026-74512 Référence CVE CVE-2026-74516 https://www.cve.org/CVERecord?id=CVE-2026-74516 Référence CVE CVE-2026-74518 https://www.cve.org/CVERecord?id=CVE-2026-74518 Référence CVE CVE-2026-74527 https://www.cve.org/CVERecord?id=CVE-2026-74527 Référence CVE CVE-2026-74537 https://www.cve.org/CVERecord?id=CVE-2026-74537 Référence CVE CVE-2026-74548 https://www.cve.org/CVERecord?id=CVE-2026-74548 Référence CVE CVE-2026-74550 https://www.cve.org/CVERecord?id=CVE-2026-74550 Référence CVE CVE-2026-74556 https://www.cve.org/CVERecord?id=CVE-2026-74556 Référence CVE CVE-2026-74563 https://www.cve.org/CVERecord?id=CVE-2026-74563 Référence CVE CVE-2026-74566 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-74499 Référence CVE CVE-2026-74505 https://www.cve.org/CVERecord?id=CVE-2026-74505 Référence CVE CVE-2026-74507 https://www.cve.org/CVERecord?id=CVE-2026-74507 Référence CVE CVE-2026-74508 https://www.cve.org/CVERecord?id=CVE-2026-74508 Référence CVE CVE-2026-74509 https://www.cve.org/CVERecord?id=CVE-2026-74509 Référence CVE CVE-2026-74510 https://www.cve.org/CVERecord?id=CVE-2026-74510 Référence CVE CVE-2026-74512 https://www.cve.org/CVERecord?id=CVE-2026-74512 Référence CVE CVE-2026-74514 https://www.cve.org/CVERecord?id=CVE-2026-74514 Référence CVE CVE-2026-74515 https://www.cve.org/CVERecord?id=CVE-2026-74515 Référence CVE CVE-2026-74516 https://www.cve.org/CVERecord?id=CVE-2026-74516 Référence CVE CVE-2026-74518 https://www.cve.org/CVERecord?id=CVE-2026-74518 Référence CVE CVE-2026-74519 https://www.cve.org/CVERecord?id=CVE-2026-74519 Référence CVE CVE-2026-74522 https://www.cve.org/CVERecord?id=CVE-2026-74522 Référence CVE CVE-2026-74523 https://www.cve.org/CVERecord?id=CVE-2026-74523 Référence CVE CVE-2026-74525 https://www.cve.org/CVERecord?id=CVE-2026-74525 Référence CVE CVE-2026-74540 https://www.cve.org/CVERecord?id=CVE-2026-74540 Référence CVE CVE-2026-74546 https://www.cve.org/CVERecord?id=CVE-2026-74546 Référence CVE CVE-2026-74547 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-74474 Référence CVE CVE-2026-74481 https://www.cve.org/CVERecord?id=CVE-2026-74481 Référence CVE CVE-2026-74482 https://www.cve.org/CVERecord?id=CVE-2026-74482 Référence CVE CVE-2026-74488 https://www.cve.org/CVERecord?id=CVE-2026-74488 Référence CVE CVE-2026-74495 https://www.cve.org/CVERecord?id=CVE-2026-74495 Référence CVE CVE-2026-74496 https://www.cve.org/CVERecord?id=CVE-2026-74496 Référence CVE CVE-2026-74509 https://www.cve.org/CVERecord?id=CVE-2026-74509 Référence CVE CVE-2026-74510 https://www.cve.org/CVERecord?id=CVE-2026-74510 Référence CVE CVE-2026-74512 https://www.cve.org/CVERecord?id=CVE-2026-74512 Référence CVE CVE-2026-74516 https://www.cve.org/CVERecord?id=CVE-2026-74516 Référence CVE CVE-2026-74518 https://www.cve.org/CVERecord?id=CVE-2026-74518 Référence CVE CVE-2026-74527 https://www.cve.org/CVERecord?id=CVE-2026-74527 Référence CVE CVE-2026-74537 https://www.cve.org/CVERecord?id=CVE-2026-74537 Référence CVE CVE-2026-74548 https://www.cve.org/CVERecord?id=CVE-2026-74548 Référence CVE CVE-2026-74550 https://www.cve.org/CVERecord?id=CVE-2026-74550 Référence CVE CVE-2026-74556 https://www.cve.org/CVERecord?id=CVE-2026-74556 Référence CVE CVE-2026-74563 https://www.cve.org/CVERecord?id=CVE-2026-74563 Référence CVE CVE-2026-74566 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-74504 Référence CVE CVE-2026-74505 https://www.cve.org/CVERecord?id=CVE-2026-74505 Référence CVE CVE-2026-74507 https://www.cve.org/CVERecord?id=CVE-2026-74507 Référence CVE CVE-2026-74508 https://www.cve.org/CVERecord?id=CVE-2026-74508 Référence CVE CVE-2026-74509 https://www.cve.org/CVERecord?id=CVE-2026-74509 Référence CVE CVE-2026-74510 https://www.cve.org/CVERecord?id=CVE-2026-74510 Référence CVE CVE-2026-74512 https://www.cve.org/CVERecord?id=CVE-2026-74512 Référence CVE CVE-2026-74514 https://www.cve.org/CVERecord?id=CVE-2026-74514 Référence CVE CVE-2026-74515 https://www.cve.org/CVERecord?id=CVE-2026-74515 Référence CVE CVE-2026-74516 https://www.cve.org/CVERecord?id=CVE-2026-74516 Référence CVE CVE-2026-74517 https://www.cve.org/CVERecord?id=CVE-2026-74517 Référence CVE CVE-2026-74518 https://www.cve.org/CVERecord?id=CVE-2026-74518 Référence CVE CVE-2026-74519 https://www.cve.org/CVERecord?id=CVE-2026-74519 Référence CVE CVE-2026-74522 https://www.cve.org/CVERecord?id=CVE-2026-74522 Référence CVE CVE-2026-74523 https://www.cve.org/CVERecord?id=CVE-2026-74523 Référence CVE CVE-2026-74524 https://www.cve.org/CVERecord?id=CVE-2026-74524 Référence CVE CVE-2026-74525 https://www.cve.org/CVERecord?id=CVE-2026-74525 Référence CVE CVE-2026-74531 https://www.cve.org/CVERecord?id=

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 15 Aug 2026 · Last source change 19 Aug 2026, 16:38 UTC · CWE not yet assigned

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

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-74516 to remediation: access.redhat.com/CVE-2026-74516.
    Before
    remediation: access.redhat.com/CVE-2026-74516
    After
    remediation: access.redhat.com/CVE-2026-74516
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  3. 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 202 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 155 more · Fixed: bpftool-0:4.18.0-553.171.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.171.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.171.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.171.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.171.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.171.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.171.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.171.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.171.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.171.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.171.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.171.1.el8_10.src as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.171.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-abi-stablelists-0:4.18.0-553.171.1.el8_10.noarch as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.171.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.171.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.171.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.171.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.171.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.171.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.171.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.171.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.171.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.171.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.171.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.171.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.171.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.171.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.171.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.171.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); and 120 more
    Red Hat Product Security ↗
  4. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-74516 to remediation: access.redhat.com/CVE-2026-74516.
    Before
    remediation: access.redhat.com/CVE-2026-74516
    After
    remediation: access.redhat.com/CVE-2026-74516
    Red Hat Product Security ↗
  5. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Red Hat Product Security ↗
  6. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/4ca05385b3ddbd463be17c6d69ec76fca657081d; removed remediation: git.kernel.org/6664a5aea45318f4ec156a729949b474dd6e3159.
    Before
    remediation: git.kernel.org/6664a5aea45318f4ec156a729949b474dd6e3159
    After
    remediation: git.kernel.org/4ca05385b3ddbd463be17c6d69ec76fca657081d
    CNA ↗
  7. Affected versionsThe structured affected or fixed version information changed.
    Before
    091abbf578f926e763adc0f577baeb7f405b4bdc < 6664a5aea45318f4ec156a729949b474dd6e3159; 091abbf578f926e763adc0f577baeb7f405b4bdc < f12373625b4dc9bcc89c41872648878c73bb9272; 091abbf578f926e763adc0f577baeb7f405b4bdc < 7668c58dcf465559dc7a0d2e95e9cb79cf47454b; 091abbf578f926e763adc0f577baeb7f405b4bdc < 89f9e8398e79c49886766fc24a84c37726231104; 091abbf578f926e763adc0f577baeb7f405b4bdc < 7d3aae206663c4e006b25a1c7a20a4029e67da76; 6.0 · Fixed: < 6.0; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    After
    091abbf578f926e763adc0f577baeb7f405b4bdc < 4ca05385b3ddbd463be17c6d69ec76fca657081d; 091abbf578f926e763adc0f577baeb7f405b4bdc < 6664a5aea45318f4ec156a729949b474dd6e3159; 091abbf578f926e763adc0f577baeb7f405b4bdc < f12373625b4dc9bcc89c41872648878c73bb9272; 091abbf578f926e763adc0f577baeb7f405b4bdc < 7668c58dcf465559dc7a0d2e95e9cb79cf47454b; 091abbf578f926e763adc0f577baeb7f405b4bdc < 89f9e8398e79c49886766fc24a84c37726231104; 091abbf578f926e763adc0f577baeb7f405b4bdc < 7d3aae206663c4e006b25a1c7a20a4029e67da76; 6.0 · Fixed: < 6.0; 6.1.183 ≤ 6.1.*; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  8. Affected versionsThe structured affected or fixed version information changed.
    Before
    091abbf578f926e763adc0f577baeb7f405b4bdc < 6664a5aea45318f4ec156a729949b474dd6e3159; 091abbf578f926e763adc0f577baeb7f405b4bdc < f12373625b4dc9bcc89c41872648878c73bb9272; 091abbf578f926e763adc0f577baeb7f405b4bdc < 7668c58dcf465559dc7a0d2e95e9cb79cf47454b; 091abbf578f926e763adc0f577baeb7f405b4bdc < 89f9e8398e79c49886766fc24a84c37726231104; 091abbf578f926e763adc0f577baeb7f405b4bdc < 7d3aae206663c4e006b25a1c7a20a4029e67da76; 6.0 · Fixed: < 6.0; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2-rc6 ≤ *
    After
    091abbf578f926e763adc0f577baeb7f405b4bdc < 6664a5aea45318f4ec156a729949b474dd6e3159; 091abbf578f926e763adc0f577baeb7f405b4bdc < f12373625b4dc9bcc89c41872648878c73bb9272; 091abbf578f926e763adc0f577baeb7f405b4bdc < 7668c58dcf465559dc7a0d2e95e9cb79cf47454b; 091abbf578f926e763adc0f577baeb7f405b4bdc < 89f9e8398e79c49886766fc24a84c37726231104; 091abbf578f926e763adc0f577baeb7f405b4bdc < 7d3aae206663c4e006b25a1c7a20a4029e67da76; 6.0 · Fixed: < 6.0; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  9. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    CNA ↗
  10. CVSS scoreCVSS score changed from not recorded to 8.2 (CVSS 3.1 · CNA · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).
    Before
    not recorded
    After
    8.2 (CVSS 3.1 · CNA · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H)
    CNA ↗
  11. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
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-59709↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor 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-74516 · cve.blacktree.nl