{"id":"CVE-2026-22998","title":"nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec\n\nCommit efa56305908b (\"nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length\")\nad…","severity":"high","cvss":7.5,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","cvssSource":"cna","vendor":"Linux","product":"Linux","affected":["Linux >= f775f2621c2ac5cc3a0b3a64665dad4fb146e510 < baabe43a0edefac8cd7b981ff87f967f6034dafe","Linux >= 4cb3cf7177ae3666be7fb27d4ad4d72a295fb02d < 76abc83a9d25593c2b7613c549413079c14a4686","Linux >= 2871aa407007f6f531fae181ad252486e022df42 < 7d75570002929d20e40110d6b03e46202c9d1bc7","Linux >= 24e05760186dc070d3db190ca61efdbce23afc88 < fdecd3b6aac10d5a18d0dc500fe57f8648b66cd4","Linux >= efa56305908ba20de2104f1b8508c6a7401833be < 3def5243150716be86599c2a1767c29c68838b6d","Linux >= efa56305908ba20de2104f1b8508c6a7401833be < 374b095e265fa27465f34780e0eb162ff1bef913","Linux >= efa56305908ba20de2104f1b8508c6a7401833be < 32b63acd78f577b332d976aa06b56e70d054cbba","Linux ee5e7632e981673f42a50ade25e71e612e543d9d","Linux 70154e8d015c9b4fb56c1a2ef1fc8b83d45c7f68","Linux >= 5.10.209 < 5.10.249","Linux >= 5.15.148 < 5.15.199","Linux >= 6.1.75 < 6.1.162","Linux >= 6.6.14 < 6.6.122","Linux >= 5.4.268 < 5.5","Linux >= 6.7.2 < 6.8","Linux 6.8"],"ssvc":{"exploitation":"none","automatable":"yes","technicalImpact":"partial","timestamp":"2026-06-16T20:38:02.086283Z"},"published":"2026-01-25","updated":"2026-10-19","sourceUpdated":"2026-10-19T18:25:26.863Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-22998","references":[{"url":"https://git.kernel.org/stable/c/baabe43a0edefac8cd7b981ff87f967f6034dafe"},{"url":"https://git.kernel.org/stable/c/76abc83a9d25593c2b7613c549413079c14a4686"},{"url":"https://git.kernel.org/stable/c/7d75570002929d20e40110d6b03e46202c9d1bc7"},{"url":"https://git.kernel.org/stable/c/fdecd3b6aac10d5a18d0dc500fe57f8648b66cd4"},{"url":"https://git.kernel.org/stable/c/3def5243150716be86599c2a1767c29c68838b6d"},{"url":"https://git.kernel.org/stable/c/374b095e265fa27465f34780e0eb162ff1bef913"},{"url":"https://git.kernel.org/stable/c/32b63acd78f577b332d976aa06b56e70d054cbba"}],"tags":["cve.org"],"epss":0.0079,"epssPercentile":0.55492,"ingestedAt":"2026-10-19T18:35:50.112Z","slug":"CVE-2026-22998","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec\n\nCommit efa56305908b (\"nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length\")\nadded ttag bounds checking and data_offset\nvalidation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate\nwhether the command's data structures (cmd->req.sg and cmd->iov) have\nbeen properly initialized before processing H2C_DATA PDUs.\n\nThe nvmet_tcp_build_pdu_iovec() function dereferences these pointers\nwithout NULL checks. This can be triggered by sending H2C_DATA PDU\nimmediately after the ICREQ/ICRESP handshake, before\nsending a CONNECT command or NVMe write command.\n\nAttack vectors that trigger NULL pointer dereferences:\n1. H2C_DATA PDU sent before CONNECT → both pointers NULL\n2. H2C_DATA PDU for READ command → cmd->req.sg allocated, cmd->iov NULL\n3. H2C_DATA PDU for uninitialized command slot → both pointers NULL\n\nThe fix validates both cmd->req.sg and cmd->iov before calling\nnvmet_tcp_build_pdu_iovec(). Both checks are required because:\n- Uninitialized commands: both NULL\n- READ commands: cmd->req.sg allocated, cmd->iov NULL\n- WRITE commands: both allocated\n\n## Affected\n\n- `Linux >= f775f2621c2ac5cc3a0b3a64665dad4fb146e510 < baabe43a0edefac8cd7b981ff87f967f6034dafe`\n- `Linux >= 4cb3cf7177ae3666be7fb27d4ad4d72a295fb02d < 76abc83a9d25593c2b7613c549413079c14a4686`\n- `Linux >= 2871aa407007f6f531fae181ad252486e022df42 < 7d75570002929d20e40110d6b03e46202c9d1bc7`\n- `Linux >= 24e05760186dc070d3db190ca61efdbce23afc88 < fdecd3b6aac10d5a18d0dc500fe57f8648b66cd4`\n- `Linux >= efa56305908ba20de2104f1b8508c6a7401833be < 3def5243150716be86599c2a1767c29c68838b6d`\n- `Linux >= efa56305908ba20de2104f1b8508c6a7401833be < 374b095e265fa27465f34780e0eb162ff1bef913`\n- `Linux >= efa56305908ba20de2104f1b8508c6a7401833be < 32b63acd78f577b332d976aa06b56e70d054cbba`\n- `Linux ee5e7632e981673f42a50ade25e71e612e543d9d`\n- `Linux 70154e8d015c9b4fb56c1a2ef1fc8b83d45c7f68`\n- `Linux >= 5.10.209 < 5.10.249`\n- `Linux >= 5.15.148 < 5.15.199`\n- `Linux >= 6.1.75 < 6.1.162`\n- `Linux >= 6.6.14 < 6.6.122`\n- `Linux >= 5.4.268 < 5.5`\n- `Linux >= 6.7.2 < 6.8`\n- `Linux 6.8`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"twilight","depthScore":41,"depthScoreParts":{"impact":41.3,"likelihood":0.2,"exploitation":0,"ransomware":0},"changes":[]}