CVE-2024-56690VulnerabilityPublished 17 Nov 2025Updated 28 Jun 2026

Red Hat Security Advisory: kernel security update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2025-39903

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.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Nov 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 =10.0	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 kernel packages is available from Red Hat for Red Hat Enterprise Linux 10.0 Extended Update Support. Users should apply the update as described in Red Hat's advisory and reboot their systems to ensure the fixes take effect. 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: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY (CVE-2024-56690) * kernel: of_numa: fix uninitialized memory nodes causing kernel panic (CVE-2025-39903) 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 could cause instability or denial of service conditions such as kernel panic due to uninitialized memory nodes, and potential issues in the crypto subsystem when handling parallel operations. The security impact is rated as moderate by Red Hat. There are no known exploits in the wild at this time.

Summary

The Red Hat kernel security update for Red Hat Enterprise Linux 10.0 Extended Update Support addresses two vulnerabilities: CVE-2024-56690, which fixes the crypto subsystem by calling the crypto layer directly when padata_do_parallel() returns -EBUSY, and CVE-2025-39903, which resolves uninitialized memory nodes in the of_numa subsystem that could lead to kernel panic. These vulnerabilities relate to improper handling of concurrency and uninitialized memory, corresponding to CWE-703 (Improper Check or Handling of Exceptional Conditions) and CWE-476 (NULL Pointer Dereference). Red Hat has released updated kernel packages to fix these issues, requiring a system reboot for the changes to take effect.

CWE-703Improper Check or Handling of Exceptional Conditions (opens in a new tab)
Pillar weaknessOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-476NULL Pointer Dereference (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #13OWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product dereferences a pointer that it expects to be valid but is NULL.
Implementation
For any pointers that could have been modified or provided from a function that can return NULL, check the pointer for NULL before use. When working with a multithreaded or otherwise asynchronous environment, ensure that proper locking APIs are used to lock before the check, and unlock when it has finished.
Requirements
Select a programming language that is not susceptible to these issues.
Implementation
Check the results of all functions that return a value and verify that the value is non-null before acting upon it.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.7 (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:22 UTC

WeaknessesCWE-703, CWE-476

Technical details

References

Community reviews

Related threats