Threats Tagged 'cve-2025-68746'
View all threats tagged with 'cve-2025-68746'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2025-68746'
Click on any threat for detailed analysis and mitigation recommendations
A vulnerability in the Linux kernel's tegra210-quad SPI driver involves improper timeout handling in the QSPI interrupt handler. When the CPU running the interrupt handler is heavily loaded, the IRQ thread may not execute before a transfer timeout occurs, leading to stale memory references. This can cause corruption and failure in SPI message handling. The issue has been addressed by clearing the current transfer pointer upon timeout and ensuring interrupts are cleared on failure to allow new interrupts to be processed. Join the discussion | GCVE Database | 12/24/2025, 15:30:44 UTC Added: 07/30/2026, 15:50:42 UTC |
In the Linux kernel, the following vulnerability has been resolved: spi: tegra210-quad: Fix timeout handling When the CPU that the QSPI interrupt handler runs on (typically CPU 0) is excessively busy, it can lead to rare cases of the IRQ thread not running before the transfer timeout is reached. While handling the timeouts, any pending transfers are cleaned up and the message that they correspond to is marked as failed, which leaves the curr_xfer field pointing at stale memory. To avoid this, clear curr_xfer to NULL upon timeout and check for this condition when the IRQ thread is finally run. While at it, also make sure to clear interrupts on failure so that new interrupts can be run. A better, more involved, fix would move the interrupt clearing into a hard IRQ handler. Ideally we would also want to signal that the IRQ thread no longer needs to be run after the timeout is hit to avoid the extra check for a valid transfer. Join the discussion | GCVE Database | 12/24/2025, 13:16:00 UTC Added: 07/18/2026, 11:31:51 UTC |
Showing 1 to 2 of 2 results