iomap: don't free integrity payload that doesn't exist
- 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 7.2.4
- 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
In the Linux kernel, the following vulnerability has been resolved: iomap: don't free integrity payload that doesn't exist fs_bio_integrity_alloc might not allocate a bio integrity payload if PI verification is disabled on the block device. Check for that case before calling fs_bio_integrity_free in iomap_bio_read_folio_range_sync to avoid a NULL pointer dereferences. Make the branch cover the PI verification as well - while fs_bio_integrity_verify works without an integrity payload, it requires one to actually do useful work.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 0b10a370529cbd7b918c1eef43d409e43d9e0b78 · fixed in 65651f1001aa3638909bc58c7b2b46160692757b; From 0b10a370529cbd7b918c1eef43d409e43d9e0b78 · fixed in 8a8685b32c0718cc7b2cb4d6202e5a5b8e0a8e2d
- Linux Linux
7.1
- KernelLinux
From 7.1.0 · fixed in 7.2.4