Kernel warnings via stale lock-class cache reuse
Published Oct 14, 2026 · Updated Oct 14, 2026
Stale-cache reuse in Linux lockdep allows attackers to trigger kernel warnings via lock acquisition after a lock class is invalidated. In kernel/locking/lockdep.c, __lock_acquire() trusts a non-null class_cache entry after zap_class() removes its class, skipping registration and retaining an invalid index or matching a reused slot to an unrelated class. The condition requires lockdep-enabled operation and subsequent acquisition of the affected lock; attacker privileges are undocumented, and the disclosed consequence is incorrect lock validation rather than established code execution or service interruption.
Summary
What happened
Stale-cache reuse in Linux lockdep allows attackers to trigger kernel warnings via lock acquisition after a lock class is invalidated. In kernel/locking/lockdep.c, __lock_acquire() trusts a non-null class_cache entry after zap_class() removes its class, skipping registration and retaining an invalid index or matching a reused slot to an unrelated class. The condition requires lockdep-enabled operation and subsequent acquisition of the affected lock; attacker privileges are undocumented, and the disclosed consequence is incorrect lock validation rather than established code execution or service interruption.
The record
- CVE
- CVE-2026-98398
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 14, 2026CVE publishedPublication date reported by the CVE source.
- Oct 14, 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=5.1
- Affected versionversion=a0b0fd53e1e67639b303b15939b9c653dbe7a8c4 <02c6be7d675b21d81f0ba3a524346850a8c0e3bf
- Affected versionversion=a0b0fd53e1e67639b303b15939b9c653dbe7a8c4 <1c9d664e2e067fca69e5a41d68e23bbc66a583fe
- Affected versionversion=a0b0fd53e1e67639b303b15939b9c653dbe7a8c4 <6bc345f6d81ebe22e0f355c2a21d7e29691f9332
- Affected versionversion=a0b0fd53e1e67639b303b15939b9c653dbe7a8c4 <baa320fbb2f9fea50f5632a307da8ce84fbef5bd
- Affected versionversion=a0b0fd53e1e67639b303b15939b9c653dbe7a8c4 <c7acfb04c7e2e2dea248282b21373d93296644dd
- Affected versionversion=a0b0fd53e1e67639b303b15939b9c653dbe7a8c4 <f63c86e9d267629758adaba18579e784ddd63c32
- Affected versionversion=a0b0fd53e1e67639b303b15939b9c653dbe7a8c4 <f8a1281ab82df5b51fd0384354d4b21daf2b7af0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- Syzkaller lockdep warning reproducerproof of concept · demonstrated
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started