{"id":74828,"date":"2025-12-24T16:46:29","date_gmt":"2025-12-24T13:16:29","guid":{"rendered":"https:\/\/afaghhosting.net\/blog\/cve-2025-68746-spi-tegra210-quad-fix-timeout-handling\/"},"modified":"2025-12-24T16:46:29","modified_gmt":"2025-12-24T13:16:29","slug":"cve-2025-68746-spi-tegra210-quad-fix-timeout-handling","status":"publish","type":"post","link":"https:\/\/afaghhosting.net\/blog\/cve-2025-68746-spi-tegra210-quad-fix-timeout-handling\/","title":{"rendered":"CVE-2025-68746 &#8211; spi: tegra210-quad: Fix timeout handling"},"content":{"rendered":"<p>CVE ID : CVE-2025-68746<\/p>\n<p>Published :  Dec. 24, 2025, 1:16 p.m. | 1\u00a0hour, 5\u00a0minutes ago<\/p>\n<p>Description : In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>spi: tegra210-quad: Fix timeout handling<\/p>\n<p>When the CPU that the QSPI interrupt handler runs on (typically CPU 0)<br \/>\nis excessively busy, it can lead to rare cases of the IRQ thread not<br \/>\nrunning before the transfer timeout is reached.<\/p>\n<p>While handling the timeouts, any pending transfers are cleaned up and<br \/>\nthe message that they correspond to is marked as failed, which leaves<br \/>\nthe curr_xfer field pointing at stale memory.<\/p>\n<p>To avoid this, clear curr_xfer to NULL upon timeout and check for this<br \/>\ncondition when the IRQ thread is finally run.<\/p>\n<p>While at it, also make sure to clear interrupts on failure so that new<br \/>\ninterrupts can be run.<\/p>\n<p>A better, more involved, fix would move the interrupt clearing into a<br \/>\nhard IRQ handler. Ideally we would also want to signal that the IRQ<br \/>\nthread no longer needs to be run after the timeout is hit to avoid the<br \/>\nextra check for a valid transfer.<\/p>\n<p>Severity: 0.0 | NA<\/p>\n<p>Visit the link for more details, such as CVSS details, affected products, timeline, and more&#8230;\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"<p>CVE ID : CVE-2025-68746 Published : Dec. 24, 2025, 1:16 p.m. | 1\u00a0hour, 5\u00a0minutes ago Description : 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 &hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-74828","post","type-post","status-publish","format-standard","hentry","category-vulnerability"],"_links":{"self":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/74828","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/comments?post=74828"}],"version-history":[{"count":0,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/74828\/revisions"}],"wp:attachment":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/media?parent=74828"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/categories?post=74828"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/tags?post=74828"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}