{"api_version":"1","generated_at":"2026-06-25T11:33:15+00:00","cve":"CVE-2026-53197","urls":{"html":"https://cve.report/CVE-2026-53197","api":"https://cve.report/api/cve/CVE-2026-53197.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-53197","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-53197"},"summary":{"title":"xfrm: iptfs: fix ABBA deadlock in iptfs_destroy_state()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: iptfs: fix ABBA deadlock in iptfs_destroy_state()\n\niptfs_destroy_state() calls hrtimer_cancel() while holding a spinlock\nthat the timer callback also acquires, leading to an ABBA deadlock on\nSMP systems.\n\nFor the output timer (iptfs_timer):\n  - iptfs_destroy_state() holds x->lock, calls hrtimer_cancel()\n  - iptfs_delay_timer() callback takes x->lock\n\nFor the drop timer (drop_timer):\n  - iptfs_destroy_state() holds drop_lock, calls hrtimer_cancel()\n  - iptfs_drop_timer() callback takes drop_lock\n\nBoth timers use HRTIMER_MODE_REL_SOFT, so their callbacks run in softirq\ncontext.  When hrtimer_cancel() is called for a soft timer that is\ncurrently executing on another CPU, hrtimer_cancel_wait_running() spins\non softirq_expiry_lock -- the same lock held by the softirq running the\ncallback.  If the callback is blocked waiting for the spinlock held by\nthe caller of hrtimer_cancel(), a circular dependency forms:\n\n  CPU 0: holds lock_A -> waits for softirq_expiry_lock\n  CPU 1: holds softirq_expiry_lock -> waits for lock_A\n\nFix by calling hrtimer_cancel() before acquiring the respective locks.\nhrtimer_cancel() is safe to call without holding any lock and will wait\nfor any in-progress callback to complete.  For the output timer, the\nlock is still acquired afterwards to drain the packet queue.  For the\ndrop timer, the lock/unlock pair is removed entirely since it only\nexisted to serialize with the timer callback, which hrtimer_cancel()\nalready guarantees.\n\nFound by source code audit.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-06-25 09:16:37","updated_at":"2026-06-25 09:16:37"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/a13ca53e47e500854a3b9ec18b5dc83acfec863e","name":"https://git.kernel.org/stable/c/a13ca53e47e500854a3b9ec18b5dc83acfec863e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/822b98d354e63e8249e85473c5f3c519f3c9cecc","name":"https://git.kernel.org/stable/c/822b98d354e63e8249e85473c5f3c519f3c9cecc","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c8a8a75b733467b00c08b91a38dbaf207a08ed6e","name":"https://git.kernel.org/stable/c/c8a8a75b733467b00c08b91a38dbaf207a08ed6e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53197","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53197","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4b3faf610cc63bfac972711635eafbca5e7d7117 a13ca53e47e500854a3b9ec18b5dc83acfec863e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4b3faf610cc63bfac972711635eafbca5e7d7117 822b98d354e63e8249e85473c5f3c519f3c9cecc git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4b3faf610cc63bfac972711635eafbca5e7d7117 c8a8a75b733467b00c08b91a38dbaf207a08ed6e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.14","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.14 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":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["net/xfrm/xfrm_iptfs.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"a13ca53e47e500854a3b9ec18b5dc83acfec863e","status":"affected","version":"4b3faf610cc63bfac972711635eafbca5e7d7117","versionType":"git"},{"lessThan":"822b98d354e63e8249e85473c5f3c519f3c9cecc","status":"affected","version":"4b3faf610cc63bfac972711635eafbca5e7d7117","versionType":"git"},{"lessThan":"c8a8a75b733467b00c08b91a38dbaf207a08ed6e","status":"affected","version":"4b3faf610cc63bfac972711635eafbca5e7d7117","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/xfrm/xfrm_iptfs.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.14"},{"lessThan":"6.14","status":"unaffected","version":"0","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.18.36","versionStartIncluding":"6.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.13","versionStartIncluding":"6.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1","versionStartIncluding":"6.14","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: iptfs: fix ABBA deadlock in iptfs_destroy_state()\n\niptfs_destroy_state() calls hrtimer_cancel() while holding a spinlock\nthat the timer callback also acquires, leading to an ABBA deadlock on\nSMP systems.\n\nFor the output timer (iptfs_timer):\n  - iptfs_destroy_state() holds x->lock, calls hrtimer_cancel()\n  - iptfs_delay_timer() callback takes x->lock\n\nFor the drop timer (drop_timer):\n  - iptfs_destroy_state() holds drop_lock, calls hrtimer_cancel()\n  - iptfs_drop_timer() callback takes drop_lock\n\nBoth timers use HRTIMER_MODE_REL_SOFT, so their callbacks run in softirq\ncontext.  When hrtimer_cancel() is called for a soft timer that is\ncurrently executing on another CPU, hrtimer_cancel_wait_running() spins\non softirq_expiry_lock -- the same lock held by the softirq running the\ncallback.  If the callback is blocked waiting for the spinlock held by\nthe caller of hrtimer_cancel(), a circular dependency forms:\n\n  CPU 0: holds lock_A -> waits for softirq_expiry_lock\n  CPU 1: holds softirq_expiry_lock -> waits for lock_A\n\nFix by calling hrtimer_cancel() before acquiring the respective locks.\nhrtimer_cancel() is safe to call without holding any lock and will wait\nfor any in-progress callback to complete.  For the output timer, the\nlock is still acquired afterwards to drain the packet queue.  For the\ndrop timer, the lock/unlock pair is removed entirely since it only\nexisted to serialize with the timer callback, which hrtimer_cancel()\nalready guarantees.\n\nFound by source code audit."}],"providerMetadata":{"dateUpdated":"2026-06-25T08:39:06.991Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/a13ca53e47e500854a3b9ec18b5dc83acfec863e"},{"url":"https://git.kernel.org/stable/c/822b98d354e63e8249e85473c5f3c519f3c9cecc"},{"url":"https://git.kernel.org/stable/c/c8a8a75b733467b00c08b91a38dbaf207a08ed6e"}],"title":"xfrm: iptfs: fix ABBA deadlock in iptfs_destroy_state()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-53197","datePublished":"2026-06-25T08:39:06.991Z","dateReserved":"2026-06-09T07:44:35.391Z","dateUpdated":"2026-06-25T08:39:06.991Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-06-25 09:16:37","lastModifiedDate":"2026-06-25 09:16:37","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"53197","Ordinal":"1","Title":"xfrm: iptfs: fix ABBA deadlock in iptfs_destroy_state()","CVE":"CVE-2026-53197","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"53197","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: iptfs: fix ABBA deadlock in iptfs_destroy_state()\n\niptfs_destroy_state() calls hrtimer_cancel() while holding a spinlock\nthat the timer callback also acquires, leading to an ABBA deadlock on\nSMP systems.\n\nFor the output timer (iptfs_timer):\n  - iptfs_destroy_state() holds x->lock, calls hrtimer_cancel()\n  - iptfs_delay_timer() callback takes x->lock\n\nFor the drop timer (drop_timer):\n  - iptfs_destroy_state() holds drop_lock, calls hrtimer_cancel()\n  - iptfs_drop_timer() callback takes drop_lock\n\nBoth timers use HRTIMER_MODE_REL_SOFT, so their callbacks run in softirq\ncontext.  When hrtimer_cancel() is called for a soft timer that is\ncurrently executing on another CPU, hrtimer_cancel_wait_running() spins\non softirq_expiry_lock -- the same lock held by the softirq running the\ncallback.  If the callback is blocked waiting for the spinlock held by\nthe caller of hrtimer_cancel(), a circular dependency forms:\n\n  CPU 0: holds lock_A -> waits for softirq_expiry_lock\n  CPU 1: holds softirq_expiry_lock -> waits for lock_A\n\nFix by calling hrtimer_cancel() before acquiring the respective locks.\nhrtimer_cancel() is safe to call without holding any lock and will wait\nfor any in-progress callback to complete.  For the output timer, the\nlock is still acquired afterwards to drain the packet queue.  For the\ndrop timer, the lock/unlock pair is removed entirely since it only\nexisted to serialize with the timer callback, which hrtimer_cancel()\nalready guarantees.\n\nFound by source code audit.","Type":"Description","Title":"xfrm: iptfs: fix ABBA deadlock in iptfs_destroy_state()"}]}}}