CVE-2026-90389

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.

CVSS

No CVSS.

References

Link	Resource
https://git.kernel.org/stable/c/28fdea874f68cac6c36651b1fc7272fd2199c48d
https://git.kernel.org/stable/c/72ebfdf507ede7d7f2b7ca0a5634811a0e4bf045
https://git.kernel.org/stable/c/a58923756b0f8e71032070c23ae0b167e46731da
https://git.kernel.org/stable/c/bace2010dd7ac07bc980575afb135c406730a7fe

Configurations

No configuration.

History

17 Sep 2026, 17:17

Type	Values Removed	Values Added
New CVE

Information

Published : 2026-09-17 17:17

Updated : 2026-09-17 17:17

NVD link : CVE-2026-90389

Mitre link : CVE-2026-90389

CVE.ORG link : CVE-2026-90389

JSON object : View

Products Affected

No product.

CWE

No CWE.

{"id": "CVE-2026-90389", "cveTags": [], "metrics": {}, "affected": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "affectedData": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "78f57ef9d50a75326da73d352d7c27828495229a", "lessThan": "72ebfdf507ede7d7f2b7ca0a5634811a0e4bf045", "versionType": "git"}, {"status": "affected", "version": "78f57ef9d50a75326da73d352d7c27828495229a", "lessThan": "28fdea874f68cac6c36651b1fc7272fd2199c48d", "versionType": "git"}, {"status": "affected", "version": "78f57ef9d50a75326da73d352d7c27828495229a", "lessThan": "a58923756b0f8e71032070c23ae0b167e46731da", "versionType": "git"}, {"status": "affected", "version": "78f57ef9d50a75326da73d352d7c27828495229a", "lessThan": "bace2010dd7ac07bc980575afb135c406730a7fe", "versionType": "git"}], "programFiles": ["drivers/md/md-bitmap.c", "drivers/md/md.c", "drivers/md/md.h", "drivers/md/raid5.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "5.8"}, {"status": "unaffected", "version": "0", "lessThan": "5.8", "versionType": "semver"}, {"status": "unaffected", "version": "6.12.110", "versionType": "semver", "lessThanOrEqual": "6.12.*"}, {"status": "unaffected", "version": "6.18.52", "versionType": "semver", "lessThanOrEqual": "6.18.*"}, {"status": "unaffected", "version": "7.2.6", "versionType": "semver", "lessThanOrEqual": "7.2.*"}, {"status": "unaffected", "version": "7.3-rc1", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["drivers/md/md-bitmap.c", "drivers/md/md.c", "drivers/md/md.h", "drivers/md/raid5.c"], "defaultStatus": "affected"}]}], "published": "2026-09-17T17:17:38.427", "references": [{"url": "https://git.kernel.org/stable/c/28fdea874f68cac6c36651b1fc7272fd2199c48d", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/72ebfdf507ede7d7f2b7ca0a5634811a0e4bf045", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/a58923756b0f8e71032070c23ae0b167e46731da", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/bace2010dd7ac07bc980575afb135c406730a7fe", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Received", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmd: scope memalloc_noio to allocation critical sections\n\nStoring a memalloc_noio_save() token in mddev->noio_flags lets one task\nsave the token and another task restore it. With concurrent suspend sysfs\nwrites, task A can enter PF_MEMALLOC_NOIO, return to userspace still in\nthat scope, and later task B can restore A's saved token.\n\nAvoid tying the token lifetime to mddev. Keep mddev_suspend() and\nmddev_resume() only responsible for array suspension, and enter\nPF_MEMALLOC_NOIO only in the MD paths that allocate memory after the array\nhas been suspended. Restore the token before resuming the array.\n\nA reproducer repeatedly writes suspend_lo and suspend_hi from concurrent\nworkers and checks each worker's /proc/self/stat flags before and after the\nsysfs write."}], "lastModified": "2026-09-17T17:17:38.427", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}