kernel: ext4: block range must be validated before use in ext4_mb_clear_bb()

A use-after-free vulnerability exists in the linux kernel, such thatthe Block range to free is validated in ext4freeblocks using ext4inodeblockvalid and then it's passed to ext4mbclearbb.However, in some situations on bigalloc file system the range might be adjusted after the validation in...

BlurExchage#setBlockRange can cause previously expired order to be unexpectedly valid again

Lines of code Vulnerability details Impact A previously canceled order becomes valid again Proof of Concept BlurExchagesetBlockRange allows the owner to set the block range for which the oracles signature is valid for. If the block range is set to longer, orders that would have been invalid are...

GSD-2022-1005084 ext4: block range must be validated before use in ext4_mb_clear_bb()

ext4: block range must be validated before use in ext4mbclearbb This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven. This ID is fixed in Linux Kernel version v5.19.4 by commit...

PT-2022-33342 · Linux · Linux Kernel

Name of the Vulnerable Software and Affected Versions: Linux Kernel versions prior to v5.19.4 Description: The issue is related to the ext4 file system, where a block range must be validated before use in the ext4 mb clear bb function. The actual impact and attack plausibility have not yet been...

PT-2018-13711 · Ethereum · Go-Ethereum

Name of the Vulnerable Software and Affected Versions: Go Ethereum versions prior to 1.8.14 Description: The issue arises from improper input validation in the TraceChain function within the eth/api tracer.go file. Specifically, it does not verify that the end block is after the start block. This...