Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-39841: scsi: lpfc: Fix buffer free/clear order in deferred receive path

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.48% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 367cb5ffd8a8a4c85dc89f55e7fa7cc191425b11, 55658c7501467ca9ef3bd4453dd920010db8bc13, 897f64b01c1249ac730329b83f4f40bab71e86c7; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1.
  • Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 7.8.

Low priority for now. Upgrade to Linux Linux 367cb5ffd8a8a4c85dc89f55e7fa7cc191425b11, 55658c7501467ca9ef3bd4453dd920010db8bc13, 897f64b01c1249ac730329b83f4f40bab71e86c7; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Sep 19, 2025
Updated
Oct 19, 2026
EPSS
0.4% · 41th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
9.8
2.0 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-39841

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux11.0
  • linux linux kernel5.5 and later · before 5.10.243
  • linux linux kernel5.11 and later · before 5.15.192
  • linux linux kernel5.16 and later · before 6.1.151
  • linux linux kernel5.1 and later · before 5.4.299
  • linux linux kernel6.7 and later · before 6.12.46
  • linux linux kernel6.13 and later · before 6.16.6
  • linux linux kernel6.2 and later · before 6.6.105
  • linux linux kernel6.17

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.1affected
    • 472e146d1cf3410a898b49834500fa9e33ac41a2 and later · before ab34084f42ee06a9028d67c78feafb911d33d111affected · git
    • 472e146d1cf3410a898b49834500fa9e33ac41a2 and later · before baa39f6ad79d372a6ce0aa639fbb2f1578479f57affected · git
    • 472e146d1cf3410a898b49834500fa9e33ac41a2 and later · before 95b63d15fce5c54a73bbf195e1aacb5a75b128e2affected · git
    • 472e146d1cf3410a898b49834500fa9e33ac41a2 and later · before 55658c7501467ca9ef3bd4453dd920010db8bc13affected · git
    • 472e146d1cf3410a898b49834500fa9e33ac41a2 and later · before d96cc9a1b57725930c60b607423759d563b4d900affected · git
    • 472e146d1cf3410a898b49834500fa9e33ac41a2 and later · before 367cb5ffd8a8a4c85dc89f55e7fa7cc191425b11affected · git
    • 472e146d1cf3410a898b49834500fa9e33ac41a2 and later · before 897f64b01c1249ac730329b83f4f40bab71e86c7affected · git
    • 472e146d1cf3410a898b49834500fa9e33ac41a2 and later · before 9dba9a45c348e8460da97c450cddf70b2056deb3affected · git
    • before 5.1not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-55.40.1.el10_06.12.0-55.40.1.el10_0
AlmaLinux:10kernel-docbefore 6.12.0-55.40.1.el10_06.12.0-55.40.1.el10_0
AlmaLinux:8bpftoolbefore 4.18.0-553.81.1.el8_104.18.0-553.81.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.81.1.el8_104.18.0-553.81.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.81.1.el8_104.18.0-553.81.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.81.1.el8_104.18.0-553.81.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.81.1.el8_104.18.0-553.81.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.81.1.el8_104.18.0-553.81.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.81.1.el8_104.18.0-553.81.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.81.1.el8_104.18.0-553.81.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.81.1.el8_104.18.0-553.81.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.81.1.el8_104.18.0-553.81.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.81.1.el8_104.18.0-553.81.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.81.1.el8_104.18.0-553.81.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.81.1.el8_104.18.0-553.81.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.81.1.el8_104.18.0-553.81.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.81.1.el8_104.18.0-553.81.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.81.1.rt7.422.el8_104.18.0-553.81.1.rt7.422.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.81.1.rt7.422.el8_104.18.0-553.81.1.rt7.422.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.81.1.rt7.422.el8_104.18.0-553.81.1.rt7.422.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.81.1.rt7.422.el8_104.18.0-553.81.1.rt7.422.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.81.1.rt7.422.el8_104.18.0-553.81.1.rt7.422.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.81.1.rt7.422.el8_104.18.0-553.81.1.rt7.422.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.81.1.rt7.422.el8_104.18.0-553.81.1.rt7.422.el8_10

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-39839Sep 19, 2025 · batman-adv: fix OOB read/write in network-coding decode
    28Monitor
  • ← EarlierCVE-2025-39840Sep 19, 2025 · audit: fix out-of-bounds read in audit_compare_dname_path()
    28Monitor
  • Later →CVE-2025-39842Sep 19, 2025 · ocfs2: prevent release journal inode after journal shutdown
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux367cb5ffd8a8a4c85dc89f55e7fa7cc191425b11Vendor (CNA)
Linux Linux55658c7501467ca9ef3bd4453dd920010db8bc13Vendor (CNA)
Linux Linux897f64b01c1249ac730329b83f4f40bab71e86c7Vendor (CNA)
Linux Linux95b63d15fce5c54a73bbf195e1aacb5a75b128e2Vendor (CNA)
Linux Linux9dba9a45c348e8460da97c450cddf70b2056deb3Vendor (CNA)
Linux Linuxab34084f42ee06a9028d67c78feafb911d33d111Vendor (CNA)
Linux Linuxbaa39f6ad79d372a6ce0aa639fbb2f1578479f57Vendor (CNA)
Linux Linuxd96cc9a1b57725930c60b607423759d563b4d900Vendor (CNA)
azl3 kernel 6.6.104.2-4 on Azure Linux 3.06.6.112.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.05.15.200.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel5.14.0-570.55.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-570.55.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-570.55.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-570.55.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-570.55.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-570.55.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-570.55.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-570.55.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-570.55.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-570.55.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-570.55.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-570.55.1.el9_6 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.153-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+7

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records