block: reject polled dio with user integrity metadata
- 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.17, 6.18.56, 7.2.10
- 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: block: reject polled dio with user integrity metadata IOCB_HAS_METADATA leaves iocb->private as a uio_meta, while iocb_bio_iopoll() expects a bio. Since 2729a60bbfb9, metadata I/O always uses __blkdev_direct_IO(), which never publishes the bio for polling, so IOPOLL calls bio_poll() on the uio_meta. Reproducer: io_uring IOPOLL plus a PI attribute on an integrity device (scsi_debug dif=1 dix=1). KASAN reports: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000004 KASAN: null-ptr-deref in range [0x0000000000000020-0x0000000000000027] RIP: 0010:bio_poll+0x9d/0x4b0 Call Trace: iocb_bio_iopoll+0x5b/0x80 io_uring_classic_poll+0xf3/0x140 io_do_iopoll+0x4e3/0xc00 io_iopoll_check+0x275/0x560 __do_sys_io_uring_enter+0x2e5/0x720 Return -EOPNOTSUPP when HIPRI is combined with user metadata.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 2729a60bbfb9215997f25372ebe9b7964f038296 · fixed in c97ef13ad96be0e08af38dfa2ed40cded0b53e1b; From 2729a60bbfb9215997f25372ebe9b7964f038296 · fixed in dd33c03cefccdfcb223e9e6262643d64f8c1ae20; From 2729a60bbfb9215997f25372ebe9b7964f038296 · fixed in 2a42e6fe1293f2e2d579c9fe5bbab056dd8b880e; From 6.16.8 · fixed in 6.17
- Linux Linux
6.17
- KernelLinux
From 6.17.0 · fixed in 6.18.56; From 6.19.0 · fixed in 7.2.10