nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length
- 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: nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length If the host sends an H2CData command with an invalid DATAL, the kernel may crash in nvmet_tcp_build_pdu_iovec(). Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 lr : nvmet_tcp_io_work+0x6ac/0x718 [nvmet_tcp] Call trace: process_one_work+0x174/0x3c8 worker_thread+0x2d0/0x3e8 kthread+0x104/0x110 Fix the bug by raising a fatal error if DATAL isn't coherent with the packet size. Also, the PDU length should never exceed the MAXH2CDATA parameter which has been communicated to the host in nvmet_tcp_handle_icreq().
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
5.0
References 7
git.kernel.org
- stable/c/ee5e7632e981673f42a50ade25e71e612e543d9d
- stable/c/f775f2621c2ac5cc3a0b3a64665dad4fb146e510
- stable/c/4cb3cf7177ae3666be7fb27d4ad4d72a295fb02d
- stable/c/2871aa407007f6f531fae181ad252486e022df42
- stable/c/24e05760186dc070d3db190ca61efdbce23afc88
- stable/c/70154e8d015c9b4fb56c1a2ef1fc8b83d45c7f68
- stable/c/efa56305908ba20de2104f1b8508c6a7401833be