{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97614 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97614 is a memory corruption vulnerability in Linux, published on 25 Sep 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-97614 and fix it if it is affected.\n\nWhat it is: CVE-2026-97614 is a memory corruption vulnerability in Linux, published on 25 Sep 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-97614 in the wild and no public exploit code.\n\nAffected product: Linux. 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-97614/ (Markdown: https://insights.sbomify.com/CVE-2026-97614/index.md)","id":"CVE-2026-97614","markdown":"https://insights.sbomify.com/CVE-2026-97614/index.md","name":"CVE-2026-97614","record":{"aliases":["BELL-CVE-2026-97614","DEBIAN-CVE-2026-97614","GHSA-3px2-442r-8h6r","UBUNTU-CVE-2026-97614"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel DSA","requires_auth":"low_privilege","summary":"A local attacker can trigger a slab-out-of-bounds read in the Linux kernel's Broadcom DSA tagger, potentially causing a crash or leaking memory.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: dsa: tag_brcm: legacy FCS: request needed tailroom\n\nThe legacy FCS tagger calculates the CRC over skb-\u003elen bytes starting at\nskb-\u003edata. When a nonlinear skb reaches the tagger, this reads past the\nlinear head into unrelated slab memory.\n\nThe tagger appends an Ethernet FCS but does not declare that tailroom. As a\nresult, DSA leaves NETIF_F_SG and NETIF_F_FRAGLIST enabled on the user\nport, and nonlinear skbs can reach the CRC calculation.\n\nDeclare the required tailroom. DSA will then clear those features and the\nnetworking core will linearize skbs before the tagger runs.\n\nA KASAN-enabled dsa_loop test using this tagger reports:\n\n  BUG: KASAN: slab-out-of-bounds in crc32_le\n  Read of size 1 at addr ffff8880397086c0 by task exp/135\n\n  Call Trace:\n   crc32_le (lib/crc/crc32-main.c:38)\n   brcm_leg_fcs_tag_xmit (net/dsa/tag_brcm.c:343)\n   dsa_user_xmit (net/dsa/user.c:942)\n   dev_hard_start_xmit (net/core/dev.c:3937)\n   __dev_queue_xmit (net/core/dev.c:4926)\n   packet_sendmsg (net/packet/af_packet.c:3110)\n   __sys_sendto (net/socket.c:2281)\n\n  The buggy address belongs to the object at ffff888039708400\n   which belongs to the cache skbuff_small_head of size 704\n  The buggy address is located 0 bytes to the right of\n   allocated 704-byte region [ffff888039708400, ffff8880397086c0)","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":"net: dsa: tag_brcm: legacy FCS: request needed tailroom","id":"CVE-2026-97614","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"net: bridge: use option bits for CFM/MRP frame handlers","id":"CVE-2026-97615"},"packages":[],"prev":{"headline":"net: mana: Reserve extra CQ slot for the fence completion CQE","id":"CVE-2026-97613"},"products":["Linux"],"published":"2026-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker can trigger a slab-out-of-bounds read in the Linux kernel's Broadcom DSA tagger, potentially causing a crash or leaking memory.","url":"https://insights.sbomify.com/CVE-2026-97614/"}