{"api_version":"1","generated_at":"2026-06-26T23:08:14+00:00","cve":"CVE-2026-53180","urls":{"html":"https://cve.report/CVE-2026-53180","api":"https://cve.report/api/cve/CVE-2026-53180.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-53180","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-53180"},"summary":{"title":"timers/migration: Fix livelock in tmigr_handle_remote_up()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntimers/migration: Fix livelock in tmigr_handle_remote_up()\n\ntmigr_handle_remote_cpu() skips timer_expire_remote() when cpu ==\nsmp_processor_id(), assuming the local softirq path already handled this\nCPU's timers.\n\nThis assumption is wrong because jiffies can advance after the handling of\nthe CPU's global timers in run_timer_base(BASE_GLOBAL) and before\ntmigr_handle_remote() evaluates the expiry times.\n\nAs a consequence a timer which expires after the CPU local timer wheel\nadvanced and becomes expired in the remote handling is ignored and the\ncallback is never invoked and removed from the timer wheel.\n\nWhat's worse is that fetch_next_timer_interrupt_remote() keeps reporting it\nas expired, and the event is re-queued with expires == now on each\niteration.  The goto-again loop spins indefinitely.\n\nFix this by calling timer_expire_remote() unconditionally. That's minimal\noverhead for the common case as __run_timer_base() returns immediately if\nthere is nothing to expire in the local wheel.\n\n[ tglx: Amend change log and add a comment ]","state":"PUBLISHED","assigner":"Linux","published_at":"2026-06-25 09:16:35","updated_at":"2026-06-25 09:16:35"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/d486b4934a8e504376b85cdb3766f306d57aff5b","name":"https://git.kernel.org/stable/c/d486b4934a8e504376b85cdb3766f306d57aff5b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/d338e61ea94052a786aac9f58e9f0d8520afa0fd","name":"https://git.kernel.org/stable/c/d338e61ea94052a786aac9f58e9f0d8520afa0fd","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/1d6c2062b77be09ec15d6bf637b2e2221c4482fc","name":"https://git.kernel.org/stable/c/1d6c2062b77be09ec15d6bf637b2e2221c4482fc","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/07b3b83587fb3012619f4439389b64a955fc7836","name":"https://git.kernel.org/stable/c/07b3b83587fb3012619f4439389b64a955fc7836","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53180","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53180","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7ee988770326fca440472200c3eb58935fe712f6 07b3b83587fb3012619f4439389b64a955fc7836 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7ee988770326fca440472200c3eb58935fe712f6 1d6c2062b77be09ec15d6bf637b2e2221c4482fc git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7ee988770326fca440472200c3eb58935fe712f6 d338e61ea94052a786aac9f58e9f0d8520afa0fd git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7ee988770326fca440472200c3eb58935fe712f6 d486b4934a8e504376b85cdb3766f306d57aff5b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.9","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.9 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.94 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.36 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.13 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"53180","cve":"CVE-2026-53180","epss":"0.001750000","percentile":"0.072010000","score_date":"2026-06-25","updated_at":"2026-06-26 00:06:14"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["kernel/time/timer_migration.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"07b3b83587fb3012619f4439389b64a955fc7836","status":"affected","version":"7ee988770326fca440472200c3eb58935fe712f6","versionType":"git"},{"lessThan":"1d6c2062b77be09ec15d6bf637b2e2221c4482fc","status":"affected","version":"7ee988770326fca440472200c3eb58935fe712f6","versionType":"git"},{"lessThan":"d338e61ea94052a786aac9f58e9f0d8520afa0fd","status":"affected","version":"7ee988770326fca440472200c3eb58935fe712f6","versionType":"git"},{"lessThan":"d486b4934a8e504376b85cdb3766f306d57aff5b","status":"affected","version":"7ee988770326fca440472200c3eb58935fe712f6","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["kernel/time/timer_migration.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.9"},{"lessThan":"6.9","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.94","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.36","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.13","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.94","versionStartIncluding":"6.9","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.36","versionStartIncluding":"6.9","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.13","versionStartIncluding":"6.9","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1","versionStartIncluding":"6.9","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ntimers/migration: Fix livelock in tmigr_handle_remote_up()\n\ntmigr_handle_remote_cpu() skips timer_expire_remote() when cpu ==\nsmp_processor_id(), assuming the local softirq path already handled this\nCPU's timers.\n\nThis assumption is wrong because jiffies can advance after the handling of\nthe CPU's global timers in run_timer_base(BASE_GLOBAL) and before\ntmigr_handle_remote() evaluates the expiry times.\n\nAs a consequence a timer which expires after the CPU local timer wheel\nadvanced and becomes expired in the remote handling is ignored and the\ncallback is never invoked and removed from the timer wheel.\n\nWhat's worse is that fetch_next_timer_interrupt_remote() keeps reporting it\nas expired, and the event is re-queued with expires == now on each\niteration.  The goto-again loop spins indefinitely.\n\nFix this by calling timer_expire_remote() unconditionally. That's minimal\noverhead for the common case as __run_timer_base() returns immediately if\nthere is nothing to expire in the local wheel.\n\n[ tglx: Amend change log and add a comment ]"}],"providerMetadata":{"dateUpdated":"2026-06-25T08:38:55.332Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/07b3b83587fb3012619f4439389b64a955fc7836"},{"url":"https://git.kernel.org/stable/c/1d6c2062b77be09ec15d6bf637b2e2221c4482fc"},{"url":"https://git.kernel.org/stable/c/d338e61ea94052a786aac9f58e9f0d8520afa0fd"},{"url":"https://git.kernel.org/stable/c/d486b4934a8e504376b85cdb3766f306d57aff5b"}],"title":"timers/migration: Fix livelock in tmigr_handle_remote_up()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-53180","datePublished":"2026-06-25T08:38:55.332Z","dateReserved":"2026-06-09T07:44:35.390Z","dateUpdated":"2026-06-25T08:38:55.332Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-06-25 09:16:35","lastModifiedDate":"2026-06-25 09:16:35","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"53180","Ordinal":"1","Title":"timers/migration: Fix livelock in tmigr_handle_remote_up()","CVE":"CVE-2026-53180","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"53180","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ntimers/migration: Fix livelock in tmigr_handle_remote_up()\n\ntmigr_handle_remote_cpu() skips timer_expire_remote() when cpu ==\nsmp_processor_id(), assuming the local softirq path already handled this\nCPU's timers.\n\nThis assumption is wrong because jiffies can advance after the handling of\nthe CPU's global timers in run_timer_base(BASE_GLOBAL) and before\ntmigr_handle_remote() evaluates the expiry times.\n\nAs a consequence a timer which expires after the CPU local timer wheel\nadvanced and becomes expired in the remote handling is ignored and the\ncallback is never invoked and removed from the timer wheel.\n\nWhat's worse is that fetch_next_timer_interrupt_remote() keeps reporting it\nas expired, and the event is re-queued with expires == now on each\niteration.  The goto-again loop spins indefinitely.\n\nFix this by calling timer_expire_remote() unconditionally. That's minimal\noverhead for the common case as __run_timer_base() returns immediately if\nthere is nothing to expire in the local wheel.\n\n[ tglx: Amend change log and add a comment ]","Type":"Description","Title":"timers/migration: Fix livelock in tmigr_handle_remote_up()"}]}}}