CVE-2024-26935VulnerabilityPublished 5 Feb 2025Updated 28 Jun 2026

Red Hat Security Advisory: kernel security update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2024-50275

Not known to be exploited : upgrade to 8.10.1 or 8.10 when convenient.

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.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.10.1, 8.10

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Feb 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-25.

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 8.10.1 or 8.10.

Affected software

Product	Affected	Fixed in
Red Hatredhat/kernel`pkg:rpm/redhat/kernel`Other threats	Affected >=8 <8.10 >=8.10 <8.10.1	Fixed in 8.10 8.10.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 updated kernel packages that fix these vulnerabilities. Users should apply the provided kernel update for Red Hat Enterprise Linux 8 as described in the Red Hat advisory RHSA-2025:1068 and reboot their systems to ensure the fixes take effect. For detailed update instructions, refer to https://access.redhat.com/articles/11258.

Description

The kernel packages contain the Linux kernel, the core of any Linux operating system. Security Fix(es): * kernel: scsi: core: Fix unremoved procfs host directory regression (CVE-2024-26935) * kernel: arm64/sve: Discard stale CPU state when handling SVE traps (CVE-2024-50275) 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 core components in Red Hat Enterprise Linux 8, potentially leading to system instability or security issues related to procfs host directory handling and CPU state management on arm64. The advisory rates the impact as moderate. There are no known exploits in the wild at this time.

Summary

This advisory covers two kernel vulnerabilities in Red Hat Enterprise Linux 8. CVE-2024-26935 addresses a regression in the SCSI core where a procfs host directory was not properly removed, potentially causing system inconsistencies. CVE-2024-50275 fixes an issue on arm64 architectures related to handling Scalable Vector Extension (SVE) traps by discarding stale CPU state, which could affect system stability or security. Red Hat has released updated kernel packages to resolve these issues and recommends applying the update and rebooting the system.

CWE-99Improper Control of Resource Identifiers ('Resource Injection') (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product receives input from an upstream component, but it does not restrict or incorrectly restricts the input before it is used as an identifier for a resource that may be outside the intended sphere of control.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Manipulating Writeable Configuration Files (opens in a new tab)
Resource Injection (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:36 UTC

WeaknessesCWE-99

Technical details

References

Community reviews

Related threats