CVE-2025-71073
BaseFortify
Publication date: 2026-01-13
Last updated on: 2026-03-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 2.6.12 |
| linux | linux_kernel | 2.6.12 |
| linux | linux_kernel | 2.6.12 |
| linux | linux_kernel | 2.6.12 |
| linux | linux_kernel | 2.6.12 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.13 (inc) to 6.18.3 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 2.6.12.1 (inc) to 6.12.64 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves the lkkbd driver where a work handler (lkkbd_reinit) can run after the lkkbd structure has been freed. Specifically, lkkbd_interrupt() schedules work that dereferences the lkkbd structure, but lkkbd_disconnect() and error paths in lkkbd_connect() free this structure without properly preventing the work from being re-queued. This leads to a potential use-after-free condition, which can cause undefined behavior or crashes. The fix involves using disable_work_sync() instead of cancel_work_sync() to ensure the work cannot be re-queued after the structure is freed.
How can this vulnerability impact me? :
This vulnerability can lead to use-after-free conditions in the Linux kernel's lkkbd driver, potentially causing system instability, crashes, or security issues such as arbitrary code execution or privilege escalation if exploited. It affects the reliability and security of systems running the vulnerable Linux kernel.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the issue is resolved. The fix involves using disable_work_sync() instead of cancel_work_sync() in the lkkbd_disconnect() and lkkbd_connect() error paths to prevent the work handler from running after the structure has been freed.