Answer in brief
CVE-2024-46823 records a High severity (CVSS 8.4) vulnerability in kunit/overflow: Fix UB in overflow_allocation_test. 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 8.4. 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 | >=d03c720e03bd9bf0b784d80b5d3ede7e2daf3b6e <d1207f07decc66546a7fa463d2f335a856c986ef || >=d03c720e03bd9bf0b784d80b5d3ede7e2daf3b6e <92e9bac18124682c4b99ede9ee3bcdd68f121e92 | d1207f07decc66546a7fa463d2f335a856c986ef, 92e9bac18124682c4b99ede9ee3bcdd68f121e92 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Sep 27, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: kunit/overflow: Fix UB in overflow_allocation_test The 'device_name' array doesn't exist out of the 'overflow_allocation_test' function scope. However, it is being used as a driver name when calling 'kunit_driver_create' from 'kunit_device_register'. It produces the kernel panic with KASAN enabled. Since this variable is used in one place only, remove it and pass the device name into kunit_device_register directly as an ascii string.
Quoted source text, attributed separately from HOL analysis.