Kernel memory corruption via deferred RQ buffer race
Published Sep 19, 2025 · Updated Sep 19, 2025
Use-after-free in the Linux lpfc driver allows remote attackers to corrupt kernel memory through a deferred receive race. The deferred receive path frees the RQ buffer before clearing the shared context pointer under lock, letting concurrent ABTS or repost handling release it again. Exploitation requires an active lpfc Fibre Channel target path and concurrent receive handling; public evidence establishes memory corruption, not code execution.
Summary
What happened
Use-after-free in the Linux lpfc driver allows remote attackers to corrupt kernel memory through a deferred receive race. The deferred receive path frees the RQ buffer before clearing the shared context pointer under lock, letting concurrent ABTS or repost handling release it again. Exploitation requires an active lpfc Fibre Channel target path and concurrent receive handling; public evidence establishes memory corruption, not code execution.
The record
- CVE
- CVE-2025-39841
- Published
- Sep 19, 2025
- Updated
- Sep 19, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 19, 2025CVE publishedPublication date reported by the CVE source.
- Sep 19, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=472e146d1cf3410a898b49834500fa9e33ac41a2 <367cb5ffd8a8a4c85dc89f55e7fa7cc191425b11
- Affected versionversion=472e146d1cf3410a898b49834500fa9e33ac41a2 <55658c7501467ca9ef3bd4453dd920010db8bc13
- Affected versionversion=472e146d1cf3410a898b49834500fa9e33ac41a2 <897f64b01c1249ac730329b83f4f40bab71e86c7
- Affected versionversion=472e146d1cf3410a898b49834500fa9e33ac41a2 <95b63d15fce5c54a73bbf195e1aacb5a75b128e2
- Affected versionversion=472e146d1cf3410a898b49834500fa9e33ac41a2 <9dba9a45c348e8460da97c450cddf70b2056deb3
- Affected versionversion=472e146d1cf3410a898b49834500fa9e33ac41a2 <ab34084f42ee06a9028d67c78feafb911d33d111
- Affected versionversion=472e146d1cf3410a898b49834500fa9e33ac41a2 <baa39f6ad79d372a6ce0aa639fbb2f1578479f57
- Affected versionversion=472e146d1cf3410a898b49834500fa9e33ac41a2 <d96cc9a1b57725930c60b607423759d563b4d900
- Affected versionversion=5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo