Skip to content
VulniPulse
High7.0Vendor: MediumRed Hat Linux

CVE-2026-98385: Red Hat Decouple sched_cache_group from mm to fix UAF

This Red Hat advisory covers CVE-2026-98385.

Open the Red Hat advisory

Key facts

Vendor rating
High, CVSS 7
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H · base score 7.8, scored by LinuxAttack vector: local. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: high. Availability impact: high.
EPSS
0.18% chance of exploitation in the next 30 days (7th percentile). FIRST EPSS, .
CISA KEV
Not listed (catalogue checked )
Source published
Listed by VulniPulse
Record changed

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

Red Hat LinuxUnclassified

Description

In the Linux kernel, the following vulnerability has been resolved: sched/cache: Decouple sched_cache_group from mm to fix UAF Currently the sched cache grouping is by mm and the scheduling statistics sched_cache_stat lives in the mm structure. This ties the life cycle of scheduling stats with mm.

In account_mm_sched(), the scheduling stats are accessed by task->mm->sc_stat. However, a task may be switching mm on one CPU when another CPU is running account_mm_sched(), and possibly accessing the old mm that was freed.

This problem was found when running tests with KASAN by Hyunwoo: Instead of serializing the mm access by introducing extra acquisition of rq lock in the mm free path, extract sched_cache_stat from mm_struct, rename it as sched_cache_group and manage its life cycle apart from mm_struct with its own ref counting.

This allows us in the next patch access sched_cache_group directly from task, and add a refcount on sched_cache_group when a task links to it. This prevents the use after free issue when accessing stale and released old mm and its sched cache stat a task switches to a new mm while account_mm_sched() is done elsewhere.

Text from the source record.

How to fix CVE-2026-98385

Vendor guidance

  • Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

CVE-2026-98385 in other vendors' advisories

Compare every advisory for CVE-2026-98385

All Red Hat Linux advisories

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Red Hat