A Linux kernel eswin clock driver declares a structure on the stack but does not fully initialize all fields. Because the clk core later examines these fields for parent resolution, leftover garbage can be interpreted as a bogus pointer. When the driver registers a clock, the kernel dereferences this bad pointer and triggers a null‑pointer dereference, causing a kernel oops. This results in a system crash and loss of availability. The vulnerability is a CWE‑824 flaw involving improper assumptions about data integrity during clock parent resolution.

The flaw exists in the eswin clock support code that ships in the mainline Linux kernel and is also present in backported 6.17 builds. Any Linux distribution or embedded system that compiles or includes this driver—including EIC7700‑based boards—can be affected. Systems that do not load or use the eswin driver are not impacted.

The CVSS base score is 5.5, indicating moderate severity. The EPSS score is less than 1 % and the vulnerability is not yet listed in CISA’s KEV catalog, implying limited known exploitation activity. The attack vector is local: an attacker would need to be able to load the eswin module or trigger its probe during boot or device initialization, which generally requires privileged or root access. The crash is nondeterministic because it depends on uninitialized stack contents, making exploitation more difficult. Nonetheless, any attacker who can cause the driver to register a clock can produce a denial‑of‑service by crashing the kernel.