CVE-2025-39841VulnerabilityPublished 10 Dec 2025Updated 28 Jun 2026

Red Hat Security Advisory: kernel security update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2025-39883

Not known to be exploited.

Data as of 26 Oct 2026, 08:30 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hatredhat/kernel`pkg:rpm/redhat/kernel`Other threats	Affected =9.2	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A security update for the Linux kernel packages is available from Red Hat for Red Hat Enterprise Linux 9.2. Users should apply the update as described in the Red Hat advisory RHSA-2025:22996 and reboot affected systems to ensure the fixes take effect. No alternative mitigations are indicated by the vendor.

Description

The kernel packages contain the Linux kernel, the core of any Linux operating system. Security Fix(es): * kernel: scsi: lpfc: Fix buffer free/clear order in deferred receive path (CVE-2025-39841) * kernel: mm/memory-failure: fix VM_BUG_ON_PAGE(PagePoisoned(page)) when unpoison memory (CVE-2025-39883) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Impact

The vulnerabilities affect the Linux kernel, which is critical to system stability and security. The buffer free/clear order issue could lead to memory corruption or instability in the SCSI lpfc driver. The memory unpoisoning bug could cause kernel assertions or crashes related to poisoned memory pages. While no exploits are known in the wild, these issues could potentially impact system reliability or security if triggered.

Summary

This Red Hat security advisory (RHSA-2025:22996) addresses two kernel vulnerabilities in Red Hat Enterprise Linux 9.2. CVE-2025-39841 fixes an issue in the SCSI lpfc driver related to the order of buffer free and clear operations in the deferred receive path. CVE-2025-39883 fixes a memory management bug where VM_BUG_ON_PAGE(PagePoisoned(page)) could be triggered during unpoisoning of memory. Both issues are resolved by updated kernel packages. The advisory applies to multiple Red Hat Enterprise Linux 9.2 variants across several CPU architectures. Users must apply the update and reboot systems for the fixes to take effect. No CVSS scores are provided, and no exploits are currently known.

CWE-416Use After Free (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #7
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Architecture and Design · Language Selection
Choose a language that provides automatic memory management.
Implementation · Attack Surface Reduction
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Jun 2026, 22:19 UTC

WeaknessesCWE-416

Technical details

References

Community reviews

Related threats