{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80741 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80741 is a high-severity vulnerability in Linux, published on 3 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-80741 and fix it if it is affected.\n\nWhat it is: CVE-2026-80741 is a high-severity vulnerability in Linux, published on 3 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-80741 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-80741/ (Markdown: https://insights.sbomify.com/CVE-2026-80741/index.md)","id":"CVE-2026-80741","markdown":"https://insights.sbomify.com/CVE-2026-80741/index.md","name":"CVE-2026-80741","record":{"aliases":["BELL-CVE-2026-80741","DEBIAN-CVE-2026-80741","GHSA-5gj3-6gp4-j7pm","UBUNTU-CVE-2026-80741"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel DRM","requires_auth":"low_privilege","summary":"An integer underflow in the Linux kernel DRM logging allows out-of-bounds reads when processing empty messages, potentially causing crashes or information leaks.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/log: Fix out-of-bounds read on empty message length\n\ndrm_log_draw_kmsg_record() accesses s[len - 1] to strip the trailing\nnewline, but len is unsigned int. If len is 0, the subtraction wraps\nto UINT_MAX, causing an out-of-bounds read.\n\nAdd an early return when len is 0.","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/log: Fix out-of-bounds read on empty message length","id":"CVE-2026-80741","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"af_packet: Don't send zero-byte data in tpacket_snd().","id":"CVE-2026-80742"},"packages":[],"prev":{"headline":"drm/log: Fix infinite loop when scale is too large for display","id":"CVE-2026-80740"},"products":["Linux"],"published":"2026-09-03","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-09-04","vendors":["Linux"]},"summary":"An integer underflow in the Linux kernel DRM logging allows out-of-bounds reads when processing empty messages, potentially causing crashes or information leaks.","url":"https://insights.sbomify.com/CVE-2026-80741/"}