Answer in brief
CVE-2026-46281 records a High severity (CVSS 7.8) vulnerability in vmalloc: fix buffer overflow in vrealloc_node_align(). 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.8. 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 | >=4c5d3365882dbbc0784688784904f440d7a4c0f1 <e9b057a44deff4c59c13f44672a5cc74dcd57522 || >=4c5d3365882dbbc0784688784904f440d7a4c0f1 <b281adf71f786c325eb6d6d1582d4d05313438a8 || >=4c5d3365882dbbc0784688784904f440d7a4c0f1 <82d1f01292d3f09bf063f829f8ab8de12b4280a1 | e9b057a44deff4c59c13f44672a5cc74dcd57522, b281adf71f786c325eb6d6d1582d4d05313438a8, 82d1f01292d3f09bf063f829f8ab8de12b4280a1 |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
Jun 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 7, 2026
In the Linux kernel, the following vulnerability has been resolved: vmalloc: fix buffer overflow in vrealloc_node_align() Commit 4c5d3365882d ("mm/vmalloc: allow to set node and align in vrealloc") added the ability to force a new allocation if the current pointer is on the wrong NUMA node, or if an alignment constraint is not met, even if the user is shrinking the allocation. On this path (need_realloc), the code allocates a new object of 'size' bytes and then memcpy()s 'old_size' bytes into it. If the request is to shrink the object (size < old_size), this results in an out-of-bounds write on the new buffer. Fix this by bounding the copy length by the new allocation size.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-46281 records a High severity (CVSS 7.8) vulnerability in vmalloc: fix buffer overflow in vrealloc_node_align(). 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.8. 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 | >=4c5d3365882dbbc0784688784904f440d7a4c0f1 <e9b057a44deff4c59c13f44672a5cc74dcd57522 || >=4c5d3365882dbbc0784688784904f440d7a4c0f1 <b281adf71f786c325eb6d6d1582d4d05313438a8 || >=4c5d3365882dbbc0784688784904f440d7a4c0f1 <82d1f01292d3f09bf063f829f8ab8de12b4280a1 | e9b057a44deff4c59c13f44672a5cc74dcd57522, b281adf71f786c325eb6d6d1582d4d05313438a8, 82d1f01292d3f09bf063f829f8ab8de12b4280a1 |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
Jun 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 7, 2026
In the Linux kernel, the following vulnerability has been resolved: vmalloc: fix buffer overflow in vrealloc_node_align() Commit 4c5d3365882d ("mm/vmalloc: allow to set node and align in vrealloc") added the ability to force a new allocation if the current pointer is on the wrong NUMA node, or if an alignment constraint is not met, even if the user is shrinking the allocation. On this path (need_realloc), the code allocates a new object of 'size' bytes and then memcpy()s 'old_size' bytes into it. If the request is to shrink the object (size < old_size), this results in an out-of-bounds write on the new buffer. Fix this by bounding the copy length by the new allocation size.
Quoted source text, attributed separately from HOL analysis.