In the Linux kernel, the following vulnerability has been resolved: char: tlclk: fix use-after-free in tlclk_cleanup() This patch improves the module cleanup process in the tlclk driver to prevent potential use-after-free and race conditions. Currently, the file_operations structure does not specify the .owner field, which could allow the module to be unloaded while user-space processes are still interacting with the device. Additionally, the tlclk_cleanup() function frees the alarm_events memory before ensuring that blocked processes in the waitqueue are fully awakened and that the switchover_timer has completed. To address these cases, this patch: - Sets '.owner = THIS_MODULE' in tlclk_fops to safely defer module unloading while the device is in use. - Updates tlclk_cleanup() to explicitly wake up all blocked readers (wake_up_all), properly release hardware I/O regions, and safely delete the timer (timer_delete_sync) prior to freeing memory.
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-80622 represents a use-after-free vulnerability in the Linux kernel's tlclk (Telephony Clock) driver cleanup routine. The vulnerability stems from improper module lifecycle management—specifically, the absence of the .owner field in the file_operations structure, which fails to prevent module unloading while user-space processes maintain active references to the device. This allows an attacker with local access to trigger a use-after-free condition by unloading the module while concurrent operations are in progress, potentially leading to kernel memory corruption, privilege escalation, or denial of service. Systems running the affected tlclk driver are at risk, particularly in telecommunications and time-critical applications that depend on this hardware abstraction layer.
While Casky's current skill mapping does not directly correlate to MITRE ATT&CK defensive techniques for this specific CVE (0 matching skills), the underlying attack patterns align with techniques involving Exploitation of Vulnerability (T1190) and Privilege Escalation (T1548). A Casky practitioner analyzing kernel driver security would benefit from extended reasoning capabilities to detect the architectural weakness: examining module registration patterns, verifying .owner field assignments in character device drivers, and analyzing cleanup function logic for race conditions between resource deallocation and in-flight user operations. Organizations should use Casky's reasoning engine to construct detection patterns around unusual kernel module state transitions and memory access anomalies that would surface use-after-free exploitation attempts on systems still running vulnerable tlclk versions.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-80622. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation