md: scope memalloc_noio to allocation critical sections (CVE-2026-90389) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-90389

md: scope memalloc_noio to allocation critical sections

Answer in brief

CVE-2026-90389 records a Unknown severity vulnerability in md: scope memalloc_noio to allocation critical sections. 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.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=78f57ef9d50a75326da73d352d7c27828495229a <72ebfdf507ede7d7f2b7ca0a5634811a0e4bf045 \|\| >=78f57ef9d50a75326da73d352d7c27828495229a <28fdea874f68cac6c36651b1fc7272fd2199c48d \|\| >=78f57ef9d50a75326da73d352d7c27828495229a <a58923756b0f8e71032070c23ae0b167e46731da \|\| >=78f57ef9d50a75326da73d352d7c27828495229a <bace2010dd7ac07bc980575afb135c406730a7fe	72ebfdf507ede7d7f2b7ca0a5634811a0e4bf045, 28fdea874f68cac6c36651b1fc7272fd2199c48d, a58923756b0f8e71032070c23ae0b167e46731da, bace2010dd7ac07bc980575afb135c406730a7fe
Linux/Linuxgeneric	5.8	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 72ebfdf507ede7d7f2b7ca0a5634811a0e4bf045 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: md: scope memalloc_noio to allocation critical sections Storing a memalloc_noio_save() token in mddev->noio_flags lets one task save the token and another task restore it. With concurrent suspend sysfs writes, task A can enter PF_MEMALLOC_NOIO, return to userspace still in that scope, and later task B can restore A's saved token. Avoid tying the token lifetime to mddev. Keep mddev_suspend() and mddev_resume() only responsible for array suspension, and enter PF_MEMALLOC_NOIO only in the MD paths that allocate memory after the array has been suspended. Restore the token before resuming the array. A reproducer repeatedly writes suspend_lo and suspend_hi from concurrent workers and checks each worker's /proc/self/stat flags before and after the sysfs write.

Quoted source text, attributed separately from HOL analysis.