BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2022-49504High confidence

scsi: lpfc: Inhibit aborts if external loopback plug is inserted

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

1 package state
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.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
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 record ↗Source updated 8 Sept 2026
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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

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 actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Inhibit aborts if external loopback plug is inserted After running a short external loopback test, when the external loopback is removed and a normal cable inserted that is directly connected to a target device, the system oops in the llpfc_set_rrq_active() routine. When the loopback was inserted an FLOGI was transmit. As we're looped back, we receive the FLOGI request. The FLOGI is ABTS'd as we recognize the same wppn thus understand it's a loopback. However, as the ABTS sends address information the port is not set to (fffffe), the ABTS is dropped on the wire. A short 1 frame loopback test is run and completes before the ABTS times out. The looback is unplugged and the new cable plugged in, and the an FLOGI to the new device occurs and completes. Due to a mixup in ref counting the completion of the new FLOGI releases the fabric ndlp. Then the original ABTS completes and references the released ndlp generating the oops. Correct by no-op'ing the ABTS when in loopback mode (it will be dropped anyway). Added a flag to track the mode to recognize when it should be no-op'd.

What

In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Inhibit aborts if external loopback plug is inserted After running a short external loopback test, when the external loopback is removed and a normal cable inserted that is directly connected to a target device, the system oops in the llpfc_set_rrq_active() routine. When the loopback was inserted an FLOGI was transmit. As we're looped back, we receive the FLOGI request. The FLOGI is ABTS'd as we recognize the same wppn thus understand it's a loopback. However, as the ABTS sends address information the port is not set to (fffffe), the ABTS is dropped on the wire. A short 1 frame loopback test is run and completes before the ABTS times out. The looback is unplugged and the new cable plugged in, and the an FLOGI to the new device occurs and completes. Due to a mixup in ref counting the completion of the new FLOGI releases the fabric ndlp. Then the original ABTS completes and references the released ndlp generating the oops. Correct by no-op'ing the ABTS when in loopback mode (it will be dropped anyway). Added a flag to track the mode to recognize when it should be no-op'd.

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: scsi: lpfc: Inhibit aborts if external loopback plug is inserted After running a short external loopback test, when the external loopback is removed and a normal cable inserted that is directly connected to a target device, the system oops in the llpfc_set_rrq_active() routine. When the loopback was inserted an FLOGI was transmit. As we're looped back, we receive the FLOGI request. The FLOGI is ABTS'd as we recognize the same wppn thus understand it's a loopback. However, as the ABTS sends address information the port is not set to (fffffe), the ABTS is dropped on the wire. A short 1 frame loopback test is run and completes before the ABTS times out. The looback is unplugged and the new cable plugged in, and the an FLOGI to the new device occurs and completes. Due to a mixup in ref counting the completion of the new FLOGI releases the fabric ndlp. Then the original ABTS completes and references the released ndlp generating the oops. Correct by no-op'ing the ABTS when in loopback mode (it will be dropped anyway). Added a flag to track the mode to recognize when it should be no-op'd.

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:N/I:N/A:H

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

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

Official authority intelligence

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

CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2022-49393 Référence CVE CVE-2022-49401 https://www.cve.org/CVERecord?id=CVE-2022-49401 Référence CVE CVE-2022-49420 https://www.cve.org/CVERecord?id=CVE-2022-49420 Référence CVE CVE-2022-49465 https://www.cve.org/CVERecord?id=CVE-2022-49465 Référence CVE CVE-2022-49469 https://www.cve.org/CVERecord?id=CVE-2022-49469 Référence CVE CVE-2022-49471 https://www.cve.org/CVERecord?id=CVE-2022-49471 Référence CVE CVE-2022-49476 https://www.cve.org/CVERecord?id=CVE-2022-49476 Référence CVE CVE-2022-49484 https://www.cve.org/CVERecord?id=CVE-2022-49484 Référence CVE CVE-2022-49496 https://www.cve.org/CVERecord?id=CVE-2022-49496 Référence CVE CVE-2022-49504 https://www.cve.org/CVERecord?id=CVE-2022-49504 Référence CVE CVE-2022-49516 https://www.cve.org/CVERecord?id=CVE-2022-49516 Référence CVE CVE-2022-49518 https://www.cve.org/CVERecord?id=CVE-2022-49518 Référence CVE CVE-2022-49528 https://www.cve.org/CVERecord?id=CVE-2022-49528 Référence CVE CVE-2022-49529 https://www.cve.org/CVERecord?id=CVE-2022-49529 Référence CVE CVE-2022-49531 https://www.cve.org/CVERecord?id=CVE-2022-49531 Référence CVE CVE-2022-49533 https://www.cve.org/CVERecord?id=CVE-2022-49533 Référence CVE CVE-2022-49534 https://www.cve.org/CVERecord?id=CVE-2022-49534 Référence CVE CVE-2022-49539 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2022-49393 Référence CVE CVE-2022-49401 https://www.cve.org/CVERecord?id=CVE-2022-49401 Référence CVE CVE-2022-49420 https://www.cve.org/CVERecord?id=CVE-2022-49420 Référence CVE CVE-2022-49465 https://www.cve.org/CVERecord?id=CVE-2022-49465 Référence CVE CVE-2022-49469 https://www.cve.org/CVERecord?id=CVE-2022-49469 Référence CVE CVE-2022-49471 https://www.cve.org/CVERecord?id=CVE-2022-49471 Référence CVE CVE-2022-49476 https://www.cve.org/CVERecord?id=CVE-2022-49476 Référence CVE CVE-2022-49484 https://www.cve.org/CVERecord?id=CVE-2022-49484 Référence CVE CVE-2022-49496 https://www.cve.org/CVERecord?id=CVE-2022-49496 Référence CVE CVE-2022-49504 https://www.cve.org/CVERecord?id=CVE-2022-49504 Référence CVE CVE-2022-49516 https://www.cve.org/CVERecord?id=CVE-2022-49516 Référence CVE CVE-2022-49518 https://www.cve.org/CVERecord?id=CVE-2022-49518 Référence CVE CVE-2022-49528 https://www.cve.org/CVERecord?id=CVE-2022-49528 Référence CVE CVE-2022-49529 https://www.cve.org/CVERecord?id=CVE-2022-49529 Référence CVE CVE-2022-49531 https://www.cve.org/CVERecord?id=CVE-2022-49531 Référence CVE CVE-2022-49533 https://www.cve.org/CVERecord?id=CVE-2022-49533 Référence CVE CVE-2022-49534 https://www.cve.org/CVERecord?id=CVE-2022-49534 Référence CVE CVE-2022-49539 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0920Multiples vulnérabilités dans les produits Microsoft

