Bug 2320198 (CVE-2024-47725) - CVE-2024-47725 kernel: dm-verity: restart or panic on an I/O error
Summary: CVE-2024-47725 kernel: dm-verity: restart or panic on an I/O error
Keywords:
Status: NEW
Alias: CVE-2024-47725
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2320354
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-10-21 13:01 UTC by OSIDB Bzimport
Modified: 2024-11-26 08:20 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2024-10-21 13:01:34 UTC
In the Linux kernel, the following vulnerability has been resolved:

dm-verity: restart or panic on an I/O error

Maxim Suhanov reported that dm-verity doesn't crash if an I/O error
happens. In theory, this could be used to subvert security, because an
attacker can create sectors that return error with the Write Uncorrectable
command. Some programs may misbehave if they have to deal with EIO.

This commit fixes dm-verity, so that if "panic_on_corruption" or
"restart_on_corruption" was specified and an I/O error happens, the
machine will panic or restart.

This commit also changes kernel_restart to emergency_restart -
kernel_restart calls reboot notifiers and these reboot notifiers may wait
for the bio that failed. emergency_restart doesn't call the notifiers.


Note You need to log in before you can comment on or make changes to this bug.