BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2022-49154High confidence

KVM: SVM: fix panic on out-of-bounds guest IRQ

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 157 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 5 Aug 2026

Evidence used

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

5 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 1 affected package state 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.5.17.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗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 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-2022-49154 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: KVM: SVM: fix panic on out-of-bounds guest IRQ
156 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 8
  • kernel as a component of Red Hat Enterprise Linux 8
  • kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8
  • kernel-core as a component of Red Hat Enterprise Linux 8
  • kernel-cross-headers as a component of Red Hat Enterprise Linux 8
  • kernel-debug as a component of Red Hat Enterprise Linux 8
  • kernel-debug-core as a component of Red Hat Enterprise Linux 8
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8
Summary
This is a vulnerability in the Linux kernel's KVM (Kernel-based Virtual Machine) subsystem, specifically affecting AMD's Secure Virtual Machine (SVM) implementation. The issue arises from improper handling of guest interrupt requests (IRQs). When guest IRQ values provided exceed expected bounds, it can trigger a kernel panic, leading to a denial of service.
Remediation
Affected
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-2022-55071

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 157 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 panic on out-of-bounds guest IRQ As guest_irq is coming from KVM_IRQFD API call, it may trigger crash in svm_update_pi_irte() due to out-of-bounds: crash> bt PID: 22218 TASK: ffff951a6ad74980 CPU: 73 COMMAND: "vcpu8" #0 [ffffb1ba6707fa40] machine_kexec at ffffffff8565b397 #1 [ffffb1ba6707fa90] __crash_kexec at ffffffff85788a6d #2 [ffffb1ba6707fb58] crash_kexec at ffffffff8578995d #3 [ffffb1ba6707fb70] oops_end at ffffffff85623c0d #4 [ffffb1ba6707fb90] no_context at ffffffff856692c9 #5 [ffffb1ba6707fbf8] exc_page_fault at ffffffff85f95b51 #6 [ffffb1ba6707fc50] asm_exc_page_fault at ffffffff86000ace [exception RIP: svm_update_pi_irte+227] RIP: ffffffffc0761b53 RSP: ffffb1ba6707fd08 RFLAGS: 00010086 RAX: ffffb1ba6707fd78 RBX: ffffb1ba66d91000 RCX: 0000000000000001 RDX: 00003c803f63f1c0 RSI: 000000000000019a RDI: ffffb1ba66db2ab8 RBP: 000000000000019a R8: 0000000000000040 R9: ffff94ca41b82200 R10: ffffffffffffffcf R11: 0000000000000001 R12: 0000000000000001 R13: 0000000000000001 R14: ffffffffffffffcf R15: 000000000000005f ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #7 [ffffb1ba6707fdb8] kvm_irq_routing_update at ffffffffc09f19a1 [kvm] #8 [ffffb1ba6707fde0] kvm_set_irq_routing at ffffffffc09f2133 [kvm] #9 [ffffb1ba6707fe18] kvm_vm_ioctl at ffffffffc09ef544 [kvm] RIP: 00007f143c36488b RSP: 00007f143a4e04b8 RFLAGS: 00000246 RAX: ffffffffffffffda RBX: 00007f05780041d0 RCX: 00007f143c36488b RDX: 00007f05780041d0 RSI: 000000004008ae6a RDI: 0000000000000020 RBP: 00000000000004e8 R8: 0000000000000008 R9: 00007f05780041e0 R10: 00007f0578004560 R11: 0000000000000246 R12: 00000000000004e0 R13: 000000000000001a R14: 00007f1424001c60 R15: 00007f0578003bc0 ORIG_RAX: 0000000000000010 CS: 0033 SS: 002b Vmx have been fix this in commit 3a8b0677fc61 (KVM: VMX: Do not BUG() on out-of-bounds guest IRQ), so we can just copy source from that to fix this.

