CVE-2026-23090
slimbus: core: fix device reference leak on report present
Description
In the Linux kernel, the following vulnerability has been resolved: slimbus: core: fix device reference leak on report present Slimbus devices can be allocated dynamically upon reception of report-present messages. Make sure to drop the reference taken when looking up already registered devices. Note that this requires taking an extra reference in case the device has not yet been registered and has to be allocated.
INFO
Published Date :
Feb. 4, 2026, 5:16 p.m.
Last Modified :
March 17, 2026, 9:09 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Apply the patch to fix the device reference leak.
- Drop the reference when looking up registered devices.
- Take an extra reference if the device needs allocation.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-23090.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-23090 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-23090
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-23090 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-23090 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Mar. 17, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Added CWE NVD-CWE-Other Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.199 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.162 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.122 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.68 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.8 *cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.16 up to (excluding) 5.10.249 Added Reference Type kernel.org: https://git.kernel.org/stable/c/02b78bbfbafe49832e508079148cb87cdfa55825 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/2ddc09f6a0a221b1d91a7cbc8cc2cefdbd334fe6 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/54de72a7aabc0749938d7a2833a0c1a5d3ed7ac9 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/6602bb4d1338e92b5838e50322b87697bdbd2ee0 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/9391380eb91ea5ac792aae9273535c8da5b9aa01 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/948615429c9f2ac9d25d4e1f1a4472926b217a9a Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/b1217e40705b2f6d311c197b12866752656217ff Types: Patch -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Feb. 06, 2026
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/02b78bbfbafe49832e508079148cb87cdfa55825 Added Reference https://git.kernel.org/stable/c/948615429c9f2ac9d25d4e1f1a4472926b217a9a Added Reference https://git.kernel.org/stable/c/b1217e40705b2f6d311c197b12866752656217ff -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Feb. 04, 2026
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: slimbus: core: fix device reference leak on report present Slimbus devices can be allocated dynamically upon reception of report-present messages. Make sure to drop the reference taken when looking up already registered devices. Note that this requires taking an extra reference in case the device has not yet been registered and has to be allocated. Added Reference https://git.kernel.org/stable/c/2ddc09f6a0a221b1d91a7cbc8cc2cefdbd334fe6 Added Reference https://git.kernel.org/stable/c/54de72a7aabc0749938d7a2833a0c1a5d3ed7ac9 Added Reference https://git.kernel.org/stable/c/6602bb4d1338e92b5838e50322b87697bdbd2ee0 Added Reference https://git.kernel.org/stable/c/9391380eb91ea5ac792aae9273535c8da5b9aa01