ublk: validate auto buf reg before taking uring_cmd
- 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.57, 7.2.6
- 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: ublk: validate auto buf reg before taking uring_cmd With UBLK_F_AUTO_BUF_REG, invalid sqe->addr can fail after ublk_fill_io_cmd() has set UBLK_IO_FLAG_ACTIVE. The uring_cmd is completed while the tag stays active, which can hang teardown. Split validation from buffer apply so the check has no side effects, then take the uring_cmd and store the already-validated buffer. Apply the same order in FETCH so io->buf is not written before __ublk_fetch() state checks.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 52460dda3a775a73f226312b43c0a0211e8665ea · fixed in 8397942b67128e0b1275cfedb5abf4faafac5fd0; From 52460dda3a775a73f226312b43c0a0211e8665ea · fixed in 653d22269a8b83b491f7f186a5d7872f14e6ddca; From 52460dda3a775a73f226312b43c0a0211e8665ea · fixed in ca5a01eee34c7cbe0f531a613b0292a3ad1a419b
- Linux Linux
6.17
- KernelLinux
From 6.17.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.6