Skip to main content
CVE-2024-56690VulnerabilityPublished Updated

SUSE · security update for kernel

Affects SUSESource GCVE Database

0

Not known to be exploited.

Data as of 25 Oct 2026, 19:02 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

  1. Disclosed: evidence found.

    CVE published 17 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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-25.

What to do

Affected software

ProductAffectedFixed in
Red Hatredhat/kernelpkg:rpm/redhat/kernelOther threatsAffected
  • =9.6
Fixed in–

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 that addresses this vulnerability. Users of Red Hat Enterprise Linux 9.6 Extended Update Support should apply the update promptly. A system reboot is required after applying the update for the fix to take effect. No additional mitigation steps are indicated by the vendor advisory.

Description

A moderate severity vulnerability (CVE-2024-56690) affects the Linux kernel in Red Hat Enterprise Linux 9.6 Extended Update Support. The issue involves the crypto subsystem where the crypto layer is not called directly when padata_do_parallel() returns -EBUSY, potentially causing improper handling in cryptographic operations. Red Hat has released a security update to address this issue. Systems must be rebooted after applying the update for the fix to take effect.

References

Community reviews

Loading reviews…