{"id":"CVE-2023-54040","title":"ice: fix wrong fallback logic for FDIR","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nice: fix wrong fallback logic for FDIR\n\nWhen adding a FDIR filter, if ice_vc_fdir_set_irq_ctx returns failure,\nthe inserted fdir entry will not be removed and if ice_vc…","severity":"high","cvss":8.8,"cvssVector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","cvssSource":"cna","vendor":"Linux","product":"Linux","affected":["Linux >= 1f7ea1cd6a3748427512ccc9582e18cd9efea966 < 391d28c0e38c0e5b11a4240a2b4976cf63e87f45","Linux >= 1f7ea1cd6a3748427512ccc9582e18cd9efea966 < aad3b871efe26f36f45f8b4649653b5d3fd9c35e","Linux >= 1f7ea1cd6a3748427512ccc9582e18cd9efea966 < cbfed5f114b5310f221979fc8190f55c6abc3400","Linux >= 1f7ea1cd6a3748427512ccc9582e18cd9efea966 < b4a01ace20f5c93c724abffc0a83ec84f514b98d","Linux 5.13"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"total","timestamp":"2026-10-15T21:37:55.813707Z"},"published":"2025-12-24","updated":"2026-10-15","sourceUpdated":"2026-10-15T21:41:38.132Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2023-54040","references":[{"url":"https://git.kernel.org/stable/c/391d28c0e38c0e5b11a4240a2b4976cf63e87f45"},{"url":"https://git.kernel.org/stable/c/aad3b871efe26f36f45f8b4649653b5d3fd9c35e"},{"url":"https://git.kernel.org/stable/c/cbfed5f114b5310f221979fc8190f55c6abc3400"},{"url":"https://git.kernel.org/stable/c/b4a01ace20f5c93c724abffc0a83ec84f514b98d"}],"tags":["cve.org"],"epss":0.00144,"epssPercentile":0.03277,"ingestedAt":"2026-10-15T22:48:25.426Z","slug":"CVE-2023-54040","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix wrong fallback logic for FDIR\n\nWhen adding a FDIR filter, if ice_vc_fdir_set_irq_ctx returns failure,\nthe inserted fdir entry will not be removed and if ice_vc_fdir_write_fltr\nreturns failure, the fdir context info for irq handler will not be cleared\nwhich may lead to inconsistent or memory leak issue. This patch refines\nfailure cases to resolve this issue.\n\n## Affected\n\n- `Linux >= 1f7ea1cd6a3748427512ccc9582e18cd9efea966 < 391d28c0e38c0e5b11a4240a2b4976cf63e87f45`\n- `Linux >= 1f7ea1cd6a3748427512ccc9582e18cd9efea966 < aad3b871efe26f36f45f8b4649653b5d3fd9c35e`\n- `Linux >= 1f7ea1cd6a3748427512ccc9582e18cd9efea966 < cbfed5f114b5310f221979fc8190f55c6abc3400`\n- `Linux >= 1f7ea1cd6a3748427512ccc9582e18cd9efea966 < b4a01ace20f5c93c724abffc0a83ec84f514b98d`\n- `Linux 5.13`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"twilight","depthScore":48,"depthScoreParts":{"impact":48.4,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}