What

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: fix panic on out-of-bounds guest IRQ As guest_irq is coming from KVM_IRQFD API call, it may trigger crash in svm_update_pi_irte() due to out-of-bounds: crash> bt PID: 22218 TASK: ffff951a6ad74980 CPU: 73 COMMAND: "vcpu8" #0 [ffffb1ba6707fa40] machine_kexec at ffffffff8565b397 #1 [ffffb1ba6707fa90] __crash_kexec at ffffffff85788a6d #2 [ffffb1ba6707fb58] crash_kexec at ffffffff8578995d #3 [ffffb1ba6707fb70] oops_end at ffffffff85623c0d #4 [ffffb1ba6707fb90] no_context at ffffffff856692c9 #5 [ffffb1ba6707fbf8] exc_page_fault at ffffffff85f95b51 #6 [ffffb1ba6707fc50] asm_exc_page_fault at ffffffff86000ace [exception RIP: svm_update_pi_irte+227] RIP: ffffffffc0761b53 RSP: ffffb1ba6707fd08 RFLAGS: 00010086 RAX: ffffb1ba6707fd78 RBX: ffffb1ba66d91000 RCX: 0000000000000001 RDX: 00003c803f63f1c0 RSI: 000000000000019a RDI: ffffb1ba66db2ab8 RBP: 000000000000019a R8: 0000000000000040 R9: ffff94ca41b82200 R10: ffffffffffffffcf R11: 0000000000000001 R12: 0000000000000001 R13: 0000000000000001 R14: ffffffffffffffcf R15: 000000000000005f ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #7 [ffffb1ba6707fdb8] kvm_irq_routing_update at ffffffffc09f19a1 [kvm] #8 [ffffb1ba6707fde0] kvm_set_irq_routing at ffffffffc09f2133 [kvm] #9 [ffffb1ba6707fe18] kvm_vm_ioctl at ffffffffc09ef544 [kvm] RIP: 00007f143c36488b RSP: 00007f143a4e04b8 RFLAGS: 00000246 RAX: ffffffffffffffda RBX: 00007f05780041d0 RCX: 00007f143c36488b RDX: 00007f05780041d0 RSI: 000000004008ae6a RDI: 0000000000000020 RBP: 00000000000004e8 R8: 0000000000000008 R9: 00007f05780041e0 R10: 00007f0578004560 R11: 0000000000000246 R12: 00000000000004e0 R13: 000000000000001a R14: 00007f1424001c60 R15: 00007f0578003bc0 ORIG_RAX: 0000000000000010 CS: 0033 SS: 002b Vmx have been fix this in commit 3a8b0677fc61 (KVM: VMX: Do not BUG() on out-of-bounds guest IRQ), so we can just copy source from that to fix this.

Why

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: fix panic on out-of-bounds guest IRQ As guest_irq is coming from KVM_IRQFD API call, it may trigger crash in svm_update_pi_irte() due to out-of-bounds: crash> bt PID: 22218 TASK: ffff951a6ad74980 CPU: 73 COMMAND: "vcpu8" #0 [ffffb1ba6707fa40] machine_kexec at ffffffff8565b397 #1 [ffffb1ba6707fa90] __crash_kexec at ffffffff85788a6d #2 [ffffb1ba6707fb58] crash_kexec at ffffffff8578995d #3 [ffffb1ba6707fb70] oops_end at ffffffff85623c0d #4 [ffffb1ba6707fb90] no_context at ffffffff856692c9 #5 [ffffb1ba6707fbf8] exc_page_fault at ffffffff85f95b51 #6 [ffffb1ba6707fc50] asm_exc_page_fault at ffffffff86000ace [exception RIP: svm_update_pi_irte+227] RIP: ffffffffc0761b53 RSP: ffffb1ba6707fd08 RFLAGS: 00010086 RAX: ffffb1ba6707fd78 RBX: ffffb1ba66d91000 RCX: 0000000000000001 RDX: 00003c803f63f1c0 RSI: 000000000000019a RDI: ffffb1ba66db2ab8 RBP: 000000000000019a R8: 0000000000000040 R9: ffff94ca41b82200 R10: ffffffffffffffcf R11: 0000000000000001 R12: 0000000000000001 R13: 0000000000000001 R14: ffffffffffffffcf R15: 000000000000005f ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #7 [ffffb1ba6707fdb8] kvm_irq_routing_update at ffffffffc09f19a1 [kvm] #8 [ffffb1ba6707fde0] kvm_set_irq_routing at ffffffffc09f2133 [kvm] #9 [ffffb1ba6707fe18] kvm_vm_ioctl at ffffffffc09ef544 [kvm] RIP: 00007f143c36488b RSP: 00007f143a4e04b8 RFLAGS: 00000246 RAX: ffffffffffffffda RBX: 00007f05780041d0 RCX: 00007f143c36488b RDX: 00007f05780041d0 RSI: 000000004008ae6a RDI: 0000000000000020 RBP: 00000000000004e8 R8: 0000000000000008 R9: 00007f05780041e0 R10: 00007f0578004560 R11: 0000000000000246 R12: 00000000000004e0 R13: 000000000000001a R14: 00007f1424001c60 R15: 00007f0578003bc0 ORIG_RAX: 0000000000000010 CS: 0033 SS: 002b Vmx have been fix this in commit 3a8b0677fc61 (KVM: VMX: Do not BUG() on out-of-bounds guest IRQ), so we can just copy source from that to fix this.

Why

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

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 → Reachable Assertion → disrupt the affected service
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-617 ↗

CWE-617: Reachable Assertion. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

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.
Denial of serviceCWE-617
A

Official authority intelligence

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

Cyber Security Agency of Singapore · English · CSA-SB-20250305Security Bulletin 5 March 2025

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

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

