Automotive Vulnerabilities. Hunted worldwide every 24 hours, across 🇺🇸🇨🇳🇯🇵🇰🇷🇹🇼🇩🇪🇫🇷🇨🇭🇦🇹🇳🇱🇧🇪🇵🇱🇨🇦🇱🇺🇪🇺. Stay ahead.
A heap-based buffer overflow in the RDP protocol dissector of Wireshark versions 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 can cause a denial of service by crashing the application. This could be relevant where Wireshark is deployed in automotive systems for network analysis or diagnostics, but the advisory does not confirm automotive use. Confirm applicability through the product SBOM or dependency inventory.
A heap-based buffer overflow in the Wireshark dissection engine, affecting versions 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18, could allow an attacker to crash the application, resulting in a denial of service. This could be relevant where Wireshark is deployed in automotive systems for network analysis or diagnostics, but the advisory does not confirm automotive use. Confirm applicability through the product SBOM or dependency inventory.
Wireshark versions 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 contain a buffer over-read vulnerability in the ERF file parser, which can cause a crash and lead to a denial of service when processing a malicious file. This could be relevant where Wireshark is deployed in automotive systems for network analysis or diagnostics, but the advisory does not confirm automotive use. Confirm applicability through the product SBOM or dependency inventory.
Zephyr is the real-time operating system deployed in vehicle ECUs, ADAS controllers, and body control modules. This vulnerability allows an attacker with local shell access to corrupt a stored crash dump file, causing an out-of-bounds memory read that could crash the system or leak sensitive device memory contents to the user. The issue is rated as moderate severity because it requires local access and cannot be triggered remotely, but it has been fixed in the latest version.
Samsung Exynos 1280 firmware contains a TOCTOU race condition in the Exynos DRM HDR Driver that can lead to a heap overflow and a kernel crash. An attacker who can trigger the race condition could crash the kernel, though the advisory does not state a severity rating. This could be relevant where Exynos 1280 processors are deployed in automotive systems; confirm applicability through the product SBOM or dependency inventory.
Samsung Exynos mobile processors (models 1330, 1380, 1480, 2400, 1580, 2500, 2600, and 1680) contain a flaw in the camera driver where sensitive information is written into debugging code, causing an information leak. An attacker could potentially exploit this to obtain sensitive data handled by the camera driver. The advisory does not state a severity rating. This could be relevant where these Exynos processors are deployed in automotive systems. Confirm applicability through the product SBOM or dependency inventory.
A vulnerability exists in the popt library, a component used for parsing command-line options. An attacker could exploit this flaw by providing specially crafted configuration content, which, when loaded, leads to a small memory corruption issue that could cause the affected process to crash or become unavailable. This could be relevant where popt is deployed in automotive systems, such as in embedded Linux environments for infotainment or control units, but the advisory does not confirm automotive use. Confirm applicability through the product SBOM or dependency inventory.
This vulnerability affects the real-time operating system Zephyr, which is deployed in vehicle ECUs, ADAS controllers, and body control modules, specifically in its firmware-update management subsystem. An attacker with local access could exploit a race condition to corrupt the update subsystem’s internal state, potentially causing a denial of service that blocks critical over-the-air firmware updates, though the issue is contained within the system and does not allow remote exploitation or code execution. The severity is moderate, requiring local access and precise timing, but it could disrupt essential vehicle maintenance and security patching if triggered.
A flaw in the Linux kernel's UDF filesystem causes a spurious warning when an I/O error occurs while writing the Logical Volume Integrity Descriptor buffer and the filesystem is later remounted read-write or synced. The fix marks the buffer as uptodate before marking it dirty, preventing the warning; the advisory describes this as a warning rather than a data-corruption or privilege-escalation issue. This could be relevant where the Linux kernel with UDF support is deployed in automotive systems; confirm applicability through the product SBOM or dependency inventory.
The Linux kernel's host1x debug output helpers could read past the end of a 256-byte buffer when a formatted debug string was longer than that, because the code used the unbounded length returned by vsnprintf() rather than the number of bytes actually written. This only affected the debugfs files, since the printk debug sink ignores the byte count, and the advisory states the issue is very unlikely to occur in practice. This could be relevant where the host1x driver is deployed in automotive systems, for example in NVIDIA Tegra-based platforms; confirm applicability through the product SBOM or dependency inventory.
The Linux kernel's zram compressed-memory driver has a flaw where destroying its compressor state can leave the primary compressor set to NULL, an invalid state that may cause a crash when the compressor name is later read. An attacker able to trigger this condition could cause a NULL-pointer dereference, though the advisory rates the risk as low. This could be relevant where the Linux kernel's zram driver is deployed in automotive systems; confirm applicability through the product SBOM or dependency inventory.
The advisory describes the removal of the erofs fscache backend from the Linux kernel, which is a code change rather than a vulnerability with a stated severity or attacker impact. The affected component is the erofs filesystem's fscache support, and the technical impact is the elimination of this backend functionality. This could be relevant where erofs is deployed in automotive systems, as it is a filesystem used in some embedded contexts, but the advisory does not confirm any automotive connection or describe a specific security threat. Confirm applicability through the product SBOM or dependency inventory.
The advisory addresses a bug in the Linux kernel's NTB (Non-Transparent Bridge) driver, where the DMA address was incorrectly modified before being released, violating the DMA API requirement that the exact original address be used for freeing. An attacker could potentially exploit this memory management error to cause system instability or a denial of service. The severity is not explicitly stated, but the fix is a kernel bug correction. This could be relevant where the Linux kernel with NTB support is deployed in automotive systems, such as for high-speed interconnects between processors. Confirm applicability through the product SBOM or dependency inventory.
The advisory addresses a bug in the Linux kernel's Tegra cryptographic driver, where a failure to allocate memory for an input buffer in the CCM (counter with cipher block chaining message authentication code) operation was not correctly reported as an out-of-memory error. An attacker could potentially exploit this incorrect error handling to cause unexpected behavior, such as a denial of service, in systems using this driver. The affected component is a software driver for Tegra system-on-chip hardware, which is not confirmed to be in automotive products by the advisory, but this could be relevant where Tegra-based hardware is deployed in automotive systems. Confirm applicability through the product SBOM or dependency inventory.
The advisory describes a fix in the Linux kernel for a memory leak in the AFS (Andrew File System) volume lookup function, where a reference to a dying volume is not properly released. An attacker could potentially exploit this to cause memory exhaustion or system instability, though the advisory does not state a specific severity rating. This could be relevant where the Linux kernel is deployed in automotive systems, such as in infotainment or control units, but the advisory does not confirm any automotive use. Confirm applicability through the product SBOM or dependency inventory.
The advisory describes a memory leak vulnerability in the Linux kernel's AFS (Andrew File System) client, specifically in the function that updates a cell's server list. An attacker could potentially exploit this to exhaust system memory, though the advisory does not state a severity rating. This could be relevant where the Linux kernel is deployed in automotive systems, such as in infotainment or telematics units, but the advisory does not confirm any automotive impact. Confirm applicability through the product SBOM or dependency inventory.
This advisory describes a bug in the Linux kernel's ring-buffer tracing component, where small trace events report a data length that is 4 bytes larger than expected on certain architectures with forced 8-byte alignment. An attacker exploiting this could cause incorrect event length reporting, potentially leading to data corruption or misreading of trace data. The issue is rated as a kernel vulnerability fix, though no specific severity score is stated. This could be relevant where the Linux kernel is deployed in automotive systems, such as in infotainment or control units, but the advisory does not confirm vehicle use. Confirm applicability through the product SBOM or dependency inventory.
The advisory addresses a fix in the Linux kernel's FUSE (Filesystem in Userspace) component for an invalidate lock leak that occurs when an open with the O_TRUNC flag fails during DAX (Direct Access) operation. An attacker could potentially exploit this flaw to cause a denial-of-service condition by exhausting system resources through the leaked lock. The severity is not explicitly stated in the advisory. This could be relevant where FUSE is deployed in automotive systems, such as for managing storage in infotainment or telematics units, but the advisory does not confirm automotive use. Confirm applicability through the product SBOM or dependency inventory.
The advisory describes a change to the Linux kernel's sun8i-ce cryptographic driver that removes its random number generator interface. The technical impact is not detailed in the provided text, and no severity rating is given. This could be relevant where the sun8i-ce driver is deployed in automotive systems, as it is a kernel component for hardware cryptography, but the advisory does not confirm any automotive use. Confirm applicability through the product SBOM or dependency inventory.
The advisory addresses a Linux kernel issue in the ALSA USB audio driver, where incomplete cleanup occurs after system-resume errors. An attacker could potentially exploit this flaw to cause system instability or denial of service. The severity is not explicitly stated in the advisory. This could be relevant where the Linux kernel with USB audio support is deployed in automotive systems, such as infotainment or telematics units. Confirm applicability through the product SBOM or dependency inventory.
This advisory addresses a Linux kernel issue in the ext4 filesystem, where direct access (DAX) is incorrectly enabled on newly encrypted files. An attacker could potentially exploit this flaw to bypass encryption protections, leading to unauthorized access to sensitive data. The severity is not explicitly stated in the advisory. This could be relevant where the Linux kernel with ext4 is deployed in automotive systems, such as infotainment or telematics units. Confirm applicability through the product SBOM or dependency inventory.
This advisory addresses a Linux kernel issue in the HID magicmouse driver, where a stale input device pointer is not cleared when no input is claimed. An attacker could potentially exploit this to cause a use-after-free condition, leading to system instability or privilege escalation. The severity is not explicitly stated in the advisory. This could be relevant where the Linux kernel with the HID magicmouse driver is deployed in automotive systems, such as infotainment or input-handling components. Confirm applicability through the product SBOM or dependency inventory.
The advisory addresses a Linux kernel issue where the Nintendo HID driver registers an input device before its capabilities are fully set, potentially allowing an attacker to exploit the incomplete state. The technical impact is not explicitly detailed in the provided text, and no severity rating is given. This could be relevant where the Linux kernel with Nintendo HID support is deployed in automotive systems, such as infotainment or embedded control units, but the advisory does not confirm automotive use. Confirm applicability through the product SBOM or dependency inventory.
The advisory addresses a vulnerability in the Linux kernel's framebuffer (fbdev) subsystem, where a function used to display display-mode information could write past the intended memory buffer if the list of modes is very long. An attacker could potentially exploit this to cause a memory corruption issue, though the advisory does not state a specific severity rating. This could be relevant where the Linux kernel's framebuffer subsystem is deployed in automotive systems, such as for in-vehicle display interfaces. Confirm applicability through the product SBOM or dependency inventory.
The advisory describes a bug fix in the Linux kernel's crypto subsystem, specifically in the QCE (Qualcomm Crypto Engine) driver. The issue is that if the registration of cryptographic algorithms fails, the error-handling code incorrectly attempts to unregister algorithms that were never successfully registered, which could lead to improper cleanup. This could be relevant where the Linux kernel with the QCE driver is deployed in automotive systems, such as in infotainment or telematics units using Qualcomm hardware. Confirm applicability through the product SBOM or dependency inventory.