{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40032 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40032 is a vulnerability in Linux, published on 28 Oct 2025. 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-2025-40032 and fix it if it is affected.\n\nWhat it is: CVE-2025-40032 is a vulnerability in Linux, published on 28 Oct 2025. 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-2025-40032 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-2025-40032/ (Markdown: https://insights.sbomify.com/CVE-2025-40032/index.md)","id":"CVE-2025-40032","markdown":"https://insights.sbomify.com/CVE-2025-40032/index.md","name":"CVE-2025-40032","record":{"aliases":["BELL-CVE-2025-40032","DEBIAN-CVE-2025-40032","GHSA-4chp-rv27-mr56","ROOT-OS-DEBIAN-11-CVE-2025-40032","ROOT-OS-DEBIAN-12-CVE-2025-40032","ROOT-OS-DEBIAN-13-CVE-2025-40032","ROOT-OS-UBUNTU-2204-CVE-2025-40032","ROOT-OS-UBUNTU-2404-CVE-2025-40032","UBUNTU-CVE-2025-40032"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A missing NULL check in the Linux kernel PCI endpoint test driver can cause a kernel panic via NULL pointer dereference, leading to denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\nPCI: endpoint: pci-epf-test: Add NULL check for DMA channels before release\n\nThe fields dma_chan_tx and dma_chan_rx of the struct pci_epf_test can be\nNULL even after EPF initialization. Then it is prudent to check that\nthey have non-NULL values before releasing the channels. Add the checks\nin pci_epf_test_clean_dma_chan().\n\nWithout the checks, NULL pointer dereferences happen and they can lead\nto a kernel panic in some cases:\n\n  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000050\n  Call trace:\n   dma_release_channel+0x2c/0x120 (P)\n   pci_epf_test_epc_deinit+0x94/0xc0 [pci_epf_test]\n   pci_epc_deinit_notify+0x74/0xc0\n   tegra_pcie_ep_pex_rst_irq+0x250/0x5d8\n   irq_thread_fn+0x34/0xb8\n   irq_thread+0x18c/0x2e8\n   kthread+0x14c/0x210\n   ret_from_fork+0x10/0x20\n\n[mani: trimmed the stack trace]","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":"PCI: endpoint: pci-epf-test: Add NULL check for DMA channels before release","id":"CVE-2025-40032","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"remoteproc: pru: Fix potential NULL pointer dereference in pru_rproc_set_ctable()","id":"CVE-2025-40033"},"packages":[],"prev":{"headline":"tee: fix register_shm_helper()","id":"CVE-2025-40031"},"products":["Linux"],"published":"2025-10-28","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-05-11","vendors":["Linux"]},"summary":"A missing NULL check in the Linux kernel PCI endpoint test driver can cause a kernel panic via NULL pointer dereference, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2025-40032/"}