{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72046 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72046 is a critical vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-72046 and fix it if it is affected.\n\nWhat it is: CVE-2026-72046 is a critical vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-72046 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-72046/ (Markdown: https://insights.sbomify.com/CVE-2026-72046/index.md)","id":"CVE-2026-72046","markdown":"https://insights.sbomify.com/CVE-2026-72046/index.md","name":"CVE-2026-72046","record":{"aliases":["BELL-CVE-2026-72046","DEBIAN-CVE-2026-72046","GHSA-9vwj-6q4v-p5m2","UBUNTU-CVE-2026-72046"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A race condition in the gve driver causes header buffer corruption when HW-GRO is enabled, leading to data misinterpretation and potential information disclosure.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ngve: fix header buffer corruption with header-split and HW-GRO\n\nThe DQO RX datapath programs a per-buffer-queue-descriptor\nheader_buf_addr at post time and reads the split header back at\ncompletion time. Both the post and the read currently index the\nheader buffer by queue position rather than by the buffer's identity:\n\n  - post (gve_rx_post_buffers_dqo): header_buf_addr is computed from\n    bufq-\u003etail\n  - read (gve_rx_dqo): the header is read from desc_idx (the completion\n    queue head index)\n\nThis relies on the buffer-queue index and the completion-queue index\nbeing equal for the start of every packet, i.e. on the device consuming\nposted buffers and returning completions in the exact same order. That\nassumption does not hold once HW-GRO is enabled with multiple\nflows: coalesced segments are accepted and completed in an order that\nmay differ from the order buffers were posted, and segments from\ndifferent flows may interleave.\n\nThat results in two problems:\n\n1. Wrong header slot on read. Because the read offset is derived from\n   the completion index (desc_idx) while the device wrote the header to\n   the address programmed for the buffer's buf_id, the driver can copy\n   a header belonging to a different packet. This shows up as\n   throughput drop (about 30% drop and large numbers of TCP\n   retransmissions) with header-split and HW-GRO both enabled and many\n   streams.\n\n2. Header buffer reused while still owned by the device. The driver\n   advances bufq-\u003ehead by one per completion and re-posts buffers based\n   on that. Arrival of N RX completions only guarantees that at least N\n   RX buffer descriptors have been read by the device. It does not\n   guarantee that the device has relinquished the ownership of all the\n   buffers corresponding to those N descriptors. With out-of-order\n   completions (e.g. the completion for a packet copied into buffer N\n   arrives before the completion for a packet copied into buffer N-1),\n   the driver can re-post and overwrite a header buffer that the device\n   is still going to write into, corrupting the header of a packet\n   whose completion has not yet been processed.\n\nFix both issues by indexing the header buffer by buf_id on both the post\nand read paths. Reading from buf_id's slot is therefore always correct\nregardless of completion ordering (fixes problem 1).\n\nIndexing by buf_id also ties each header slot to the lifetime of its\nbuffer state. A buffer state is only returned to the free/recycle lists\nwhen its own completion (buf_id) is processed, so its header slot can\nonly be re-posted after the device is done with it. This makes header\nslot reuse safe under out-of-order completions (fixes problem 2).\n\nAllocate (gve_rx_alloc_hdr_bufs) and free (gve_rx_free_hdr_bufs) the\nheader buffers based on num_buf_states to match the buf_id indexing.","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":"gve: fix header buffer corruption with header-split and HW-GRO","id":"CVE-2026-72046","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"ieee802154: ca8210: fix pointer truncation in kfifo on 64-bit","id":"CVE-2026-72047"},"packages":[],"prev":{"headline":"octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF","id":"CVE-2026-72045"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A race condition in the gve driver causes header buffer corruption when HW-GRO is enabled, leading to data misinterpretation and potential information disclosure.","url":"https://insights.sbomify.com/CVE-2026-72046/"}