Kernel warning via cross-process semaphore release
Published Nov 3, 2026 · Updated Nov 3, 2026
Locking misuse in Linux dm-cache allows local users to trigger a kernel warning through cache device suspend and resume operations. The background_work_lock write semaphore can be acquired and released by different processes, violating ownership requirements in cache_resume(). Reproduction requires a configured dm-cache device, administrative device-mapper access, and CONFIG_DEBUG_RWSEMS; the documented result is a warning, not a demonstrated crash.
Summary
What happened
Locking misuse in Linux dm-cache allows local users to trigger a kernel warning through cache device suspend and resume operations. The background_work_lock write semaphore can be acquired and released by different processes, violating ownership requirements in cache_resume(). Reproduction requires a configured dm-cache device, administrative device-mapper access, and CONFIG_DEBUG_RWSEMS; the documented result is a warning, not a demonstrated crash.
The record
- CVE
- CVE-2026-99256
- Published
- Nov 3, 2026
- Updated
- Nov 3, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 3, 2026CVE publishedPublication date reported by the CVE source.
- Nov 3, 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=4.12
- Affected versionversion=b29d4986d0da1a27cd35917cdb433672f5c95d7f <0c7a8cad7c96012a9157a189649e569d0390f384
- Affected versionversion=b29d4986d0da1a27cd35917cdb433672f5c95d7f <104f09e02038b0fc6bbb718b3976af029e15c1d0
- Affected versionversion=b29d4986d0da1a27cd35917cdb433672f5c95d7f <2f2cfa16dd0f4179bb988139dd37d00a42324f6c
- Affected versionversion=b29d4986d0da1a27cd35917cdb433672f5c95d7f <6290507ecc0dd6dd40759729cbbbd49b1d2a63c4
- Affected versionversion=b29d4986d0da1a27cd35917cdb433672f5c95d7f <73df2ff409f3db95029982fe3656329568e3715d
- Affected versionversion=b29d4986d0da1a27cd35917cdb433672f5c95d7f <8433fd005c25fd127021f67c9144a879fb585572
- Affected versionversion=b29d4986d0da1a27cd35917cdb433672f5c95d7f <bc9781c0247de107876f32929f1637db93a42b34
- Affected versionversion=b29d4986d0da1a27cd35917cdb433672f5c95d7f <f5db935d257023c3ef410bd39163b949b0e5a55d
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
- dm-cache suspend/resume warning reproducerproof of concept · unverified
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.
Contact us