{"uuid": "9acc42ce-8076-4864-a376-e100c3352965", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21643", "type": "seen", "source": "https://t.me/cvedetector/15836", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21643 - \"CIFS Netfs Linux Kernel Async DIO Handling Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-21643 \nPublished : Jan. 19, 2025, 11:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnetfs: Fix kernel async DIO  \n  \nNetfslib needs to be able to handle kernel-initiated asynchronous DIO that  \nis supplied with a bio_vec[] array.  Currently, because of the async flag,  \nthis gets passed to netfs_extract_user_iter() which throws a warning and  \nfails because it only handles IOVEC and UBUF iterators.  This can be  \ntriggered through a combination of cifs and a loopback blockdev with  \nsomething like:  \n  \n        mount //my/cifs/share /foo  \n        dd if=/dev/zero of=/foo/m0 bs=4K count=1K  \n        losetup --sector-size 4096 --direct-io=on /dev/loop2046 /foo/m0  \n        echo hello >/dev/loop2046  \n  \nThis causes the following to appear in syslog:  \n  \n        WARNING: CPU: 2 PID: 109 at fs/netfs/iterator.c:50 netfs_extract_user_iter+0x170/0x250 [netfs]  \n  \nand the write to fail.  \n  \nFix this by removing the check in netfs_unbuffered_write_iter_locked() that  \ncauses async kernel DIO writes to be handled as userspace writes.  Note  \nthat this change relies on the kernel caller maintaining the existence of  \nthe bio_vec array (or kvec[] or folio_queue) until the op is complete. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-19T13:07:22.000000Z"}