Answer in brief
CVE-2026-46088 records a Medium severity (CVSS 5.5) vulnerability in ALSA: control: Validate buf_len before strnlen() in snd_ctl_elem_init_enum_names(). 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.
Answer in brief
CVE-2026-46088 records a Medium severity (CVSS 5.5) vulnerability in ALSA: control: Validate buf_len before strnlen() in snd_ctl_elem_init_enum_names(). 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 5.5. 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 | >=8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 <708f6ec9bcdf58bfd561409110baaf4fd3be4ea3 || >=8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 <bfcbb4994da9e979c4bcfcf24aaaac69e457e48e || >=8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 <a470f7cabc4df72d9bd132f5719a8717292bb440 || >=8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 <1fbe46d2b72754d8bd580e13e59ccb5d3d0e8cb0 || >=8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 <8ba0214c3dd32b8ec652947e3f2bc5b8f6e6be9e || >=8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 <654c818a69c21d2bea4e8fd9eae7da865df9a5c8 || >=8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 <82012fd3e78a14360fbc2f1a7491589896704f97 || >=8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 <e0da8a8cac74f4b9f577979d131f0d2b88a84487 | 708f6ec9bcdf58bfd561409110baaf4fd3be4ea3, bfcbb4994da9e979c4bcfcf24aaaac69e457e48e, a470f7cabc4df72d9bd132f5719a8717292bb440, 1fbe46d2b72754d8bd580e13e59ccb5d3d0e8cb0, 8ba0214c3dd32b8ec652947e3f2bc5b8f6e6be9e, 654c818a69c21d2bea4e8fd9eae7da865df9a5c8, 82012fd3e78a14360fbc2f1a7491589896704f97, e0da8a8cac74f4b9f577979d131f0d2b88a84487 |
| Linux/Linuxgeneric | 3.2 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
In the Linux kernel, the following vulnerability has been resolved: ALSA: control: Validate buf_len before strnlen() in snd_ctl_elem_init_enum_names() snd_ctl_elem_init_enum_names() advances pointer p through the names buffer while decrementing buf_len. If buf_len reaches zero but items remain, the next iteration calls strnlen(p, 0). While strnlen(p, 0) returns 0 and would hit the existing name_len == 0 error path, CONFIG_FORTIFY_SOURCE's fortified strnlen() first checks maxlen against __builtin_dynamic_object_size(). When Clang loses track of p's object size inside the loop, this triggers a BRK exception panic before the return value is examined. Add a buf_len == 0 guard at the loop entry to prevent calling fortified strnlen() on an exhausted buffer. Found by kernel fuzz testing through Xiaomi Smartphone.
Quoted source text, attributed separately from HOL analysis.
CVSS is 5.5. 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 | >=8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 <708f6ec9bcdf58bfd561409110baaf4fd3be4ea3 || >=8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 <bfcbb4994da9e979c4bcfcf24aaaac69e457e48e || >=8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 <a470f7cabc4df72d9bd132f5719a8717292bb440 || >=8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 <1fbe46d2b72754d8bd580e13e59ccb5d3d0e8cb0 || >=8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 <8ba0214c3dd32b8ec652947e3f2bc5b8f6e6be9e || >=8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 <654c818a69c21d2bea4e8fd9eae7da865df9a5c8 || >=8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 <82012fd3e78a14360fbc2f1a7491589896704f97 || >=8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 <e0da8a8cac74f4b9f577979d131f0d2b88a84487 | 708f6ec9bcdf58bfd561409110baaf4fd3be4ea3, bfcbb4994da9e979c4bcfcf24aaaac69e457e48e, a470f7cabc4df72d9bd132f5719a8717292bb440, 1fbe46d2b72754d8bd580e13e59ccb5d3d0e8cb0, 8ba0214c3dd32b8ec652947e3f2bc5b8f6e6be9e, 654c818a69c21d2bea4e8fd9eae7da865df9a5c8, 82012fd3e78a14360fbc2f1a7491589896704f97, e0da8a8cac74f4b9f577979d131f0d2b88a84487 |
| Linux/Linuxgeneric | 3.2 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
In the Linux kernel, the following vulnerability has been resolved: ALSA: control: Validate buf_len before strnlen() in snd_ctl_elem_init_enum_names() snd_ctl_elem_init_enum_names() advances pointer p through the names buffer while decrementing buf_len. If buf_len reaches zero but items remain, the next iteration calls strnlen(p, 0). While strnlen(p, 0) returns 0 and would hit the existing name_len == 0 error path, CONFIG_FORTIFY_SOURCE's fortified strnlen() first checks maxlen against __builtin_dynamic_object_size(). When Clang loses track of p's object size inside the loop, this triggers a BRK exception panic before the return value is examined. Add a buf_len == 0 guard at the loop entry to prevent calling fortified strnlen() on an exhausted buffer. Found by kernel fuzz testing through Xiaomi Smartphone.
Quoted source text, attributed separately from HOL analysis.