{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97952 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97952 is a denial of service 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-97952 and fix it if it is affected.\n\nWhat it is: CVE-2026-97952 is a denial of service 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-97952 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-97952/ (Markdown: https://insights.sbomify.com/CVE-2026-97952/index.md)","id":"CVE-2026-97952","markdown":"https://insights.sbomify.com/CVE-2026-97952/index.md","name":"CVE-2026-97952","record":{"aliases":["AZL-104163","BELL-CVE-2026-97952","DEBIAN-CVE-2026-97952","GHSA-gjc3-h94h-x64h","UBUNTU-CVE-2026-97952"],"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 resource leak in the Linux kernel sunvdc driver allows attackers to exhaust map table entries, causing permanent disk failure and denial of service.","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\nsunvdc: unmap LDC cookies when the descriptor send fails\n\n__send_request() maps the request's pages into the LDC channel's map\ntable (ldc_map_sg()), fills in the descriptor and marks it\nVIO_DESC_READY before ringing the doorbell via __vdc_tx_trigger().\nWhen the trigger fails, the error path only prints a message: the\ndescriptor stays READY and the cookies are never unmapped. The\nmapping is normally released in vdc_end_one() when the peer completes\nthe descriptor - but a descriptor whose doorbell was never sent will\nnever complete, and since dr-\u003eprod is not advanced on failure, the\nreset path (vdc_requeue_inflight(), which walks [cons, prod)) never\nvisits it either. The map table entries are leaked permanently.\n\nSince commit a11f6ca9aef9 (\"sunvdc: Do not spin in an infinite loop\nwhen vio_ldc_send() returns EAGAIN\") trigger failures occur in\npractice under load, so every resulting I/O error also leaks one\nrequest's worth of entries from the fixed-size (8192 entries per\nchannel) map table. Because the allocator hands out contiguous\nranges, fragmentation makes large multi-segment requests fail first\nas the table drains, until ldc_map_sg() fails permanently and the\ndisk is dead until reboot.\n\nIt also makes any retry-based recovery unusable: requeuing the\nrequest on -EAGAIN remaps the pages on every attempt, overwriting\ndesc-\u003ecookies and orphaning the previous mapping, so the table\ndrains at the retry rate. This is the memory exhaustion observed\nwhen the requeue approach was first tested in October 2025.\n\nRoll back on failure: unmap the cookies, mark the descriptor FREE\nagain and clear the request entry. If the trigger failed with\n-ENOTCONN, __vdc_tx_trigger() has already reset the port, which\ntears down and reallocates both the dring and the LDC channel\nincluding its map table - nothing to roll back, and the stale\ndescriptor must not be touched.","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":"sunvdc: unmap LDC cookies when the descriptor send fails","id":"CVE-2026-97952","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"net: stmmac: fix TX descriptor availability check for TSO traffic","id":"CVE-2026-97953"},"packages":[],"prev":{"headline":"scsi: target: iscsi: Fix hang for aborted WRITE_PENDING commands","id":"CVE-2026-97951"},"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 resource leak in the Linux kernel sunvdc driver allows attackers to exhaust map table entries, causing permanent disk failure and denial of service.","url":"https://insights.sbomify.com/CVE-2026-97952/"}