CVE-2026-90190
CVE CVE-2026-90190EUVD EUVD-2026-81783Published 2026-09-17T16:07:11.000Z
What the advisory describes
In 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] <TASK> [ 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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 7.2.6; patch: 6.12.110; patch: 7.3-rc1; 49c3b9266a718dbd73c42e004288b4bb2ea0ac0b <017dac7670909eaea3eb36e6b3b5a8be9ce0a14d; 49c3b9266a718dbd73c42e004288b4bb2ea0ac0b <349903f7ee72f7ac5b7a98840d701b2082d140a3; patch: 6.18.52; 49c3b9266a718dbd73c42e004288b4bb2ea0ac0b <f9f4ca45c770b7eec83fea6c9b727b26e691b513; patch: 6.1.188; patch: 0; 49c3b9266a718dbd73c42e004288b4bb2ea0ac0b <c7dea90c9b4ef1dfbd2e4df36de180c76fd7c33c; patch: 6.6.157; 49c3b9266a718dbd73c42e004288b4bb2ea0ac0b <234117949da3b3f9705a21b66094f9f30bbe681d; 5.19; 49c3b9266a718dbd73c42e004288b4bb2ea0ac0b <0a8c2f7b95981913ac370683e34db4906970c210
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.