dm-integrity: fix NULL pointer dereference when the 'R' flag is used
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.58, 7.2.12
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Linux kernel's dm-integrity device-mapper target, which provides block-level integrity checking, is affected. A crash (NULL pointer dereference) can occur when a device with a dirty bitmap is activated in the 'R' (read-only recovery) mode, potentially causing a system crash or denial of service.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix NULL pointer dereference when the 'R' flag is used If the dm-integrity device has the SB_FLAG_DIRTY_BITMAP flag set and the user activates the device in the 'R' mode, a crash in dm_integrity_resume happens because the function attempts to read the journal containing the bitmap. This patch makes dm-integrity skip any writes to the device in dm_integrity_resume if the device is activated in the 'R' mode.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Linux Linux
From 468dfca38b1a6fbdccd195d875599cb7c8875cd9 · fixed in 2e25842f0e4423e0efb243f56153d842ed6b933f; From 468dfca38b1a6fbdccd195d875599cb7c8875cd9 · fixed in 69ed43ed8a174465fca1ba6bfbde53e4618c8956; From 468dfca38b1a6fbdccd195d875599cb7c8875cd9 · fixed in 7d4d4f3b668d708d94f62ecdd33ac330a6fd8a84
- Linux Linux
5.2
- KernelLinux
From 5.2.0 · fixed in 6.18.58; From 6.19.0 · fixed in 7.2.12