LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23182: spi: tegra: Fix a memory leak in tegra_slink_probe()

In the Linux kernel, the following vulnerability has been resolved: spi: tegra: Fix a memory leak in tegra_slink_probe() In tegra_slink_probe(), when platform_get_irq() fails, it directly returns from the function with an error code, which causes a memory leak. Replace it with a goto label to ensure proper cleanup.

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

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel cleanup bug in the Tegra SPI driver. If IRQ lookup fails during device initialization, memory is not released. The sources do not provide CVSS, business impact details, or evidence of active exploitation.

Executive priority

Treat this as a targeted Linux kernel maintenance issue, not an emergency based on current evidence. Patch through normal kernel update cycles, with higher priority for Tegra-based operational technology, embedded, or appliance fleets.

Technical view

The flaw is in tegra_slink_probe(). When platform_get_irq() fails, the function returned immediately instead of taking the cleanup path, causing a memory leak. The kernel fix replaces that direct return with cleanup through a goto label.

Likely exposure

Exposure appears limited to Linux systems using the Tegra SPI controller driver and affected kernel versions or commits listed in the CVE record. The source bundle does not identify distributions, appliances, or cloud images affected.

Exploitation context

No active exploitation is reported in the provided sources, and the CVE is not marked KEV. The record describes an error-path memory leak during device probe, but does not provide exploitability, privilege, or remote attack details.

Researcher notes

The provided record lacks CVSS, CWE, trigger conditions beyond platform_get_irq() failure, and exploitability analysis. Assessment should stay focused on affected kernel lineage, Tegra SPI driver presence, and whether downstream vendor kernels carry the stable commits.

Mitigation direction

  • Identify systems running affected Linux kernel versions listed in the CVE record.
  • Prioritize Tegra-based devices or builds enabling the Tegra SPI controller driver.
  • Apply the relevant upstream stable kernel fix or vendor kernel update.
  • Check distribution and device vendor advisories for packaged update guidance.

Validation and detection

  • Inventory kernel versions and compare against the affected and fixed versions in the CVE record.
  • Confirm whether the Tegra SPI driver is built, loaded, or used on candidate systems.
  • Review kernel changelogs for the referenced stable commits.
  • Verify vendor kernels include the tegra_slink_probe() cleanup-path fix.
Prepared
Confidence
medium
Sources
8

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-23182 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
7Source 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
LinuxLinuxb64683f5d7282f7b160e9867e33cdac00b5c792b, 5c25f89c00b97844d0427f0f96818a15714bd609, 46ee23101f32a1ced5335d5407d5ecffd160ccdf, eb9913b511f10968a02cfa5329a896855dd152a3, eb9913b511f10968a02cfa5329a896855dd152a3, eb9913b511f10968a02cfa5329a896855dd152a3, 4eb8065494ca19caba3f45fc83941fd568a8c3cd, 5.15.139, 6.1.63, 6.6.2, 6.5.12unaffected
LinuxLinux6.7, 0, 5.15.200, 6.1.163, 6.6.124, 6.12.70, 6.18.10, 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.