LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23090: slimbus: core: fix device reference leak on report present

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-23090 is a Linux kernel bug in the Slimbus core. When certain device presence reports are handled, the kernel can keep an extra device reference instead of releasing it. The public record does not provide CVSS, real-world impact, or exploitation evidence.

Executive priority

Handle through normal kernel patch management unless affected Slimbus-dependent systems are business-critical. Escalate if your vendor rates the issue higher or reports a stronger impact.

Technical view

The issue is a device reference leak in Slimbus report-present handling. Already registered devices are looked up with a reference that was not dropped. The fix also preserves the needed reference when a device is newly allocated and not yet registered.

Likely exposure

Exposure appears limited to Linux systems with affected kernel code paths and Slimbus device handling. The supplied data lists Linux kernel versions and stable commits, but does not define exact distribution package exposure.

Exploitation context

The source bundle does not show active exploitation, public weaponization, KEV listing, CVSS scoring, or attacker prerequisites. Treat this as an incomplete-impact kernel maintenance vulnerability unless vendor guidance says otherwise.

Researcher notes

Evidence supports a reference leak fixed upstream, not a confirmed privilege escalation or remote attack. The affected-version data is sparse and commit-oriented, so validate against kernel source, vendor backports, and device configuration.

Mitigation direction

  • Check your Linux vendor advisory for CVE-2026-23090 package status.
  • Update to a kernel containing the referenced stable fixes.
  • Prioritize systems using Slimbus-related kernel functionality.
  • Track distribution backports instead of relying only on upstream version numbers.

Validation and detection

  • Inventory running kernel versions across affected Linux systems.
  • Check whether Slimbus-related kernel modules or drivers are present.
  • Compare vendor kernel package changelogs against CVE-2026-23090.
  • Confirm the relevant stable fix commit is included or backported.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23090 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux46a2bb5a7f7ea2728be50f8f5b29a20267f700fe, 46a2bb5a7f7ea2728be50f8f5b29a20267f700fe, 46a2bb5a7f7ea2728be50f8f5b29a20267f700fe, 46a2bb5a7f7ea2728be50f8f5b29a20267f700fe, 46a2bb5a7f7ea2728be50f8f5b29a20267f700fe, 46a2bb5a7f7ea2728be50f8f5b29a20267f700fe, 46a2bb5a7f7ea2728be50f8f5b29a20267f700feunaffected
LinuxLinux4.16, 0, 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.68, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.