{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-31517 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-31517 is a medium-severity denial of service vulnerability in Linux kernel, published on 22 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-31517 and fix it if it is affected.\n\nWhat it is: CVE-2026-31517 is a medium-severity denial of service vulnerability in Linux kernel, published on 22 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-31517 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-31517/ (Markdown: https://insights.sbomify.com/CVE-2026-31517/index.md)","id":"CVE-2026-31517","markdown":"https://insights.sbomify.com/CVE-2026-31517/index.md","name":"CVE-2026-31517","record":{"aliases":["BELL-CVE-2026-31517","DEBIAN-CVE-2026-31517","GHSA-759f-2cpp-x5g6","UBUNTU-CVE-2026-31517"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A remote attacker can cause a kernel panic and system crash by sending crafted IP-TFS fragments that trigger a linearization assertion failure.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: iptfs: fix skb_put() panic on non-linear skb during reassembly\n\nIn iptfs_reassem_cont(), IP-TFS attempts to append data to the new inner\npacket 'newskb' that is being reassembled. First a zero-copy approach is\ntried if it succeeds then newskb becomes non-linear.\n\nWhen a subsequent fragment in the same datagram does not meet the\nfast-path conditions, a memory copy is performed. It calls skb_put() to\nappend the data and as newskb is non-linear it triggers\nSKB_LINEAR_ASSERT check.\n\n Oops: invalid opcode: 0000 [#1] SMP NOPTI\n [...]\n RIP: 0010:skb_put+0x3c/0x40\n [...]\n Call Trace:\n  \u003cIRQ\u003e\n  iptfs_reassem_cont+0x1ab/0x5e0 [xfrm_iptfs]\n  iptfs_input_ordered+0x2af/0x380 [xfrm_iptfs]\n  iptfs_input+0x122/0x3e0 [xfrm_iptfs]\n  xfrm_input+0x91e/0x1a50\n  xfrm4_esp_rcv+0x3a/0x110\n  ip_protocol_deliver_rcu+0x1d7/0x1f0\n  ip_local_deliver_finish+0xbe/0x1e0\n  __netif_receive_skb_core.constprop.0+0xb56/0x1120\n  __netif_receive_skb_list_core+0x133/0x2b0\n  netif_receive_skb_list_internal+0x1ff/0x3f0\n  napi_complete_done+0x81/0x220\n  virtnet_poll+0x9d6/0x116e [virtio_net]\n  __napi_poll.constprop.0+0x2b/0x270\n  net_rx_action+0x162/0x360\n  handle_softirqs+0xdc/0x510\n  __irq_exit_rcu+0xe7/0x110\n  irq_exit_rcu+0xe/0x20\n  common_interrupt+0x85/0xa0\n  \u003c/IRQ\u003e\n  \u003cTASK\u003e\n\nFix this by checking if the skb is non-linear. If it is, linearize it by\ncalling skb_linearize(). As the initial allocation of newskb originally\nreserved enough tailroom for the entire reassembled packet we do not\nneed to check if we have enough tailroom or extend it.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"xfrm: iptfs: fix skb_put() panic on non-linear skb during reassembly","id":"CVE-2026-31517","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"esp: fix skb leak with espintcp and async crypto","id":"CVE-2026-31518"},"packages":[],"prev":{"headline":"xfrm: prevent policy_hthresh.work from racing with netns teardown","id":"CVE-2026-31516"},"products":["Linux"],"published":"2026-04-22","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A remote attacker can cause a kernel panic and system crash by sending crafted IP-TFS fragments that trigger a linearization assertion failure.","url":"https://insights.sbomify.com/CVE-2026-31517/"}