{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-63929 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-63929 is a memory corruption vulnerability in Linux, published on 19 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-63929 and fix it if it is affected.\n\nWhat it is: CVE-2026-63929 is a memory corruption vulnerability in Linux, published on 19 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-63929 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-63929/ (Markdown: https://insights.sbomify.com/CVE-2026-63929/index.md)","id":"CVE-2026-63929","markdown":"https://insights.sbomify.com/CVE-2026-63929/index.md","name":"CVE-2026-63929","record":{"aliases":["BELL-CVE-2026-63929","DEBIAN-CVE-2026-63929","GHSA-7xv7-rch9-q9hw","UBUNTU-CVE-2026-63929"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel IIO","requires_auth":"low_privilege","summary":"A memory leak in the Linux kernel IIO buffer subsystem allows local attackers to exhaust kernel memory, causing denial of service.","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\niio: buffer: Fix DMA fence leak in iio_buffer_enqueue_dmabuf()\n\niio_buffer_enqueue_dmabuf() allocates a struct iio_dma_fence (104 bytes,\nkmalloc-128) via kmalloc_obj()+dma_fence_init(), which sets the initial\nkref to 1.  It then calls dma_resv_add_fence() which takes a second\nreference (kref=2), and stores a raw pointer in block-\u003efence.\n\nOn the success path the function returns without calling dma_fence_put()\nto release the initial reference, so every buffer enqueue permanently\nleaks one kmalloc-128 allocation.\n\nThe iio_buffer_cleanup() work item only releases the temporary reference\ntaken during completion signalling by iio_buffer_signal_dmabuf_done();\nthe initial reference from dma_fence_init() is never released.\n\nWith four iio_rwdev instances at 240kHz and 512 samples per buffer,\nthis produces ~1875 kmalloc-128 allocations per second matching the\nobserved slab growth exactly. A test with ftrace confirmed that the\ndma_fence_destroy event was never triggered.\n\nFix by calling dma_fence_put() after dma_resv_add_fence(), transferring\nownership of the fence to the DMA reservation object. The DMA fence then\ngets properly discarded after being signalled.","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":"iio: buffer: Fix DMA fence leak in iio_buffer_enqueue_dmabuf()","id":"CVE-2026-63929","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"iio: buffer: hw-consumer: fix use-after-free in error path","id":"CVE-2026-63930"},"packages":[],"prev":{"headline":"USB: serial: omninet: fix memory corruption with small endpoint","id":"CVE-2026-63928"},"products":["Linux"],"published":"2026-07-19","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-07-19","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel IIO buffer subsystem allows local attackers to exhaust kernel memory, causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-63929/"}