d?id=CVE-2022-49118 Référence CVE CVE-2022-49122 https://www.cve.org/CVERecord?id=CVE-2022-49122 Référence CVE CVE-2022-49130 https://www.cve.org/CVERecord?id=CVE-2022-49130 Référence CVE CVE-2022-49139 https://www.cve.org/CVERecord?id=CVE-2022-49139 Référence CVE CVE-2022-49145 https://www.cve.org/CVERecord?id=CVE-2022-49145 Référence CVE CVE-2022-49147 https://www.cve.org/CVERecord?id=CVE-2022-49147 Référence CVE CVE-2022-49148 https://www.cve.org/CVERecord?id=CVE-2022-49148 Référence CVE CVE-2022-49152 https://www.cve.org/CVERecord?id=CVE-2022-49152 Référence CVE CVE-2022-49153 https://www.cve.org/CVERecord?id=CVE-2022-49153 Référence CVE CVE-2022-49154 https://www.cve.org/CVERecord?id=CVE-2022-49154 Référence CVE CVE-2022-49155 https://www.cve.org/CVERecord?id=CVE-2022-49155 Référence CVE CVE-2022-49156 https://www.cve.org/CVERecord?id=CVE-2022-49156 Référence CVE CVE-2022-49159 https://www.cve.org/CVERecord?id=CVE-2022-49159 Référence CVE CVE-2022-49171 https://www.cve.org/CVERecord?id=CVE-2022-49171 Référence CVE CVE-2022-49174 https://www.cve.org/CVERecord?id=CVE-2022-49174 Référence CVE CVE-2022-49175 https://www.cve.org/CVERecord?id=CVE-2022-49175 Référence CVE CVE-2022-49180 https://www.cve.org/CVERecord?id=CVE-2022-49180 Référence CVE CVE-2022-49187 https://www.cve.org/CVERecord?id=

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

