Answer in brief
CVE-2026-80749 records a High severity (CVSS 7.1) vulnerability in drm/connector/hdmi: Fix out of bounds memory read. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f378b77227bc4732922c57f92be89438bb1018a1 <d9f7454c185c0c7f0973e11d62ad6c06862c324c || >=f378b77227bc4732922c57f92be89438bb1018a1 <e5b527804a1ea4f70e139179d3062cf5de8c06ab || >=f378b77227bc4732922c57f92be89438bb1018a1 <f72bb95732bc5ca87b50c52c8f087ba501950809 || >=f378b77227bc4732922c57f92be89438bb1018a1 <9ecf8ba763d0ffe0673538eb4bf7806f20455d19 | d9f7454c185c0c7f0973e11d62ad6c06862c324c, e5b527804a1ea4f70e139179d3062cf5de8c06ab, f72bb95732bc5ca87b50c52c8f087ba501950809, 9ecf8ba763d0ffe0673538eb4bf7806f20455d19 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Sep 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 3, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/connector/hdmi: Fix out of bounds memory read A helper function was copying a given audio infoframe into the connector's copy but using the size of the destination (a generic target, sized to accept many different data blocks) not the source (a very specific type of data block). Thus, it was copying 60 bytes of data from a 28 byte allocation. Fix that by using the source size instead, together with a build bug on the source size actually being smaller than the destination. I hit this running KUnit tests under KASAN (while debugging something else entirely). In the real world, it seems unlikely to cause an actual problem. It is a read not a write so it can't corrupt any memory. However, it could potentially fall off the end of a page and cause an accvio bug.
Quoted source text, attributed separately from HOL analysis.