Answer in brief
CVE-2025-71135 records a Unknown severity vulnerability in md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=be19e6e4339d1579d5f2fae8ce4facf9521dbbfc <20597b7229aea8b5bc45cd92097640257c7fc33b || >=fa1944bbe6220eb929e2c02e5e8706b908565711 <e5abb6af905de6b2fead8a0b3f32ab0b81468a01 || >=fa1944bbe6220eb929e2c02e5e8706b908565711 <7ad6ef91d8745d04aff9cce7bdbc6320d8e05fe9 || >=6.12.4 <6.12.64 | 20597b7229aea8b5bc45cd92097640257c7fc33b, e5abb6af905de6b2fead8a0b3f32ab0b81468a01, 7ad6ef91d8745d04aff9cce7bdbc6320d8e05fe9, 6.12.64 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Jan 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.