Cologne Firmware
by Qualcomm
CVEs (67)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2026-21378 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory Corruption when accessing an output buffer without validating its size during IOCTL processing in a camera sensor driver. | ||
| CVE-2026-21376 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory Corruption when accessing an output buffer without validating its size during IOCTL processing in a camera sensor driver. | ||
| CVE-2026-21375 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory Corruption when accessing an output buffer without validating its size during IOCTL processing. | ||
| CVE-2026-21374 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory Corruption when processing auxiliary sensor input/output control commands with insufficient buffer size validation. | ||
| CVE-2026-21373 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory Corruption when accessing an output buffer without validating its size during IOCTL processing. | ||
| CVE-2026-21372 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory Corruption when sending IOCTL requests with invalid buffer sizes during memcpy operations. | ||
| CVE-2026-21371 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory Corruption when retrieving output buffer with insufficient size validation. | ||
| CVE-2025-47390 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory corruption while preprocessing IOCTL request in JPEG driver. | ||
| CVE-2025-47389 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory corruption when buffer copy operation fails due to integer overflow during attestation report generation. | ||
| CVE-2025-59603 | Hig | 0.51 | 7.8 | 0.00 | Mar 2, 2026 | Memory Corruption when processing invalid user address with nonstandard buffer address. | ||
| CVE-2025-47373 | Hig | 0.51 | 7.8 | 0.00 | Mar 2, 2026 | Memory Corruption when accessing buffers with invalid length during TA invocation. | ||
| CVE-2025-47399 | Hig | 0.51 | 7.8 | 0.00 | Feb 2, 2026 | Memory Corruption while processing IOCTL call to update sensor property settings with invalid input parameters. | ||
| CVE-2025-47356 | Hig | 0.51 | 7.8 | 0.00 | Jan 7, 2026 | Memory Corruption when multiple threads concurrently access and modify shared resources. | ||
| CVE-2025-47343 | Hig | 0.51 | 7.8 | 0.00 | Jan 7, 2026 | Memory corruption while processing a video session to set video parameters. | ||
| CVE-2026-25275 | Hig | 0.49 | 7.5 | 0.00 | Sep 17, 2026 | Transient DOS when processing authentication frames with invalid FILS information element header lengths. | ||
| CVE-2026-21381 | Hig | 0.49 | 7.6 | 0.00 | Apr 6, 2026 | Transient DOS when receiving a service data frame with excessive length during device matching over a neighborhood awareness network protocol connection. | ||
| CVE-2026-21367 | Hig | 0.49 | 7.6 | 0.00 | Apr 6, 2026 | Transient DOS when processing nonstandard FILS Discovery Frames with out-of-range action sizes during initial scans. | ||
| CVE-2026-25294 | Hig | 0.48 | 7.4 | 0.00 | Sep 17, 2026 | Transient DOS while parsing frame during channel usage. | ||
| CVE-2026-25281 | Hig | 0.48 | 7.4 | 0.00 | Sep 17, 2026 | Transient DOS when processing large or numerous request buffers without sufficient memory allocation validation. | ||
| CVE-2026-24081 | Hig | 0.48 | 7.4 | 0.00 | Sep 17, 2026 | Transient DOS when processing a channel map with insufficient used channels and adaptive frequency hopping is fully enabled. |
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when accessing an output buffer without validating its size during IOCTL processing in a camera sensor driver.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when accessing an output buffer without validating its size during IOCTL processing in a camera sensor driver.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when accessing an output buffer without validating its size during IOCTL processing.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when processing auxiliary sensor input/output control commands with insufficient buffer size validation.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when accessing an output buffer without validating its size during IOCTL processing.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when sending IOCTL requests with invalid buffer sizes during memcpy operations.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when retrieving output buffer with insufficient size validation.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while preprocessing IOCTL request in JPEG driver.
- risk 0.51cvss 7.8epss 0.00
Memory corruption when buffer copy operation fails due to integer overflow during attestation report generation.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when processing invalid user address with nonstandard buffer address.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when accessing buffers with invalid length during TA invocation.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption while processing IOCTL call to update sensor property settings with invalid input parameters.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when multiple threads concurrently access and modify shared resources.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while processing a video session to set video parameters.
- risk 0.49cvss 7.5epss 0.00
Transient DOS when processing authentication frames with invalid FILS information element header lengths.
- risk 0.49cvss 7.6epss 0.00
Transient DOS when receiving a service data frame with excessive length during device matching over a neighborhood awareness network protocol connection.
- risk 0.49cvss 7.6epss 0.00
Transient DOS when processing nonstandard FILS Discovery Frames with out-of-range action sizes during initial scans.
- risk 0.48cvss 7.4epss 0.00
Transient DOS while parsing frame during channel usage.
- risk 0.48cvss 7.4epss 0.00
Transient DOS when processing large or numerous request buffers without sufficient memory allocation validation.
- risk 0.48cvss 7.4epss 0.00
Transient DOS when processing a channel map with insufficient used channels and adaptive frequency hopping is fully enabled.
Page 2 of 4