{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-53366 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-53366 is a high-severity vulnerability in Linux kernel, published on 16 Jul 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-53366 and fix it if it is affected.\n\nWhat it is: CVE-2026-53366 is a high-severity vulnerability in Linux kernel, published on 16 Jul 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-53366 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-53366/ (Markdown: https://insights.sbomify.com/CVE-2026-53366/index.md)","id":"CVE-2026-53366","markdown":"https://insights.sbomify.com/CVE-2026-53366/index.md","name":"CVE-2026-53366","record":{"aliases":["BELL-CVE-2026-53366","DEBIAN-CVE-2026-53366","GHSA-r67c-r6r6-mj6m","ROOT-OS-DEBIAN-12-CVE-2026-53366","ROOT-OS-UBUNTU-2404-CVE-2026-53366","SUSE-SU-2026:3253-1","SUSE-SU-2026:3392-1","UBUNTU-CVE-2026-53366"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"An integer overflow in the Linux kernel IPv4 fragmentation handling can lead to memory corruption, potentially causing denial of service or code execution.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-131","name":"Incorrect Calculation of Buffer Size"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nipv4: account for fraggap on the paged allocation path\n\nIn __ip_append_data(), when the paged-allocation branch is taken,\nalloclen and pagedlen are computed as\n\n\talloclen = fragheaderlen + transhdrlen;\n\tpagedlen = datalen - transhdrlen;\n\ndatalen already includes fraggap, but the fraggap bytes carried over\nfrom the previous skb are copied into the new skb's linear area at\noffset transhdrlen by the subsequent skb_copy_and_csum_bits(). The\nlinear area is therefore undersized by fraggap bytes while pagedlen is\noverstated by the same amount.\n\nThe non-paged branch sets alloclen to fraglen, which already accounts\nfor fraggap because datalen does. Bring the paged branch in line by\nadding fraggap to alloclen and subtracting it from pagedlen.\n\nAfter this adjustment, copy no longer collapses to -fraggap on the\npaged path, so remove the stale comment describing that old arithmetic.","ecosystems":["SUSE:Linux Enterprise Live Patching 15 SP7"],"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":"ipv4: account for fraggap on the paged allocation path","id":"CVE-2026-53366","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"integer_overflow","year":"2026"},"n_packages":2,"n_references":6,"next":{"headline":"selinux: fix avdcache auditing","id":"CVE-2026-53367"},"packages":[{"ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","fixed":["2-150700.2.1"],"introduced":["0"],"last_affected":[],"package":"kernel-livepatch-SLE15-SP7-RT_Update_17","purl":"pkg:rpm/suse/kernel-livepatch-SLE15-SP7-RT_Update_17\u0026distro=SUSE%20Linux%20Enterprise%20Live%20Patching%2015%20SP7","source":"SUSE-SU-2026:3253-1"},{"ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","fixed":["2-150700.2.1"],"introduced":["0"],"last_affected":[],"package":"kernel-livepatch-SLE15-SP7_Update_18","purl":"pkg:rpm/suse/kernel-livepatch-SLE15-SP7_Update_18\u0026distro=SUSE%20Linux%20Enterprise%20Live%20Patching%2015%20SP7","source":"SUSE-SU-2026:3392-1"}],"prev":{"headline":"vsock/virtio: fix zerocopy completion for multi-skb sends","id":"CVE-2026-53365"},"products":["Linux"],"published":"2026-07-16","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":"CC BY 4.0","name":"SUSE","prefix":"SUSE"},{"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"An integer overflow in the Linux kernel IPv4 fragmentation handling can lead to memory corruption, potentially causing denial of service or code execution.","url":"https://insights.sbomify.com/CVE-2026-53366/"}