{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99004 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99004 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99004 and fix it if it is affected.\n\nWhat it is: CVE-2026-99004 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99004 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-99004/ (Markdown: https://insights.sbomify.com/CVE-2026-99004/index.md)","id":"CVE-2026-99004","markdown":"https://insights.sbomify.com/CVE-2026-99004/index.md","name":"CVE-2026-99004","record":{"aliases":["BELL-CVE-2026-99004","DEBIAN-CVE-2026-99004","GHSA-862j-6x74-2p6m","UBUNTU-CVE-2026-99004"],"analysis":null,"analysis_generated_by":null,"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\ndrm/imagination: Size page table preallocation by device address\n\nCommit 0a8224058a58 (\"drm/imagination: Fix page count for page table for\nmap() interface\") passed the device address to\npvr_mmu_op_context_create(), but the preallocation is still sized from\ndevice_addr + sgt_offset with an exclusive end. The offset into the\nobject's pages has no place in a device-virtual range, and the exclusive\nend allocates one table too many when the range ends on a table\nboundary.\n\nCount the tables from device_addr and the inclusive end of the range.\n\nThe new calculation does not take page table indices into account. This\nfixes another issue with the previous implementation, where the\ndifference between start and end indices could underflow when a mapping\ncrossed a page table boundary. This would lead to the driver\npreallocating a huge number of MMU pages, exhausting system memory and\ntriggering an out of memory panic.\n\n[Alessio: add paragraph to point out OOM bug being fixed, cc stable]","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":"drm/imagination: Size page table preallocation by device address","id":"CVE-2026-99004","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"drm/i915/gt: Unmask interrupts only when ACTIVE is true","id":"CVE-2026-99005"},"packages":[],"prev":{"headline":"drm/panthor: validate userspace queue count against initialized firmware slot count","id":"CVE-2026-99003"},"products":["Linux"],"published":"2026-10-23","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-23","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-99004/"}