fs/aio: Restrict kiocb_set_cancel_fn() to I/O submitted via libaio
- 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
- 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: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: fs/aio: Restrict kiocb_set_cancel_fn() to I/O submitted via libaio If kiocb_set_cancel_fn() is called for I/O submitted via io_uring, the following kernel warning appears: WARNING: CPU: 3 PID: 368 at fs/aio.c:598 kiocb_set_cancel_fn+0x9c/0xa8 Call trace: kiocb_set_cancel_fn+0x9c/0xa8 ffs_epfile_read_iter+0x144/0x1d0 io_read+0x19c/0x498 io_issue_sqe+0x118/0x27c io_submit_sqes+0x25c/0x5fc __arm64_sys_io_uring_enter+0x104/0xab0 invoke_syscall+0x58/0x11c el0_svc_common+0xb4/0xf4 do_el0_svc+0x2c/0xb0 el0_svc+0x2c/0xa4 el0t_64_sync_handler+0x68/0xb4 el0t_64_sync+0x1a4/0x1a8 Fix this by setting the IOCB_AIO_RW flag for read and write I/O that is submitted by libaio.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.1
References 8
git.kernel.org
- stable/c/337b543e274fe7a8f47df3c8293cc6686ffa620f
- stable/c/b4eea7a05ee0ab5ab0514421e6ba8c5d249cf942
- stable/c/ea1cd64d59f22d6d13f367d62ec6e27b9344695f
- stable/c/d7b6fa97ec894edd02f64b83e5e72e1aa352f353
- stable/c/18f614369def2a11a52f569fe0f910b199d13487
- stable/c/e7e23fc5d5fe422827c9a43ecb579448f73876c7
- stable/c/1dc7d74fe456944a9b1c57bd776280249f441ac6
- stable/c/b820de741ae48ccf50dd95e297889c286ff4f760