{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40304 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40304 is a high-severity memory corruption vulnerability in Linux, published on 8 Dec 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-40304 and fix it if it is affected.\n\nWhat it is: CVE-2025-40304 is a high-severity memory corruption vulnerability in Linux, published on 8 Dec 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-40304 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-40304/ (Markdown: https://insights.sbomify.com/CVE-2025-40304/index.md)","id":"CVE-2025-40304","markdown":"https://insights.sbomify.com/CVE-2025-40304/index.md","name":"CVE-2025-40304","record":{"aliases":["BELL-CVE-2025-40304","DEBIAN-CVE-2025-40304","GHSA-6cgq-9674-3xfg","ROOT-OS-DEBIAN-12-CVE-2025-40304","ROOT-OS-DEBIAN-13-CVE-2025-40304","ROOT-OS-UBUNTU-2204-CVE-2025-40304","ROOT-OS-UBUNTU-2404-CVE-2025-40304","UBUNTU-CVE-2025-40304"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A missing bounds check in the Linux kernel framebuffer driver allows out-of-bounds writes, potentially causing crashes or code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds\n\nAdd bounds checking to prevent writes past framebuffer boundaries when\nrendering text near screen edges. Return early if the Y position is off-screen\nand clip image height to screen boundary. Break from the rendering loop if the\nX position is off-screen. When clipping image width to fit the screen, update\nthe character count to match the clipped width to prevent buffer size\nmismatches.\n\nWithout the character count update, bit_putcs_aligned and bit_putcs_unaligned\nreceive mismatched parameters where the buffer is allocated for the clipped\nwidth but cnt reflects the original larger count, causing out-of-bounds writes.","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":"fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds","id":"CVE-2025-40304","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":8,"next":{"headline":"9p/trans_fd: p9_fd_request: kick rx thread if EPOLLIN","id":"CVE-2025-40305"},"packages":[],"prev":{"headline":"btrfs: ensure no dirty metadata is written back for an fs with errors","id":"CVE-2025-40303"},"products":["Linux"],"published":"2025-12-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-05","vendors":["Linux"]},"summary":"A missing bounds check in the Linux kernel framebuffer driver allows out-of-bounds writes, potentially causing crashes or code execution.","url":"https://insights.sbomify.com/CVE-2025-40304/"}