GHSA-4PJ7-MFRC-7J5J
Vulnerability from github – Published: 2026-09-17 18:31 – Updated: 2026-09-17 18:31In the Linux kernel, the following vulnerability has been resolved:
null_blk: use DEFINE_MUTEX for the file-scope mutex
In null_init(), mutex_init(&lock) currently happens after configfs_register_subsystem(), which exposes the nullb subsystem to userspace. A racing mkdir() into /sys/kernel/config/nullb/ can reach null_find_dev_by_name() -> mutex_lock(&lock) before the mutex is initialized, trigger warning:
[ 123.137788] DEBUG_LOCKS_WARN_ON(lock->magic != lock) [ 123.137796] WARNING: kernel/locking/mutex.c:159 at mutex_lock+0x171/0x1c0, CPU#13: mkdir/1301 [ 123.140090] Modules linked in: null_blk(+) nft_fib_inet nft_fib_ipv4 ...... [ 123.154926] Call Trace: [ 123.155172] [ 123.155419] ? __pfx_mutex_lock+0x10/0x10 [ 123.156181] ? __pfx__raw_spin_lock+0x10/0x10 [ 123.156571] nullb_group_make_group+0x20/0x100 [null_blk] [ 123.157011] configfs_mkdir+0x47b/0xc70 [ 123.157337] ? __pfx_configfs_mkdir+0x10/0x10 [ 123.157719] ? may_create_dentry+0x242/0x2e0 [ 123.158061] vfs_mkdir+0x2a9/0x6c0 [ 123.158352] filename_mkdirat+0x3dc/0x500 [ 123.158710] ? __pfx_filename_mkdirat+0x10/0x10 [ 123.159070] ? strncpy_from_user+0x3a/0x1d0 [ 123.159413] __x64_sys_mkdir+0x6b/0x90 [ 123.159760] do_syscall_64+0xea/0x600
Replace the runtime mutex_init(&lock) with a static DEFINE_MUTEX(lock) declaration to fix this issue.
{
"affected": [],
"aliases": [
"CVE-2026-90190"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:13Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnull_blk: use DEFINE_MUTEX for the file-scope mutex\n\nIn null_init(), mutex_init(\u0026lock) currently happens after\nconfigfs_register_subsystem(), which exposes the nullb subsystem to\nuserspace. A racing mkdir() into /sys/kernel/config/nullb/ can reach\nnull_find_dev_by_name() -\u003e mutex_lock(\u0026lock) before the mutex is\ninitialized, trigger warning:\n\n[ 123.137788] DEBUG_LOCKS_WARN_ON(lock-\u003emagic != lock)\n[ 123.137796] WARNING: kernel/locking/mutex.c:159 at mutex_lock+0x171/0x1c0, CPU#13: mkdir/1301\n[ 123.140090] Modules linked in: null_blk(+) nft_fib_inet nft_fib_ipv4\n......\n[ 123.154926] Call Trace:\n[ 123.155172] \u003cTASK\u003e\n[ 123.155419] ? __pfx_mutex_lock+0x10/0x10\n[ 123.156181] ? __pfx__raw_spin_lock+0x10/0x10\n[ 123.156571] nullb_group_make_group+0x20/0x100 [null_blk]\n[ 123.157011] configfs_mkdir+0x47b/0xc70\n[ 123.157337] ? __pfx_configfs_mkdir+0x10/0x10\n[ 123.157719] ? may_create_dentry+0x242/0x2e0\n[ 123.158061] vfs_mkdir+0x2a9/0x6c0\n[ 123.158352] filename_mkdirat+0x3dc/0x500\n[ 123.158710] ? __pfx_filename_mkdirat+0x10/0x10\n[ 123.159070] ? strncpy_from_user+0x3a/0x1d0\n[ 123.159413] __x64_sys_mkdir+0x6b/0x90\n[ 123.159760] do_syscall_64+0xea/0x600\n\nReplace the runtime mutex_init(\u0026lock) with a static DEFINE_MUTEX(lock)\ndeclaration to fix this issue.",
"id": "GHSA-4pj7-mfrc-7j5j",
"modified": "2026-09-17T18:31:54Z",
"published": "2026-09-17T18:31:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90190"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/017dac7670909eaea3eb36e6b3b5a8be9ce0a14d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0a8c2f7b95981913ac370683e34db4906970c210"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/234117949da3b3f9705a21b66094f9f30bbe681d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/349903f7ee72f7ac5b7a98840d701b2082d140a3"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c7dea90c9b4ef1dfbd2e4df36de180c76fd7c33c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f9f4ca45c770b7eec83fea6c9b727b26e691b513"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
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.
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.