nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec
- 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.249, 5.15.199, 6.1.162, 6.6.122, 5.5, 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
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec Commit efa56305908b ("nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length") added ttag bounds checking and data_offset validation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate whether the command's data structures (cmd->req.sg and cmd->iov) have been properly initialized before processing H2C_DATA PDUs. The nvmet_tcp_build_pdu_iovec() function dereferences these pointers without NULL checks. This can be triggered by sending H2C_DATA PDU immediately after the ICREQ/ICRESP handshake, before sending a CONNECT command or NVMe write command. Attack vectors that trigger NULL pointer dereferences: 1. H2C_DATA PDU sent before CONNECT → both pointers NULL 2. H2C_DATA PDU for READ command → cmd->req.sg allocated, cmd->iov NULL 3. H2C_DATA PDU for uninitialized command slot → both pointers NULL The fix validates both cmd->req.sg and cmd->iov before calling nvmet_tcp_build_pdu_iovec(). Both checks are required because: • Uninitialized commands: both NULL • READ commands: cmd->req.sg allocated, cmd->iov NULL • WRITE commands: both allocated
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From f775f2621c2ac5cc3a0b3a64665dad4fb146e510 · fixed in baabe43a0edefac8cd7b981ff87f967f6034dafe; From 4cb3cf7177ae3666be7fb27d4ad4d72a295fb02d · fixed in 76abc83a9d25593c2b7613c549413079c14a4686; From 2871aa407007f6f531fae181ad252486e022df42 · fixed in 7d75570002929d20e40110d6b03e46202c9d1bc7; From 24e05760186dc070d3db190ca61efdbce23afc88 · fixed in fdecd3b6aac10d5a18d0dc500fe57f8648b66cd4; From efa56305908ba20de2104f1b8508c6a7401833be · fixed in 3def5243150716be86599c2a1767c29c68838b6d; From efa56305908ba20de2104f1b8508c6a7401833be · fixed in 374b095e265fa27465f34780e0eb162ff1bef913; From efa56305908ba20de2104f1b8508c6a7401833be · fixed in 32b63acd78f577b332d976aa06b56e70d054cbba; From 5.10.209 · fixed in 5.10.249; From 5.15.148 · fixed in 5.15.199; From 6.1.75 · fixed in 6.1.162; From 6.6.14 · fixed in 6.6.122; From 5.4.268 · fixed in 5.5; From 6.7.2 · fixed in 6.8
- Linux Linux
6.8
- KernelLinux
fixed in 5.10.249; From 5.11.0 · fixed in 5.15.199; From 5.16.0 · fixed in 6.1.162; From 6.2.0 · fixed in 6.6.122; From 6.7.0 · fixed in 6.12.67; From 6.8.0 · fixed in 6.18.7
References 7
git.kernel.org
- stable/c/baabe43a0edefac8cd7b981ff87f967f6034dafe
- stable/c/76abc83a9d25593c2b7613c549413079c14a4686
- stable/c/7d75570002929d20e40110d6b03e46202c9d1bc7
- stable/c/fdecd3b6aac10d5a18d0dc500fe57f8648b66cd4
- stable/c/3def5243150716be86599c2a1767c29c68838b6d
- stable/c/374b095e265fa27465f34780e0eb162ff1bef913
- stable/c/32b63acd78f577b332d976aa06b56e70d054cbba