Kernel memory corruption via unsynchronized watchdog timer
Published May 21, 2024 · Updated May 11, 2026
Use-after-free in the Linux kernel SBC60xx watchdog driver allows attackers to corrupt kernel memory during device removal. The wdt_startup() removal path calls del_timer(), which can return while wdt_timer remains active and later accesses freed driver state. Reachability requires the SBC60xx watchdog driver and a removal race while its timer handler is running; consequences include a kernel crash or memory corruption.
Summary
What happened
Use-after-free in the Linux kernel SBC60xx watchdog driver allows attackers to corrupt kernel memory during device removal. The wdt_startup() removal path calls del_timer(), which can return while wdt_timer remains active and later accesses freed driver state. Reachability requires the SBC60xx watchdog driver and a removal race while its timer handler is running; consequences include a kernel crash or memory corruption.
The record
- CVE
- CVE-2021-47324
- Published
- May 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0ac50a76cf3cd63db000648b3b19f3f98b8aaa76
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <146cc288fb80c662c9c35e7bc58325d1ac0a7875
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <63a3dc24bd053792f84cb4eef0168b1266202a02
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <862f2b5a7c38762ac9e369daefbf361a91aca685
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8adbbe6c86bb13e14f8a19e036ae5f4f5661fd90
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a397cb4576fc2fc802562418b3a50b8f67d60d31
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b4ebf4a4692e84163a69444c70ad515de06e2259
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c08a6b31e4917034f0ed0cb457c3bb209576f542
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <dc9403097be52d57a5c9c35efa9be79d166a78af
- Affected versionversion=2.6.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo