CVE-2024-47745VulnerabilityPublished 15 May 2025Updated 27 Jun 2026

Red Hat Security Advisory: kernel security update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2025-21756

Not known to be exploited : upgrade to 9.2.1 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

Severity

Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 9.2.1

Exploitation evidence

Disclosed: evidence found.
CVE published 15 May 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 2026-10-26.

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

Upgrade redhat/kernel to 9.2.1.

Affected software

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

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

AI-suggested

Red Hat has released an official security update for Red Hat Enterprise Linux 9.2 Extended Update Support that addresses these vulnerabilities. Users should apply the kernel update provided in advisory RHSA-2025:7683 and reboot their systems to ensure the fixes take effect. Refer to https://access.redhat.com/articles/11258 for detailed update instructions. No additional mitigation steps are indicated by the vendor.

Description

The kernel packages contain the Linux kernel, the core of any Linux operating system. Security Fix(es): * kernel: mm: call the security_mmap_file() LSM hook in remap_file_pages() (CVE-2024-47745) * kernel: vsock: Keep the binding until socket destruction (CVE-2025-21756) 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's memory management and vsock subsystems, potentially impacting system security by bypassing security hooks or improper socket binding lifecycle management. The advisory classifies the impact as Moderate. No known exploits in the wild have been reported. The issues could allow unauthorized actions related to memory mapping and socket handling if left unpatched.

CWE-670Always-Incorrect Control Flow Implementation (opens in a new tab)
Class weakness
The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated.
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:10 UTC

WeaknessesCWE-670, CWE-416

Technical details

References

Community reviews

Related threats