s produits Microsoft Gestion du document Référence CERTFR-2025-AVI-0920 Titre Multiples vulnérabilités dans les produits Microsoft Date de la première version 24 octobre 2025 Date de la dernière version 24 octobre 2025 Source(s) Bulletin de sécurité Microsoft CVE-2024-57899 du 19 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-62168 du 19 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49267 du 22 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49306 du 22 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49333 du 22 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49420 du 22 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49504 du 22 octobre 2025 Bulletin de sécurité Microsoft CVE-2024-38564 du 22 octobre 2025 Bulletin de sécurité Microsoft CVE-2024-57888 du 22 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-53040 du 23 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-53042 du 23 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-53044 du 23 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-53045 du 23 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-53053 du 23 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-53054 du 23 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-53062 du 23 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-53069

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

d?id=CVE-2022-49335 Référence CVE CVE-2022-49351 https://www.cve.org/CVERecord?id=CVE-2022-49351 Référence CVE CVE-2022-49385 https://www.cve.org/CVERecord?id=CVE-2022-49385 Référence CVE CVE-2022-49390 https://www.cve.org/CVERecord?id=CVE-2022-49390 Référence CVE CVE-2022-49411 https://www.cve.org/CVERecord?id=CVE-2022-49411 Référence CVE CVE-2022-49442 https://www.cve.org/CVERecord?id=CVE-2022-49442 Référence CVE CVE-2022-49465 https://www.cve.org/CVERecord?id=CVE-2022-49465 Référence CVE CVE-2022-49478 https://www.cve.org/CVERecord?id=CVE-2022-49478 Référence CVE CVE-2022-49489 https://www.cve.org/CVERecord?id=CVE-2022-49489 Référence CVE CVE-2022-49504 https://www.cve.org/CVERecord?id=CVE-2022-49504 Référence CVE CVE-2022-49521 https://www.cve.org/CVERecord?id=CVE-2022-49521 Référence CVE CVE-2022-49525 https://www.cve.org/CVERecord?id=CVE-2022-49525 Référence CVE CVE-2022-49534 https://www.cve.org/CVERecord?id=CVE-2022-49534 Référence CVE CVE-2022-49535 https://www.cve.org/CVERecord?id=CVE-2022-49535 Référence CVE CVE-2022-49536 https://www.cve.org/CVERecord?id=CVE-2022-49536 Référence CVE CVE-2022-49537 https://www.cve.org/CVERecord?id=CVE-2022-49537 Référence CVE CVE-2022-49542 https://www.cve.org/CVERecord?id=CVE-2022-49542 Référence CVE CVE-2022-49561 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-49493 Référence CVE CVE-2022-49494 https://www.cve.org/CVERecord?id=CVE-2022-49494 Référence CVE CVE-2022-49495 https://www.cve.org/CVERecord?id=CVE-2022-49495 Référence CVE CVE-2022-49497 https://www.cve.org/CVERecord?id=CVE-2022-49497 Référence CVE CVE-2022-49498 https://www.cve.org/CVERecord?id=CVE-2022-49498 Référence CVE CVE-2022-49499 https://www.cve.org/CVERecord?id=CVE-2022-49499 Référence CVE CVE-2022-49501 https://www.cve.org/CVERecord?id=CVE-2022-49501 Référence CVE CVE-2022-49502 https://www.cve.org/CVERecord?id=CVE-2022-49502 Référence CVE CVE-2022-49503 https://www.cve.org/CVERecord?id=CVE-2022-49503 Référence CVE CVE-2022-49504 https://www.cve.org/CVERecord?id=CVE-2022-49504 Référence CVE CVE-2022-49505 https://www.cve.org/CVERecord?id=CVE-2022-49505 Référence CVE CVE-2022-49506 https://www.cve.org/CVERecord?id=CVE-2022-49506 Référence CVE CVE-2022-49507 https://www.cve.org/CVERecord?id=CVE-2022-49507 Référence CVE CVE-2022-49508 https://www.cve.org/CVERecord?id=CVE-2022-49508 Référence CVE CVE-2022-49509 https://www.cve.org/CVERecord?id=CVE-2022-49509 Référence CVE CVE-2022-49510 https://www.cve.org/CVERecord?id=CVE-2022-49510 Référence CVE CVE-2022-49511 https://www.cve.org/CVERecord?id=CVE-2022-49511 Référence CVE CVE-2022-49512 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-49493 Référence CVE CVE-2022-49494 https://www.cve.org/CVERecord?id=CVE-2022-49494 Référence CVE CVE-2022-49495 https://www.cve.org/CVERecord?id=CVE-2022-49495 Référence CVE CVE-2022-49497 https://www.cve.org/CVERecord?id=CVE-2022-49497 Référence CVE CVE-2022-49498 https://www.cve.org/CVERecord?id=CVE-2022-49498 Référence CVE CVE-2022-49499 https://www.cve.org/CVERecord?id=CVE-2022-49499 Référence CVE CVE-2022-49501 https://www.cve.org/CVERecord?id=CVE-2022-49501 Référence CVE CVE-2022-49502 https://www.cve.org/CVERecord?id=CVE-2022-49502 Référence CVE CVE-2022-49503 https://www.cve.org/CVERecord?id=CVE-2022-49503 Référence CVE CVE-2022-49504 https://www.cve.org/CVERecord?id=CVE-2022-49504 Référence CVE CVE-2022-49505 https://www.cve.org/CVERecord?id=CVE-2022-49505 Référence CVE CVE-2022-49506 https://www.cve.org/CVERecord?id=CVE-2022-49506 Référence CVE CVE-2022-49507 https://www.cve.org/CVERecord?id=CVE-2022-49507 Référence CVE CVE-2022-49508 https://www.cve.org/CVERecord?id=CVE-2022-49508 Référence CVE CVE-2022-49509 https://www.cve.org/CVERecord?id=CVE-2022-49509 Référence CVE CVE-2022-49510 https://www.cve.org/CVERecord?id=CVE-2022-49510 Référence CVE CVE-2022-49511 https://www.cve.org/CVERecord?id=CVE-2022-49511 Référence CVE CVE-2022-49512 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-49491 Référence CVE CVE-2022-49492 https://www.cve.org/CVERecord?id=CVE-2022-49492 Référence CVE CVE-2022-49493 https://www.cve.org/CVERecord?id=CVE-2022-49493 Référence CVE CVE-2022-49494 https://www.cve.org/CVERecord?id=CVE-2022-49494 Référence CVE CVE-2022-49495 https://www.cve.org/CVERecord?id=CVE-2022-49495 Référence CVE CVE-2022-49498 https://www.cve.org/CVERecord?id=CVE-2022-49498 Référence CVE CVE-2022-49501 https://www.cve.org/CVERecord?id=CVE-2022-49501 Référence CVE CVE-2022-49502 https://www.cve.org/CVERecord?id=CVE-2022-49502 Référence CVE CVE-2022-49503 https://www.cve.org/CVERecord?id=CVE-2022-49503 Référence CVE CVE-2022-49504 https://www.cve.org/CVERecord?id=CVE-2022-49504 Référence CVE CVE-2022-49505 https://www.cve.org/CVERecord?id=CVE-2022-49505 Référence CVE CVE-2022-49506 https://www.cve.org/CVERecord?id=CVE-2022-49506 Référence CVE CVE-2022-49507 https://www.cve.org/CVERecord?id=CVE-2022-49507 Référence CVE CVE-2022-49508 https://www.cve.org/CVERecord?id=CVE-2022-49508 Référence CVE CVE-2022-49509 https://www.cve.org/CVERecord?id=CVE-2022-49509 Référence CVE CVE-2022-49512 https://www.cve.org/CVERecord?id=CVE-2022-49512 Référence CVE CVE-2022-49514 https://www.cve.org/CVERecord?id=CVE-2022-49514 Référence CVE CVE-2022-49515 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.
Patch available
Affected
1b51197d0fd0c06877c6df1bba84ac4008a7fc60 < a1516930cb605caee3bc7b4f3b7994b88c0b8505; 1b51197d0fd0c06877c6df1bba84ac4008a7fc60 < ead76d4c09b89f4c8d632648026a476a5a34fde8; 3.3
Fixed
< 3.3; 5.18.3 ≤ 5.18.*; 5.19 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
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 11 May 2026, 19:01 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-54725
Product sourceCNA
Remediation sourceCVE/CNA references
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-49504 · cve.blacktree.nl