{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-53180","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-06-09T07:44:35.390Z","datePublished":"2026-06-25T08:38:55.332Z","dateUpdated":"2026-08-05T12:33:47.890Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T12:33:47.890Z"},"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 ]"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","baseScore":7.5,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:N - Unauthenticated remote packets can create non-pinned global kernel timers, for example incomplete IPv4/IPv6 fragment reassembly queues whose timers are armed from packet receive paths. Those timers are handled by the affected timer migration code, making a network trigger reasonable on exposed Linux hosts.\nAC:L - The bug requires a timing window where jiffies advances between local global timer processing and migration handling, but an attacker can repeatedly create many expiring global timers to exercise it. Under the required rule, this uncertainty is scored as low complexity.\nPR:N - The remote fragmented-packet path requires no local account, capabilities, or protocol authentication. It can be reached before any application-level authorization.\nUI:N - No victim user action is required once the host receives the triggering traffic. Timer expiry and softirq processing happen autonomously in the kernel.\nS:U - The impact remains within the same kernel security authority. There is no VM, IOMMU, container-boundary, or sandbox escape scope change.\nC:N - The defect is a timer migration logic livelock, not a memory disclosure or memory corruption issue. No kernel memory read primitive is indicated.\nI:N - The skipped timer callback and repeated requeue do not provide data modification, arbitrary write, or control-flow hijack. The observed effect is denial of service only.\nA:H - The stale expired timer causes tmigr_handle_remote_up() to spin indefinitely in the timer softirq path. An infinite kernel livelock/soft lockup is a high availability impact."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["kernel/time/timer_migration.c"],"versions":[{"version":"7ee988770326fca440472200c3eb58935fe712f6","lessThan":"07b3b83587fb3012619f4439389b64a955fc7836","status":"affected","versionType":"git"},{"version":"7ee988770326fca440472200c3eb58935fe712f6","lessThan":"1d6c2062b77be09ec15d6bf637b2e2221c4482fc","status":"affected","versionType":"git"},{"version":"7ee988770326fca440472200c3eb58935fe712f6","lessThan":"d338e61ea94052a786aac9f58e9f0d8520afa0fd","status":"affected","versionType":"git"},{"version":"7ee988770326fca440472200c3eb58935fe712f6","lessThan":"d486b4934a8e504376b85cdb3766f306d57aff5b","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["kernel/time/timer_migration.c"],"versions":[{"version":"6.9","status":"affected"},{"version":"0","lessThan":"6.9","status":"unaffected","versionType":"semver"},{"version":"6.12.94","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.18.36","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.0.13","lessThanOrEqual":"7.0.*","status":"unaffected","versionType":"semver"},{"version":"7.1","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.9","versionEndExcluding":"6.12.94"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.9","versionEndExcluding":"6.18.36"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.9","versionEndExcluding":"7.0.13"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.9","versionEndExcluding":"7.1"}]}]}],"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"}}}}