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

iavf: Fix error handling in iavf_init_module()

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 1 structured product or package state 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.25% 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: No default targetRemediation target: Normal maintenance

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 1 structured product or package state 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.6.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.12-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 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

1 current
CVE-2022-49027 · CSAF 2.0 · revision 52 · interimSUSE Product Security TeamCVE-2022-49027
232 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: iavf: Fix error handling in iavf_init_module() The iavf_init_module() won't destroy workqueue when pci_register_driver() failed. Call destroy_workqueue() when pci_register_driver() failed to prevent the resource leak. Similar to the handling of u132_hcd_init in commit f276e002793c ("usb: u132-hcd: fix resource leak")
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-2022-53911

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

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 1 structured product or package state 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: iavf: Fix error handling in iavf_init_module() The iavf_init_module() won't destroy workqueue when pci_register_driver() failed. Call destroy_workqueue() when pci_register_driver() failed to prevent the resource leak. Similar to the handling of u132_hcd_init in commit f276e002793c ("usb: u132-hcd: fix resource leak")

What

In the Linux kernel, the following vulnerability has been resolved: iavf: Fix error handling in iavf_init_module() The iavf_init_module() won't destroy workqueue when pci_register_driver() failed. Call destroy_workqueue() when pci_register_driver() failed to prevent the resource leak. Similar to the handling of u132_hcd_init in commit f276e002793c ("usb: u132-hcd: fix resource leak")

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 low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: iavf: Fix error handling in iavf_init_module() The iavf_init_module() won't destroy workqueue when pci_register_driver() failed. Call destroy_workqueue() when pci_register_driver() failed to prevent the resource leak. Similar to the handling of u132_hcd_init in commit f276e002793c ("usb: u132-hcd: fix resource leak")

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 low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

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

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

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

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

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

Likely attack path
local access → vulnerable operation → 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.
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:L/UI:N/S:U/C:H/I:N/A:N

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.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
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.

BSI · German · WID-SEC-2024-3251Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241023Security Bulletin 23 Oct 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 23 Oct 2024, published on 23 October 2024. 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-49012 Référence CVE CVE-2022-49013 https://www.cve.org/CVERecord?id=CVE-2022-49013 Référence CVE CVE-2022-49014 https://www.cve.org/CVERecord?id=CVE-2022-49014 Référence CVE CVE-2022-49015 https://www.cve.org/CVERecord?id=CVE-2022-49015 Référence CVE CVE-2022-49017 https://www.cve.org/CVERecord?id=CVE-2022-49017 Référence CVE CVE-2022-49018 https://www.cve.org/CVERecord?id=CVE-2022-49018 Référence CVE CVE-2022-49021 https://www.cve.org/CVERecord?id=CVE-2022-49021 Référence CVE CVE-2022-49022 https://www.cve.org/CVERecord?id=CVE-2022-49022 Référence CVE CVE-2022-49024 https://www.cve.org/CVERecord?id=CVE-2022-49024 Référence CVE CVE-2022-49027 https://www.cve.org/CVERecord?id=CVE-2022-49027 Référence CVE CVE-2022-49028 https://www.cve.org/CVERecord?id=CVE-2022-49028 Référence CVE CVE-2022-49029 https://www.cve.org/CVERecord?id=CVE-2022-49029 Référence CVE CVE-2022-49043 https://www.cve.org/CVERecord?id=CVE-2022-49043 Référence CVE CVE-2022-49048 https://www.cve.org/CVERecord?id=CVE-2022-49048 Référence CVE CVE-2022-49049 https://www.cve.org/CVERecord?id=CVE-2022-49049 Référence CVE CVE-2022-49052 https://www.cve.org/CVERecord?id=CVE-2022-49052 Référence CVE CVE-2022-49057 https://www.cve.org/CVERecord?id=CVE-2022-49057 Référence CVE CVE-2022-49058 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49000 Référence CVE CVE-2022-49002 https://www.cve.org/CVERecord?id=CVE-2022-49002 Référence CVE CVE-2022-49010 https://www.cve.org/CVERecord?id=CVE-2022-49010 Référence CVE CVE-2022-49011 https://www.cve.org/CVERecord?id=CVE-2022-49011 Référence CVE CVE-2022-49014 https://www.cve.org/CVERecord?id=CVE-2022-49014 Référence CVE CVE-2022-49015 https://www.cve.org/CVERecord?id=CVE-2022-49015 Référence CVE CVE-2022-49020 https://www.cve.org/CVERecord?id=CVE-2022-49020 Référence CVE CVE-2022-49021 https://www.cve.org/CVERecord?id=CVE-2022-49021 Référence CVE CVE-2022-49026 https://www.cve.org/CVERecord?id=CVE-2022-49026 Référence CVE CVE-2022-49027 https://www.cve.org/CVERecord?id=CVE-2022-49027 Référence CVE CVE-2022-49028 https://www.cve.org/CVERecord?id=CVE-2022-49028 Référence CVE CVE-2022-49029 https://www.cve.org/CVERecord?id=CVE-2022-49029 Référence CVE CVE-2023-46343 https://www.cve.org/CVERecord?id=CVE-2023-46343 Référence CVE CVE-2023-52881 https://www.cve.org/CVERecord?id=CVE-2023-52881 Référence CVE CVE-2023-52898 https://www.cve.org/CVERecord?id=CVE-2023-52898 Référence CVE CVE-2023-52918 https://www.cve.org/CVERecord?id=CVE-2023-52918 Référence CVE CVE-2023-52919 https://www.cve.org/CVERecord?id=CVE-2023-52919 Référence CVE CVE-2023-6270 https://www.cve.org/CVERecord?id=C

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

