Skip to main content
VulnerabilityPublished Updated

CVE-2026-72096: Linux kernel · dm-verity: make error counter atomic

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in b8eddcb1bf72199451950aff9087bd76da80635d : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:04 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in b8eddcb1bf72199451950aff9087bd76da80635d, ac99781115d37d10894653b47941d9d8fc26fa64, aab5cb8a40e82bd33d0f3ae3c73041848b18bfd2 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 65ff5b7ddf0541f2b6e5cc59c47bfbf6cbcd91b8, < b8eddcb1bf72199451950aff9087bd76da80635d
Fixed in
  • b8eddcb1bf72199451950aff9087bd76da80635d
LinuxLinuxAffected
  • ≥ 65ff5b7ddf0541f2b6e5cc59c47bfbf6cbcd91b8, < ac99781115d37d10894653b47941d9d8fc26fa64
Fixed in
  • ac99781115d37d10894653b47941d9d8fc26fa64
LinuxLinuxAffected
  • ≥ 65ff5b7ddf0541f2b6e5cc59c47bfbf6cbcd91b8, < aab5cb8a40e82bd33d0f3ae3c73041848b18bfd2
Fixed in
  • aab5cb8a40e82bd33d0f3ae3c73041848b18bfd2
LinuxLinuxAffected
  • ≥ 65ff5b7ddf0541f2b6e5cc59c47bfbf6cbcd91b8, < a7df22c4e0e9110f0be577919d3cb9389b2aba65
Fixed in
  • a7df22c4e0e9110f0be577919d3cb9389b2aba65
LinuxLinuxAffected
  • ≥ 65ff5b7ddf0541f2b6e5cc59c47bfbf6cbcd91b8, < 3303e5c6501e3638ded8e9402d703805b00ce64e
Fixed in
  • 3303e5c6501e3638ded8e9402d703805b00ce64e
LinuxLinuxAffected
  • ≥ 65ff5b7ddf0541f2b6e5cc59c47bfbf6cbcd91b8, < 752e214b2c6f15b40b0d873a2ce27733ce0884c6
Fixed in
  • 752e214b2c6f15b40b0d873a2ce27733ce0884c6

Description

In the Linux kernel, the following vulnerability has been resolved: dm-verity: make error counter atomic The error counter "v->corrupted_errs" was not atomic, thus it could be subject to race conditions. The call to dm_audit_log_target("max-corrupted-errors") may be skipped due to the races.

References

Community reviews

Loading reviews…