CVE-2023-54316 json
refscale: Fix uninitalized use of wait_queue_head_t
published 10mo ago modified 4mo ago also EUVD-2023-60488
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
refscale: Fix uninitalized use of wait_queue_head_t
Running the refscale test occasionally crashes the kernel with the following error:
[ 8569.952896] BUG: unable to handle page fault for address: ffffffffffffffe8 [ 8569.952900] #PF: supervisor read access in kernel mode [ 8569.952902] #PF: error_code(0x0000) - not-present page [ 8569.952904] PGD c4b048067 P4D c4b049067 PUD c4b04b067 PMD 0 [ 8569.952910] Oops: 0000 [#1] PREEMPT_RT SMP NOPTI [ 8569.952916] Hardware name: Dell Inc. PowerEdge R750/0WMWCR, BIOS 1.2.4 05/28/2021 [ 8569.952917] RIP: 0010:prepare_to_wait_event+0x101/0x190 : [ 8569.952940] Call Trace: [ 8569.952941] <TASK> [ 8569.952944] ref_scale_reader+0x380/0x4a0 [refscale] [ 8569.952959] kthread+0x10e/0x130 [ 8569.952966] ret_from_fork+0x1f/0x30 [ 8569.952973] </TASK>
The likely cause is that init_waitqueue_head() is called after the call to the torture_create_kthread() function that creates the ref_scale_reader kthread. Although this init_waitqueue_head() call will very likely complete before this kthread is created and starts running, it is possible that the calling kthread will be delayed between the calls to torture_create_kthread() and init_waitqueue_head(). In this case, the new kthread will use the waitqueue head before it is properly initialized, which is not good for the kernel's health and well-being.
The above crash happened here:
static inline void __add_wait_queue(...) { : if (!(wq->flags & WQ_FLAG_PRIORITY)) <=== Crash here
The offset of flags from list_head entry in wait_queue_entry is -0x18. If reader_tasks[i].wq.head.next is NULL as allocated reader_task structure is zero initialized, the instruction will try to access address 0xffffffffffffffe8, which is exactly the fault address listed above.
This commit therefore invokes init_waitqueue_head() before creating the kthread.
Patch / fix
- Linux Linux 5.10.195, 5.15.132, 6.1.53, 6.4.16, 6.5.3, 6.6
- linux Debian 12 6.1.55-1
- linux Debian 14, Debian 13 6.5.3-1
debian advisories DEBIAN-CVE-2023-54316
- linux Ubuntu 22.04 LTS 5.15.0-94.104
- linux-aws Ubuntu 22.04 LTS 5.15.0-1053.58
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1051.59
- linux-gke Ubuntu 22.04 LTS 5.15.0-1050.55
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1046.49
- linux-kvm Ubuntu 22.04 LTS 5.15.0-1050.55
- linux-azure Ubuntu 22.04 LTS 5.15.0-1056.64
- linux-gkeop Ubuntu 22.04 LTS 5.15.0-1036.42
ubuntu advisories UBUNTU-CVE-2023-54316
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel RHEL 9 5.14.0-427.13.1.el9_4
- rv RHEL 9 5.14.0-427.13.1.el9_4
- perf RHEL 9 5.14.0-427.13.1.el9_4
- rtla RHEL 9 5.14.0-427.13.1.el9_4
- bpftool RHEL 9 7.3.0-427.13.1.el9_4
- libperf RHEL 9 5.14.0-427.13.1.el9_4
- kernel-rt RHEL 9 5.14.0-427.13.1.el9_4
- kernel-64k RHEL 9 5.14.0-427.13.1.el9_4
red hat advisories RHSA-2024:2394
- kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-40.1
- kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-40.1
- kernel-source Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
- kernel-default Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
- kernel-kvmsmall Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
- kernel-default-base Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1.21.16
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.28.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.28.1
suse advisories SUSE-SU-2026:20845-1SUSE-SU-2026:20876-1SUSE-SU-2026:20477-1SUSE-SU-2026:20498-1SUSE-SU-2026:0315-1SUSE-SU-2026:0293-1
- git.kernel.org/stable/c/066fbd8bc981cf49923bf828b7b4092894df577f commit
- git.kernel.org/stable/c/ec9d118ad99dc6f1bc674c1e649c25533d89b9ba commit
- git.kernel.org/stable/c/e0322a255a2242dbe4686b6176b3c83dea490529 commit
- git.kernel.org/stable/c/e5de968a9032366198720eac4f368ed7e690b3ef commit
- git.kernel.org/stable/c/70a2856fd1d0a040c876ba9e3f89b949ae92e4dd commit
- git.kernel.org/stable/c/f5063e8948dad7f31adb007284a5d5038ae31bb8 commit
Is CVE-2023-54316 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-54316 updated cvss 2.5
kernel: refscale: Fix uninitalized use of wait_queue_head_t
-
Red Hat Enterprise Linux 9 kernel-rt, kernel-rt-kvm, kernel-rt-core, kernel-rt-modules, kernel-rt-debug-kvm, kernel-rt-debug-core, +12 moreaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux AppStream (v. 9) rv 5.14.0-427.13.1.el9_4, perf 5.14.0-427.13.1.el9_4, rtla 5.14.0-427.13.1.el9_4, kernel-devel-matched 5.14.0-427.13.1.el9_4, kernel-64k-devel-matched 5.14.0-427.13.1.el9_4, kernel-debug-devel-matched 5.14.0-427.13.1.el9_4, +6 more Red Hat Enterprise Linux BaseOS (v. 9) bpftool 7.3.0-427.13.1.el9_4, kernel 5.14.0-427.13.1.el9_4, kernel-64k 5.14.0-427.13.1.el9_4, kernel-core 5.14.0-427.13.1.el9_4, kernel-tools 5.14.0-427.13.1.el9_4, python3-perf 5.14.0-427.13.1.el9_4, +28 more Red Hat Enterprise Linux CRB (v. 9) libperf 5.14.0-427.13.1.el9_4, kernel-debuginfo-common-s390x 5.14.0-427.13.1.el9_4, kernel-debuginfo-common-x86_64 5.14.0-427.13.1.el9_4, kernel-debuginfo-common-aarch64 5.14.0-427.13.1.el9_4, kernel-debuginfo-common-ppc64le 5.14.0-427.13.1.el9_4 Red Hat Enterprise Linux NFV (v. 9) kernel-rt 5.14.0-427.13.1.el9_4, kernel-rt-kvm 5.14.0-427.13.1.el9_4, kernel-rt-core 5.14.0-427.13.1.el9_4, kernel-rt-modules 5.14.0-427.13.1.el9_4, kernel-rt-debug-kvm 5.14.0-427.13.1.el9_4, kernel-rt-debug-core 5.14.0-427.13.1.el9_4, +6 more Red Hat Enterprise Linux RT (v. 9) kernel-rt 5.14.0-427.13.1.el9_4, kernel-rt-core 5.14.0-427.13.1.el9_4, kernel-rt-modules 5.14.0-427.13.1.el9_4, kernel-rt-debug-core 5.14.0-427.13.1.el9_4, kernel-rt-modules-core 5.14.0-427.13.1.el9_4, kernel-rt-debug-modules 5.14.0-427.13.1.el9_4, +4 morefixed: vendor fix RHSA-2024:2394
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-16).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/066fbd8bc981cf49923bf828b7b4092894df577f
- git.kernel.org /stable/c/ec9d118ad99dc6f1bc674c1e649c25533d89b9ba
- git.kernel.org /stable/c/e0322a255a2242dbe4686b6176b3c83dea490529
- git.kernel.org /stable/c/e5de968a9032366198720eac4f368ed7e690b3ef
- git.kernel.org /stable/c/70a2856fd1d0a040c876ba9e3f89b949ae92e4dd
- git.kernel.org /stable/c/f5063e8948dad7f31adb007284a5d5038ae31bb8
Sources
- CVE List CVE-2023-54316
- NVD CVE-2023-54316
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.