d?id=CVE-2022-49017 Référence CVE CVE-2022-49019 https://www.cve.org/CVERecord?id=CVE-2022-49019 Référence CVE CVE-2022-49020 https://www.cve.org/CVERecord?id=CVE-2022-49020 Référence CVE CVE-2022-49021 https://www.cve.org/CVERecord?id=CVE-2022-49021 Référence CVE CVE-2022-49022 https://www.cve.org/CVERecord?id=CVE-2022-49022 Référence CVE CVE-2022-49023 https://www.cve.org/CVERecord?id=CVE-2022-49023 Référence CVE CVE-2022-49024 https://www.cve.org/CVERecord?id=CVE-2022-49024 Référence CVE CVE-2022-49025 https://www.cve.org/CVERecord?id=CVE-2022-49025 Référence CVE CVE-2022-49026 https://www.cve.org/CVERecord?id=CVE-2022-49026 Référence CVE CVE-2022-49027 https://www.cve.org/CVERecord?id=CVE-2022-49027 Référence CVE CVE-2022-49028 https://www.cve.org/CVERecord?id=CVE-2022-49028 Référence CVE CVE-2022-49029 https://www.cve.org/CVERecord?id=CVE-2022-49029 Référence CVE CVE-2022-49031 https://www.cve.org/CVERecord?id=CVE-2022-49031 Référence CVE CVE-2022-49032 https://www.cve.org/CVERecord?id=CVE-2022-49032 Référence CVE CVE-2023-2166 https://www.cve.org/CVERecord?id=CVE-2023-2166 Référence CVE CVE-2023-28327 https://www.cve.org/CVERecord?id=CVE-2023-28327 Référence CVE CVE-2023-52524 https://www.cve.org/CVERecord?id=CVE-2023-52524 Référence CVE CVE-2023-52766 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2022-49016 Référence CVE CVE-2022-49019 https://www.cve.org/CVERecord?id=CVE-2022-49019 Référence CVE CVE-2022-49020 https://www.cve.org/CVERecord?id=CVE-2022-49020 Référence CVE CVE-2022-49021 https://www.cve.org/CVERecord?id=CVE-2022-49021 Référence CVE CVE-2022-49022 https://www.cve.org/CVERecord?id=CVE-2022-49022 Référence CVE CVE-2022-49023 https://www.cve.org/CVERecord?id=CVE-2022-49023 Référence CVE CVE-2022-49024 https://www.cve.org/CVERecord?id=CVE-2022-49024 Référence CVE CVE-2022-49025 https://www.cve.org/CVERecord?id=CVE-2022-49025 Référence CVE CVE-2022-49026 https://www.cve.org/CVERecord?id=CVE-2022-49026 Référence CVE CVE-2022-49027 https://www.cve.org/CVERecord?id=CVE-2022-49027 Référence CVE CVE-2022-49028 https://www.cve.org/CVERecord?id=CVE-2022-49028 Référence CVE CVE-2022-49029 https://www.cve.org/CVERecord?id=CVE-2022-49029 Référence CVE CVE-2022-49031 https://www.cve.org/CVERecord?id=CVE-2022-49031 Référence CVE CVE-2022-49032 https://www.cve.org/CVERecord?id=CVE-2022-49032 Référence CVE CVE-2023-1829 https://www.cve.org/CVERecord?id=CVE-2023-1829 Référence CVE CVE-2023-2166 https://www.cve.org/CVERecord?id=CVE-2023-2166 Référence CVE CVE-2023-28327 https://www.cve.org/CVERecord?id=CVE-2023-28327 Référence CVE CVE-2023-46343 https://www.cve.org/CVERecord?id=CVE-

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

