nvmet-tcp: Do not WARN on remotely-controlled oversized SGL allocations
- 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 5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106, and 3 more
- 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: nvmet-tcp: Do not WARN on remotely-controlled oversized SGL allocations When fuzzing the nvme target code, I tripped a kernel warning in nvmet_tcp_map_data() because the length passed into the allocator is controlled by the remote initiator. A remote initiator that sends a command with an SGL claiming a huge number, can create a scatterlist and iovec allocation of over 1 million entries, which causes the backing kmalloc call to exceed MAX_PAGE_ORDER and then the page allocator will trip on a WARN_ON_ONCE_GFP() message: WARNING: mm/page_alloc.c:5280 __alloc_frozen_pages_noprof Workqueue: nvmet_tcp_wq nvmet_tcp_io_work ... sgl_alloc_order nvmet_tcp_map_data nvmet_tcp_try_recv_pdu As it's never good to trip a kernel warning remotely due to many systems having panic-on-warn enabled, let's silence it by just add GFP_NOWARN to the allocation flags.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 872d26a391da92ed8f0c0f5cb5fef428067b7f30 · fixed in 8d01f0d0e96485e39ad89b859ef85e1dc3020465; From 872d26a391da92ed8f0c0f5cb5fef428067b7f30 · fixed in 7b6a54d4e7b0da423c2b53ed293fd36b16c0b19e; From 872d26a391da92ed8f0c0f5cb5fef428067b7f30 · fixed in e7077e6c45423dd2bb7de7b5fc4b018a8e6c4741; From 872d26a391da92ed8f0c0f5cb5fef428067b7f30 · fixed in 86cc450022473c4a29b43a09f3ec22a9ef566dac; From 872d26a391da92ed8f0c0f5cb5fef428067b7f30 · fixed in c509f20be1cabda3087810bb2d658d66b3f31f35; From 872d26a391da92ed8f0c0f5cb5fef428067b7f30 · fixed in 9c95f7e66c62ee6c6abedcf1c04311f430ff5833; From 872d26a391da92ed8f0c0f5cb5fef428067b7f30 · fixed in 7fd6da0f28932442b51658bac4ff55565ca9b377; From 872d26a391da92ed8f0c0f5cb5fef428067b7f30 · fixed in 9b770e40bc00381e5ebf53653de5776773415be3; From 872d26a391da92ed8f0c0f5cb5fef428067b7f30 · fixed in 737a3b535247226f6e1a7988fd9d6e63e7d6fc71
- Linux Linux
5.0
- KernelLinux
From 5.0.0 · fixed in 5.10.267; From 5.11.0 · fixed in 5.15.218; From 5.16.0 · fixed in 6.1.185; From 6.2.0 · fixed in 6.6.154; From 6.7.0 · fixed in 6.12.106; From 6.13.0 · fixed in 6.18.47; From 6.19.0 · fixed in 7.1.11; From 7.2.0 · fixed in 7.2.1
References 9
git.kernel.org
- stable/c/8d01f0d0e96485e39ad89b859ef85e1dc3020465
- stable/c/7b6a54d4e7b0da423c2b53ed293fd36b16c0b19e
- stable/c/e7077e6c45423dd2bb7de7b5fc4b018a8e6c4741
- stable/c/86cc450022473c4a29b43a09f3ec22a9ef566dac
- stable/c/c509f20be1cabda3087810bb2d658d66b3f31f35
- stable/c/9c95f7e66c62ee6c6abedcf1c04311f430ff5833
- stable/c/7fd6da0f28932442b51658bac4ff55565ca9b377
- stable/c/9b770e40bc00381e5ebf53653de5776773415be3
- stable/c/737a3b535247226f6e1a7988fd9d6e63e7d6fc71