FKIE_CVE-2026-90185
Vulnerability from fkie_nvd - Published: 2026-09-17 17:17 - Updated: 2026-09-17 17:17
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved:
null_blk: serialize configfs attribute stores with the lock
The NULLB_DEVICE_ATTR _store takes no lock: apply_fn attributes
(submit_queues, poll_queues) get dev->NAME written again after apply_fn
returns, outside its lock; APPLY=NULL attributes are entirely lockless.
configfs only serializes stores per-open-file, so concurrent stores on
separate fds race.
For apply_fn attributes, once one store's apply_fn has reconfigured the
hardware, a second (losing) store can still overwrite dev->NAME
afterwards. This leaves dev->submit_queues out of sync with the live
queue count, which is later caught by the WARN_ON_ONCE() in
null_map_queues().
For !apply_fn attributes, power_store()'s null_add_dev() validates and
builds the device under "lock" but only sets CONFIGURED afterwards. A store
slipping in during this window can change a field mid-setup -- for example,
zone_nr_conv can be pushed above nr_zones after it has already been
clamped, leading to an out-of-bounds dev->zones[] access.
Take "lock" in the macro around the apply_fn call, the CONFIGURED test and
the field write, and move it out of nullb_apply_submit_queues()/
nullb_apply_poll_queues() so both paths are covered once. This serializes
stores with power_store's setup and with each other.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/block/null_blk/main.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "8e839ed5210399a0330a8a6c5885c1d40a537c6d",
"status": "affected",
"version": "45919fbfe1c487c17ea1d198534339a5e8abeae3",
"versionType": "git"
},
{
"lessThan": "88d806d0e1d36246208386a8e55b511c1b3d647c",
"status": "affected",
"version": "45919fbfe1c487c17ea1d198534339a5e8abeae3",
"versionType": "git"
},
{
"lessThan": "3945ce8cbce4e328e6fdf0b522dc71e340de19db",
"status": "affected",
"version": "45919fbfe1c487c17ea1d198534339a5e8abeae3",
"versionType": "git"
},
{
"lessThan": "65cae82fd3c39b53430672cb9e3ecd267471a6ce",
"status": "affected",
"version": "45919fbfe1c487c17ea1d198534339a5e8abeae3",
"versionType": "git"
},
{
"lessThan": "c70994c2862b05e44728912b2ea9487d31e2aea7",
"status": "affected",
"version": "45919fbfe1c487c17ea1d198534339a5e8abeae3",
"versionType": "git"
},
{
"lessThan": "7e7fff51808237703a3a1df6dd5cae1dfd1db86d",
"status": "affected",
"version": "45919fbfe1c487c17ea1d198534339a5e8abeae3",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/block/null_blk/main.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.5"
},
{
"lessThan": "5.5",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.188",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.157",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.110",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.52",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.6",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnull_blk: serialize configfs attribute stores with the lock\n\nThe NULLB_DEVICE_ATTR _store takes no lock: apply_fn attributes\n(submit_queues, poll_queues) get dev-\u003eNAME written again after apply_fn\nreturns, outside its lock; APPLY=NULL attributes are entirely lockless.\nconfigfs only serializes stores per-open-file, so concurrent stores on\nseparate fds race.\n\nFor apply_fn attributes, once one store\u0027s apply_fn has reconfigured the\nhardware, a second (losing) store can still overwrite dev-\u003eNAME\nafterwards. This leaves dev-\u003esubmit_queues out of sync with the live\nqueue count, which is later caught by the WARN_ON_ONCE() in\nnull_map_queues().\n\nFor !apply_fn attributes, power_store()\u0027s null_add_dev() validates and\nbuilds the device under \"lock\" but only sets CONFIGURED afterwards. A store\nslipping in during this window can change a field mid-setup -- for example,\nzone_nr_conv can be pushed above nr_zones after it has already been\nclamped, leading to an out-of-bounds dev-\u003ezones[] access.\n\nTake \"lock\" in the macro around the apply_fn call, the CONFIGURED test and\nthe field write, and move it out of nullb_apply_submit_queues()/\nnullb_apply_poll_queues() so both paths are covered once. This serializes\nstores with power_store\u0027s setup and with each other."
}
],
"id": "CVE-2026-90185",
"lastModified": "2026-09-17T17:17:12.980",
"metrics": {},
"published": "2026-09-17T17:17:12.980",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/3945ce8cbce4e328e6fdf0b522dc71e340de19db"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/65cae82fd3c39b53430672cb9e3ecd267471a6ce"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/7e7fff51808237703a3a1df6dd5cae1dfd1db86d"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/88d806d0e1d36246208386a8e55b511c1b3d647c"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/8e839ed5210399a0330a8a6c5885c1d40a537c6d"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c70994c2862b05e44728912b2ea9487d31e2aea7"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…