VulnerabilityPublished 14 Jan 2026Updated 5 Nov 2026

CVE-2025-71135: Linux kernel · md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt()

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in e5abb6af905de6b2fead8a0b3f32ab0b81468a01 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:34 UTC

Severity

Unrated

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

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch

Available – fixed in e5abb6af905de6b2fead8a0b3f32ab0b81468a01, 20597b7229aea8b5bc45cd92097640257c7fc33b, 7ad6ef91d8745d04aff9cce7bdbc6320d8e05fe9 +1

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 5 Nov 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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 Linux kernel to e5abb6af905de6b2fead8a0b3f32ab0b81468a01, 20597b7229aea8b5bc45cd92097640257c7fc33b, 7ad6ef91d8745d04aff9cce7bdbc6320d8e05fe9 or 6.12.64.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=6.12.4 <6.12.64	Fixed in e5abb6af905de6b2fead8a0b3f32ab0b81468a01 20597b7229aea8b5bc45cd92097640257c7fc33b 7ad6ef91d8745d04aff9cce7bdbc6320d8e05fe9 6.12.64
LinuxLinux	Affected =6.13	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() The variable mddev->private is first assigned to conf and then checked: conf = mddev->private; if (!conf) ... If conf is NULL, then mddev->private is also NULL. In this case, null-pointer dereferences can occur when calling raid5_quiesce(): raid5_quiesce(mddev, true); raid5_quiesce(mddev, false); since mddev->private is assigned to conf again in raid5_quiesce(), and conf is dereferenced in several places, for example: conf->quiesce = 0; wake_up(&conf->wait_for_quiescent); To fix this issue, the function should unlock mddev and return before invoking raid5_quiesce() when conf is NULL, following the existing pattern in raid5_change_consistency_policy().

References

Community reviews

Loading reviews…