io_uring/kbuf: reallocate buf lists on upgrade
- 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.6.79, 6.12.16, 6.13.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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: reallocate buf lists on upgrade IORING_REGISTER_PBUF_RING can reuse an old struct io_buffer_list if it was created for legacy selected buffer and has been emptied. It violates the requirement that most of the field should stay stable after publish. Always reallocate it instead.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 2fcabce2d7d34f69a888146dab15b36a917f09d4 · fixed in 146a185f6c05ee263db715f860620606303c4633; From 2fcabce2d7d34f69a888146dab15b36a917f09d4 · fixed in 7d0dc28dae836caf7645fef62a10befc624dd17b; From 2fcabce2d7d34f69a888146dab15b36a917f09d4 · fixed in 2a5febbef40ce968e295a7aeaa5d5cbd9e3e5ad4; From 2fcabce2d7d34f69a888146dab15b36a917f09d4 · fixed in 8802766324e1f5d414a81ac43365c20142e85603
- Linux Linux
5.19
- KernelLinux
From 5.19.0 · fixed in 6.6.79; From 6.7.0 · fixed in 6.12.16; From 6.13.0 · fixed in 6.13.4