LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21914: slimbus: messaging: Free transaction ID in delayed interrupt scenario

In the Linux kernel, the following vulnerability has been resolved: slimbus: messaging: Free transaction ID in delayed interrupt scenario In case of interrupt delay for any reason, slim_do_transfer() returns timeout error but the transaction ID (TID) is not freed. This results into invalid memory access inside qcom_slim_ngd_rx_msgq_cb() due to invalid TID. Fix the issue by freeing the TID in slim_do_transfer() before returning timeout error to avoid invalid memory access. Call trace: __memcpy_fromio+0x20/0x190 qcom_slim_ngd_rx_msgq_cb+0x130/0x290 [slim_qcom_ngd_ctrl] vchan_complete+0x2a0/0x4a0 tasklet_action_common+0x274/0x700 tasklet_action+0x28/0x3c _stext+0x188/0x620 run_ksoftirqd+0x34/0x74 smpboot_thread_fn+0x1d8/0x464 kthread+0x178/0x238 ret_from_fork+0x10/0x20 Code: aa0003e8 91000429 f100044a 3940002b (3800150b) ---[ end trace 0fe00bec2b975c99 ]--- Kernel panic - not syncing: Oops: Fatal exception in interrupt.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in Linux SLIMbus messaging can cause invalid memory access and a kernel panic when a hardware response arrives after a transaction timeout. The supplied CVSS rating is 7.8 (high) and assumes local, low-privileged access. Systems using the relevant Qualcomm SLIMbus driver deserve prompt review because a crash could disrupt availability.

Executive priority

Treat as high priority on systems using the affected Qualcomm SLIMbus path, especially availability-sensitive devices. Schedule prompt vendor-supported kernel updates after compatibility testing. For Linux systems lacking the relevant driver or hardware, validate non-exposure and retain normal patch cadence rather than assuming fleet-wide critical risk.

Technical view

slim_do_transfer() can time out without freeing its transaction identifier. A delayed interrupt may then reach qcom_slim_ngd_rx_msgq_cb() with an invalid identifier, causing invalid memory access and potentially a fatal kernel exception. The upstream correction frees the identifier before returning the timeout error. The supplied CVSS vector rates confidentiality, integrity, and availability impacts high.

Likely exposure

Exposure appears limited to affected Linux kernels using the relevant SLIMbus messaging path, particularly the Qualcomm NGD controller driver identified in the trace. Version data in the bundle is ambiguous, so kernel commit ancestry and distribution advisories should determine exposure. Systems without this driver or hardware path are less likely to be affected.

Exploitation context

The bundle provides no evidence of active exploitation, and the CVE is not marked as KEV. The CVSS vector describes a local attack requiring low privileges, low complexity, and no user interaction. Public evidence demonstrates a kernel-panic failure, but does not establish practical exploitation for confidentiality or integrity impact.

Researcher notes

The root cause is transaction-lifecycle mishandling during a timeout and delayed-interrupt race. The supplied trace ends in a fatal interrupt-context exception. Multiple stable-kernel commits indicate backports across branches. Exact vulnerable and fixed version boundaries are not reliably expressed in the bundle; use commit containment and vendor package advisories instead of version-string assumptions.

Mitigation direction

  • Apply a vendor kernel update containing the cited stable fix.
  • Consult distribution advisories to identify the corrected package for each deployed kernel.
  • Prioritize systems that load the Qualcomm SLIMbus NGD controller driver.
  • Restrict unnecessary local access until affected systems are updated.

Validation and detection

  • Inventory kernel versions and distribution package revisions across Linux systems.
  • Check whether the SLIMbus and Qualcomm NGD controller modules are present or loaded.
  • Compare kernel commit ancestry against the applicable cited stable fix.
  • After updating, confirm the running kernel matches the installed corrected package.
Prepared
Confidence
medium
Sources
12

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-2025-21914 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
1ADP providers
11Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-21914Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxafbdcc7c384b0d446da08b1e0901dc176b41b9e0, afbdcc7c384b0d446da08b1e0901dc176b41b9e0, afbdcc7c384b0d446da08b1e0901dc176b41b9e0, afbdcc7c384b0d446da08b1e0901dc176b41b9e0, afbdcc7c384b0d446da08b1e0901dc176b41b9e0, afbdcc7c384b0d446da08b1e0901dc176b41b9e0, afbdcc7c384b0d446da08b1e0901dc176b41b9e0, afbdcc7c384b0d446da08b1e0901dc176b41b9e0unaffected
LinuxLinux4.16, 0, 5.4.291, 5.10.235, 5.15.179, 6.1.131, 6.6.83, 6.12.19, 6.13.7, 6.14affected
Weakness

CWE details

No CWE listed

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