{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98615 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98615 is a denial of service vulnerability in Linux, published on 18 Oct 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-98615 and fix it if it is affected.\n\nWhat it is: CVE-2026-98615 is a denial of service vulnerability in Linux, published on 18 Oct 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-98615 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-98615/ (Markdown: https://insights.sbomify.com/CVE-2026-98615/index.md)","id":"CVE-2026-98615","markdown":"https://insights.sbomify.com/CVE-2026-98615/index.md","name":"CVE-2026-98615","record":{"aliases":["BELL-CVE-2026-98615","DEBIAN-CVE-2026-98615","GHSA-83c5-m4vx-chr4","UBUNTU-CVE-2026-98615"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A flaw in the fbnic network driver causes a denial of service during mailbox teardown due to incomplete flush operations, requiring a kernel patch.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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\neth: fbnic: Set AW_FLUSH_MODE alongside AW_FLUSH when flushing the mailbox\n\nWhen tearing down the FW mailbox Rx ring, fbnic_mbx_reset_desc_ring()\nwrites AW_CFG with FLUSH set and everything else, BME included, cleared.\nClearing BME halts the device's writes to the host but leaves the staged\nrequests parked in the PUL write pipeline rather than draining them, so\non the write path FLUSH alone never terminates the outstanding requests\nand the flush the firmware waits on never completes.\n\nAdd the FLUSH_MODE definition and set both bits so the staged writes\ndrain out of the pipeline on their own. BME stays cleared, so nothing\nlands on the host; it is restored later in fbnic_mbx_init_desc_ring()\nwhen the ring is rebuilt, once the outstanding writes are gone.\n\nThe read path is unaffected. AR_CFG has no equivalent mode bit and\nAR_FLUSH terminates the outstanding reads by itself, so it is left as\nis.\n\nBoth writes remain plain stores rather than read-modify-writes. That is\ndeliberate: the matching write in fbnic_mbx_init_desc_ring() restores\nBME and the TLP attributes, and clears both flush bits as a side effect.","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":"eth: fbnic: Set AW_FLUSH_MODE alongside AW_FLUSH when flushing the mailbox","id":"CVE-2026-98615","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"eth: fbnic: reset num_napi when the napi vectors are freed","id":"CVE-2026-98616"},"packages":[],"prev":{"headline":"sctp: avoid livelock while updating retransmit path","id":"CVE-2026-98614"},"products":["Linux"],"published":"2026-10-18","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 flaw in the fbnic network driver causes a denial of service during mailbox teardown due to incomplete flush operations, requiring a kernel patch.","url":"https://insights.sbomify.com/CVE-2026-98615/"}