e.org/CVERecord?id=CVE-2021-47595 Référence CVE CVE-2022-1679 https://www.cve.org/CVERecord?id=CVE-2022-1679 Référence CVE CVE-2022-21546 https://www.cve.org/CVERecord?id=CVE-2022-21546 Référence CVE CVE-2022-2585 https://www.cve.org/CVERecord?id=CVE-2022-2585 Référence CVE CVE-2022-2586 https://www.cve.org/CVERecord?id=CVE-2022-2586 Référence CVE CVE-2022-2905 https://www.cve.org/CVERecord?id=CVE-2022-2905 Référence CVE CVE-2022-3903 https://www.cve.org/CVERecord?id=CVE-2022-3903 Référence CVE CVE-2022-4095 https://www.cve.org/CVERecord?id=CVE-2022-4095 Référence CVE CVE-2022-4662 https://www.cve.org/CVERecord?id=CVE-2022-4662 Référence CVE CVE-2022-49154 https://www.cve.org/CVERecord?id=CVE-2022-49154 Référence CVE CVE-2022-49622 https://www.cve.org/CVERecord?id=CVE-2022-49622 Référence CVE CVE-2022-49731 https://www.cve.org/CVERecord?id=CVE-2022-49731 Référence CVE CVE-2022-49764 https://www.cve.org/CVERecord?id=CVE-2022-49764 Référence CVE CVE-2022-49780 https://www.cve.org/CVERecord?id=CVE-2022-49780 Référence CVE CVE-2022-49814 https://www.cve.org/CVERecord?id=CVE-2022-49814 Référence CVE CVE-2022-49879 https://www.cve.org/CVERecord?id=CVE-2022-49879 Référence CVE CVE-2022-49881 https://www.cve.org/CVERecord?id=CVE-2022-49881 Référence CVE CVE-2022-49917 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49137 Référence CVE CVE-2022-49138 https://www.cve.org/CVERecord?id=CVE-2022-49138 Référence CVE CVE-2022-49139 https://www.cve.org/CVERecord?id=CVE-2022-49139 Référence CVE CVE-2022-49144 https://www.cve.org/CVERecord?id=CVE-2022-49144 Référence CVE CVE-2022-49145 https://www.cve.org/CVERecord?id=CVE-2022-49145 Référence CVE CVE-2022-49147 https://www.cve.org/CVERecord?id=CVE-2022-49147 Référence CVE CVE-2022-49148 https://www.cve.org/CVERecord?id=CVE-2022-49148 Référence CVE CVE-2022-49151 https://www.cve.org/CVERecord?id=CVE-2022-49151 Référence CVE CVE-2022-49153 https://www.cve.org/CVERecord?id=CVE-2022-49153 Référence CVE CVE-2022-49154 https://www.cve.org/CVERecord?id=CVE-2022-49154 Référence CVE CVE-2022-49155 https://www.cve.org/CVERecord?id=CVE-2022-49155 Référence CVE CVE-2022-49156 https://www.cve.org/CVERecord?id=CVE-2022-49156 Référence CVE CVE-2022-49157 https://www.cve.org/CVERecord?id=CVE-2022-49157 Référence CVE CVE-2022-49158 https://www.cve.org/CVERecord?id=CVE-2022-49158 Référence CVE CVE-2022-49159 https://www.cve.org/CVERecord?id=CVE-2022-49159 Référence CVE CVE-2022-49160 https://www.cve.org/CVERecord?id=CVE-2022-49160 Référence CVE CVE-2022-49162 https://www.cve.org/CVERecord?id=CVE-2022-49162 Référence CVE CVE-2022-49163 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49137 Référence CVE CVE-2022-49138 https://www.cve.org/CVERecord?id=CVE-2022-49138 Référence CVE CVE-2022-49139 https://www.cve.org/CVERecord?id=CVE-2022-49139 Référence CVE CVE-2022-49144 https://www.cve.org/CVERecord?id=CVE-2022-49144 Référence CVE CVE-2022-49145 https://www.cve.org/CVERecord?id=CVE-2022-49145 Référence CVE CVE-2022-49147 https://www.cve.org/CVERecord?id=CVE-2022-49147 Référence CVE CVE-2022-49148 https://www.cve.org/CVERecord?id=CVE-2022-49148 Référence CVE CVE-2022-49151 https://www.cve.org/CVERecord?id=CVE-2022-49151 Référence CVE CVE-2022-49153 https://www.cve.org/CVERecord?id=CVE-2022-49153 Référence CVE CVE-2022-49154 https://www.cve.org/CVERecord?id=CVE-2022-49154 Référence CVE CVE-2022-49155 https://www.cve.org/CVERecord?id=CVE-2022-49155 Référence CVE CVE-2022-49156 https://www.cve.org/CVERecord?id=CVE-2022-49156 Référence CVE CVE-2022-49157 https://www.cve.org/CVERecord?id=CVE-2022-49157 Référence CVE CVE-2022-49158 https://www.cve.org/CVERecord?id=CVE-2022-49158 Référence CVE CVE-2022-49159 https://www.cve.org/CVERecord?id=CVE-2022-49159 Référence CVE CVE-2022-49160 https://www.cve.org/CVERecord?id=CVE-2022-49160 Référence CVE CVE-2022-49162 https://www.cve.org/CVERecord?id=CVE-2022-49162 Référence CVE CVE-2022-49163 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49131 Référence CVE CVE-2022-49132 https://www.cve.org/CVERecord?id=CVE-2022-49132 Référence CVE CVE-2022-49135 https://www.cve.org/CVERecord?id=CVE-2022-49135 Référence CVE CVE-2022-49137 https://www.cve.org/CVERecord?id=CVE-2022-49137 Référence CVE CVE-2022-49145 https://www.cve.org/CVERecord?id=CVE-2022-49145 Référence CVE CVE-2022-49147 https://www.cve.org/CVERecord?id=CVE-2022-49147 Référence CVE CVE-2022-49148 https://www.cve.org/CVERecord?id=CVE-2022-49148 Référence CVE CVE-2022-49151 https://www.cve.org/CVERecord?id=CVE-2022-49151 Référence CVE CVE-2022-49153 https://www.cve.org/CVERecord?id=CVE-2022-49153 Référence CVE CVE-2022-49154 https://www.cve.org/CVERecord?id=CVE-2022-49154 Référence CVE CVE-2022-49155 https://www.cve.org/CVERecord?id=CVE-2022-49155 Référence CVE CVE-2022-49156 https://www.cve.org/CVERecord?id=CVE-2022-49156 Référence CVE CVE-2022-49157 https://www.cve.org/CVERecord?id=CVE-2022-49157 Référence CVE CVE-2022-49158 https://www.cve.org/CVERecord?id=CVE-2022-49158 Référence CVE CVE-2022-49159 https://www.cve.org/CVERecord?id=CVE-2022-49159 Référence CVE CVE-2022-49160 https://www.cve.org/CVERecord?id=CVE-2022-49160 Référence CVE CVE-2022-49162 https://www.cve.org/CVERecord?id=CVE-2022-49162 Référence CVE CVE-2022-49163 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-026274Linux の Linux Kernel における到達可能なアサーションに関する脆弱性

Linux の Linux Kernel には、到達可能なアサーションに関する脆弱性が存在します。

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
Linux: < 4.9, 5.10.110 ≤ 5.10.*, 5.15.33 ≤ 5.15.*, 5.16.19 ≤ 5.16.*, 5.17.2 ≤ 5.17.*, 5.18 ≤ *
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 26 Feb 2025 · Last source change 5 Aug 2026, 08:54 UTC · CWE-617 · Reachable Assertion

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-14
European sourceENISA EUVD · EUVD-2022-55071
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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.

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-2022-55071↗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-2022-49154 · cve.blacktree.nl