CVE-2025-39841

scsi: lpfc: Fix buffer free/clear order in deferred receive path

HIGH
7.8
CVSS Score
Published: September 19, 2025 at 03:26 PM UTC
Updated: October 19, 2026 at 09:10 PM UTC
15 products affected across 3 vendorsLinux KernelDebian LinuxRUGGEDCOM RST2428P Firmware

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix buffer free/clear order in deferred receive path Fix a use-after-free window by correcting the buffer release sequence in the deferred receive path. The code freed the RQ buffer first and only then cleared the context pointer under the lock. Concurrent paths (e.g., ABTS and the repost path) also inspect and release the same pointer under the lock, so the old order could lead to double-free/UAF. Note that the repost path already uses the correct pattern: detach the pointer under the lock, then free it after dropping the lock. The deferred path should do the same.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.1 ≤ v < 5.4.2995.11 ≤ v < 5.15.1925.16 ≤ v < 6.1.1515.5 ≤ v < 5.10.2436.13 ≤ v < 6.16.66.2 ≤ v < 6.6.1056.7 ≤ v < 6.12.46472e146d1cf3410a898b49834500fa9e33ac41a26.176.17 rc16.17 rc26.17 rc36.17 rc4
Vendor states this is fixed in 367cb5ffd8a8a4c85dc89f55e7fa7cc191425b11 (fixed)
Vendor states this is fixed in 55658c7501467ca9ef3bd4453dd920010db8bc13 (fixed)
Vendor states this is fixed in 897f64b01c1249ac730329b83f4f40bab71e86c7 (fixed)
Vendor states this is fixed in 95b63d15fce5c54a73bbf195e1aacb5a75b128e2 (fixed)
Vendor states this is fixed in 9dba9a45c348e8460da97c450cddf70b2056deb3 (fixed)
Vendor states this is fixed in ab34084f42ee06a9028d67c78feafb911d33d111 (fixed)
Vendor states this is fixed in baa39f6ad79d372a6ce0aa639fbb2f1578479f57 (fixed)
Vendor states this is fixed in d96cc9a1b57725930c60b607423759d563b4d900 (fixed)
Vendor states this is fixed in 5.1 (unaffected)
Vendor states this is fixed in 5.10.243 (unaffected)
Vendor states this is fixed in 5.15.192 (unaffected)
Vendor states this is fixed in 5.4.299 (unaffected)
Vendor states this is fixed in 6.1.151 (unaffected)
Vendor states this is fixed in 6.12.46 (unaffected)
Vendor states this is fixed in 6.16.6 (unaffected)
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.6.105 (unaffected)
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card