CVE-2026-23090

Local service interruption via leaked device references

Published Feb 4, 2026 · Updated Feb 4, 2026

Device reference leak in the Linux kernel Slimbus core allows local users to interrupt service through report-present events. slim_device_report_present() obtains a reference through slim_get_device() for an registered device but returns without calling put_device(), so each processed report retains the reference. Reachability requires local low-privileged access and a Slimbus controller path that processes repeated report-present messages; the bounded consequence is resource exhaustion and service interruption.

CVSS severity5.5
Medium
EPSS probability0.13%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Device reference leak in the Linux kernel Slimbus core allows local users to interrupt service through report-present events. slim_device_report_present() obtains a reference through slim_get_device() for an registered device but returns without calling put_device(), so each processed report retains the reference. Reachability requires local low-privileged access and a Slimbus controller path that processes repeated report-present messages; the bounded consequence is resource exhaustion and service interruption.

The record

CVE
CVE-2026-23090
Published
Feb 4, 2026
Updated
Feb 4, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 4, 2026CVE publishedPublication date reported by the CVE source.
  2. Feb 4, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.16
  2. Affected versionversion=46a2bb5a7f7ea2728be50f8f5b29a20267f700fe <2ddc09f6a0a221b1d91a7cbc8cc2cefdbd334fe6
  3. Affected versionversion=46a2bb5a7f7ea2728be50f8f5b29a20267f700fe <54de72a7aabc0749938d7a2833a0c1a5d3ed7ac9
  4. Affected versionversion=46a2bb5a7f7ea2728be50f8f5b29a20267f700fe <6602bb4d1338e92b5838e50322b87697bdbd2ee0
  5. Affected versionversion=46a2bb5a7f7ea2728be50f8f5b29a20267f700fe <9391380eb91ea5ac792aae9273535c8da5b9aa01

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=4.16; version=46a2bb5a7f7ea2728be50f8f5b29a20267f700fe <2ddc09f6a0a221b1d91a7cbc8cc2cefdbd334fe6; version=46a2bb5a7f7ea2728be50f8f5b29a20267f700fe <54de72a7aabc0749938d7a2833a0c1a5d3ed7ac9; version=46a2bb5a7f7ea2728be50f8f5b29a20267f700fe <6602bb4d1338e92b5838e50322b87697bdbd2ee0; version=46a2bb5a7f7ea2728be50f8f5b29a20267f700fe <9391380eb91ea5ac792aae9273535c8da5b9aa01

Published CVSS scores

5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo