CVE-2026-23090: slimbus: core: fix device reference leak on report present
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 02b78bbfbafe49832e508079148cb87cdfa55825, 2ddc09f6a0a221b1d91a7cbc8cc2cefdbd334fe6, 54de72a7aabc0749938d7a2833a0c1a5d3ed7ac9.
Low priority for now. Upgrade to Linux Linux 02b78bbfbafe49832e508079148cb87cdfa55825, 2ddc09f6a0a221b1d91a7cbc8cc2cefdbd334fe6, 54de72a7aabc0749938d7a2833a0c1a5d3ed7ac9 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 4, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.16 and later · before 5.10.249
- linux linux kernel5.11 and later · before 5.15.199
- linux linux kernel5.16 and later · before 6.1.162
- linux linux kernel6.2 and later · before 6.6.122
- linux linux kernel6.7 and later · before 6.12.68
- linux linux kernel6.13 and later · before 6.18.8
- linux linux kernel6.19
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.16affected
- 46a2bb5a7f7ea2728be50f8f5b29a20267f700fe and later · before b1217e40705b2f6d311c197b12866752656217ffaffected · git
- 46a2bb5a7f7ea2728be50f8f5b29a20267f700fe and later · before 948615429c9f2ac9d25d4e1f1a4472926b217a9aaffected · git
- 46a2bb5a7f7ea2728be50f8f5b29a20267f700fe and later · before 02b78bbfbafe49832e508079148cb87cdfa55825affected · git
- 46a2bb5a7f7ea2728be50f8f5b29a20267f700fe and later · before 2ddc09f6a0a221b1d91a7cbc8cc2cefdbd334fe6affected · git
- 46a2bb5a7f7ea2728be50f8f5b29a20267f700fe and later · before 54de72a7aabc0749938d7a2833a0c1a5d3ed7ac9affected · git
- 46a2bb5a7f7ea2728be50f8f5b29a20267f700fe and later · before 6602bb4d1338e92b5838e50322b87697bdbd2ee0affected · git
- 46a2bb5a7f7ea2728be50f8f5b29a20267f700fe and later · before 9391380eb91ea5ac792aae9273535c8da5b9aa01affected · git
- before 4.16not affected · semver
- 5.10.249 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.69-1 | 6.12.69-1 |
| Debian:14 | linux | before 6.18.8-1 | 6.18.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-23082Feb 4, 2026 · can: gs_usb: gs_usb_receive_bulk_callback(): unanchor URL on usb_submit_urb() error22Monitor
- ← EarlierCVE-2026-23088Feb 4, 2026 · tracing: Fix crash on synthetic stacktrace field usage22Monitor
- Later →CVE-2026-23092Feb 4, 2026 · iio: dac: ad3552r-hs: fix out-of-bound write in ad3552r_hs_write_data_source31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 02b78bbfbafe49832e508079148cb87cdfa55825 | Vendor (CNA) |
| Linux Linux | 2ddc09f6a0a221b1d91a7cbc8cc2cefdbd334fe6 | Vendor (CNA) |
| Linux Linux | 54de72a7aabc0749938d7a2833a0c1a5d3ed7ac9 | Vendor (CNA) |
| Linux Linux | 6602bb4d1338e92b5838e50322b87697bdbd2ee0 | Vendor (CNA) |
| Linux Linux | 9391380eb91ea5ac792aae9273535c8da5b9aa01 | Vendor (CNA) |
| Linux Linux | 948615429c9f2ac9d25d4e1f1a4472926b217a9a | Vendor (CNA) |
| Linux Linux | b1217e40705b2f6d311c197b12866752656217ff | Vendor (CNA) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/2ddc09f6a0a221b1d91a7cbc8cc2cefdbd334fe6
- git.kernel.org/stable/c/54de72a7aabc0749938d7a2833a0c1a5d3ed7ac9
- git.kernel.org/stable/c/6602bb4d1338e92b5838e50322b87697bdbd2ee0
- git.kernel.org/stable/c/9391380eb91ea5ac792aae9273535c8da5b9aa01
- git.kernel.org/stable/c/948615429c9f2ac9d25d4e1f1a4472926b217a9a
- git.kernel.org/stable/c/b1217e40705b2f6d311c197b12866752656217ff
Vendor advisories and official records. Exploit/PoC links are deliberately left out.