Answer in brief
CVE-2025-21914 records a Unknown severity vulnerability in slimbus: messaging: Free transaction ID in delayed interrupt scenario. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-21914 records a Unknown severity vulnerability in slimbus: messaging: Free transaction ID in delayed interrupt scenario. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <cec8c0ac173fe5321f03fdb1a09a9cb69bc9a9fe || >=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <a32e5198a9134772eb03f7b72a7849094c55bda9 || >=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <09d34c4cbc38485c7514069f25348e439555b282 || >=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <18ae4cee05c310c299ba75d7477dcf34be67aa16 || >=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <faac8e894014e8167471a8e4a5eb35a8fefbb82a || >=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <6abf3d8bb51cbaf886c3f08109a0462890b10db6 || >=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <0c541c8f6da23e0b92f0a6216d899659a7572074 || >=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <dcb0d43ba8eb9517e70b1a0e4b0ae0ab657a0e5a | cec8c0ac173fe5321f03fdb1a09a9cb69bc9a9fe, a32e5198a9134772eb03f7b72a7849094c55bda9, 09d34c4cbc38485c7514069f25348e439555b282, 18ae4cee05c310c299ba75d7477dcf34be67aa16, faac8e894014e8167471a8e4a5eb35a8fefbb82a, 6abf3d8bb51cbaf886c3f08109a0462890b10db6, 0c541c8f6da23e0b92f0a6216d899659a7572074, dcb0d43ba8eb9517e70b1a0e4b0ae0ab657a0e5a |
| Linux/Linuxgeneric | 4.16 | Not reported |
Published upstream
Apr 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <cec8c0ac173fe5321f03fdb1a09a9cb69bc9a9fe || >=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <a32e5198a9134772eb03f7b72a7849094c55bda9 || >=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <09d34c4cbc38485c7514069f25348e439555b282 || >=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <18ae4cee05c310c299ba75d7477dcf34be67aa16 || >=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <faac8e894014e8167471a8e4a5eb35a8fefbb82a || >=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <6abf3d8bb51cbaf886c3f08109a0462890b10db6 || >=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <0c541c8f6da23e0b92f0a6216d899659a7572074 || >=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <dcb0d43ba8eb9517e70b1a0e4b0ae0ab657a0e5a | cec8c0ac173fe5321f03fdb1a09a9cb69bc9a9fe, a32e5198a9134772eb03f7b72a7849094c55bda9, 09d34c4cbc38485c7514069f25348e439555b282, 18ae4cee05c310c299ba75d7477dcf34be67aa16, faac8e894014e8167471a8e4a5eb35a8fefbb82a, 6abf3d8bb51cbaf886c3f08109a0462890b10db6, 0c541c8f6da23e0b92f0a6216d899659a7572074, dcb0d43ba8eb9517e70b1a0e4b0ae0ab657a0e5a |
| Linux/Linuxgeneric | 4.16 | Not reported |
Published upstream
Apr 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.