d?id=CVE-2022-49015 Référence CVE CVE-2022-49016 https://www.cve.org/CVERecord?id=CVE-2022-49016 Référence CVE CVE-2022-49019 https://www.cve.org/CVERecord?id=CVE-2022-49019 Référence CVE CVE-2022-49021 https://www.cve.org/CVERecord?id=CVE-2022-49021 Référence CVE CVE-2022-49022 https://www.cve.org/CVERecord?id=CVE-2022-49022 Référence CVE CVE-2022-49023 https://www.cve.org/CVERecord?id=CVE-2022-49023 Référence CVE CVE-2022-49024 https://www.cve.org/CVERecord?id=CVE-2022-49024 Référence CVE CVE-2022-49025 https://www.cve.org/CVERecord?id=CVE-2022-49025 Référence CVE CVE-2022-49026 https://www.cve.org/CVERecord?id=CVE-2022-49026 Référence CVE CVE-2022-49027 https://www.cve.org/CVERecord?id=CVE-2022-49027 Référence CVE CVE-2022-49028 https://www.cve.org/CVERecord?id=CVE-2022-49028 Référence CVE CVE-2022-49029 https://www.cve.org/CVERecord?id=CVE-2022-49029 Référence CVE CVE-2022-49031 https://www.cve.org/CVERecord?id=CVE-2022-49031 Référence CVE CVE-2022-49032 https://www.cve.org/CVERecord?id=CVE-2022-49032 Référence CVE CVE-2023-2166 https://www.cve.org/CVERecord?id=CVE-2023-2166 Référence CVE CVE-2023-28327 https://www.cve.org/CVERecord?id=CVE-2023-28327 Référence CVE CVE-2023-46343 https://www.cve.org/CVERecord?id=CVE-2023-46343 Référence CVE CVE-2023-52766 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2022-49017 Référence CVE CVE-2022-49019 https://www.cve.org/CVERecord?id=CVE-2022-49019 Référence CVE CVE-2022-49020 https://www.cve.org/CVERecord?id=CVE-2022-49020 Référence CVE CVE-2022-49021 https://www.cve.org/CVERecord?id=CVE-2022-49021 Référence CVE CVE-2022-49022 https://www.cve.org/CVERecord?id=CVE-2022-49022 Référence CVE CVE-2022-49023 https://www.cve.org/CVERecord?id=CVE-2022-49023 Référence CVE CVE-2022-49024 https://www.cve.org/CVERecord?id=CVE-2022-49024 Référence CVE CVE-2022-49025 https://www.cve.org/CVERecord?id=CVE-2022-49025 Référence CVE CVE-2022-49026 https://www.cve.org/CVERecord?id=CVE-2022-49026 Référence CVE CVE-2022-49027 https://www.cve.org/CVERecord?id=CVE-2022-49027 Référence CVE CVE-2022-49028 https://www.cve.org/CVERecord?id=CVE-2022-49028 Référence CVE CVE-2022-49029 https://www.cve.org/CVERecord?id=CVE-2022-49029 Référence CVE CVE-2022-49031 https://www.cve.org/CVERecord?id=CVE-2022-49031 Référence CVE CVE-2022-49032 https://www.cve.org/CVERecord?id=CVE-2022-49032 Référence CVE CVE-2023-2166 https://www.cve.org/CVERecord?id=CVE-2023-2166 Référence CVE CVE-2023-28327 https://www.cve.org/CVERecord?id=CVE-2023-28327 Référence CVE CVE-2023-52766 https://www.cve.org/CVERecord?id=CVE-2023-52766 Référence CVE CVE-2023-52800 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-025527Linux の 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.6, 5.10.158 ≤ 5.10.*, 5.15.82 ≤ 5.15.*, 6.0.12 ≤ 6.0.*, 6.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.
04

Evidence and provenance

Published 21 Oct 2024 · Last source change 11 May 2026, 18:51 UTC · CWE not yet assigned

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-2022-53911
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

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 ↗

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
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-49027 · cve.blacktree.nl