CVE-2023-6356: Red Hat Enterprise Linux 8 · NULL Pointer Dereference
Affects Red Hat Enterprise Linux 8Source CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 1.4% chance of exploitation in 30 days – higher than 73% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
AI-suggested
Organizations should monitor Red Hat advisories closely and apply kernel patches addressing CVE-2023-6356 as soon as they become available. Until patches are deployed, network-level mitigations should be implemented, including restricting access to NVMe over TCP services via firewalls or network segmentation to trusted hosts only. Disabling NVMe over TCP if not in use can eliminate exposure. Employing intrusion detection systems (IDS) to monitor for unusual TCP packet patterns targeting NVMe ports may help detect exploitation attempts. Regularly auditing system logs and kernel messages for signs of kernel panics or crashes related to NVMe can aid early detection. Additionally, organizations should ensure robust backup and recovery procedures to minimize downtime impact. Coordination with Red Hat support for guidance and updates is recommended. Finally, educating system administrators about this vulnerability and its impact will improve response readiness.
Description
A flaw was found in the Linux kernel's NVMe driver. This issue may allow an unauthenticated malicious actor to send a set of crafted TCP packages when using NVMe over TCP, leading the NVMe driver to a NULL pointer dereference in the NVMe driver and causing kernel panic and a denial of service.
References
- access.redhat.com/errata/RHSA-2024:0723 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:0724 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:0725 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:0881 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:0897 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:1248 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:2094 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:3810 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2023-6356 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2254054 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2024/06/msg00016.html (opens in a new tab)
- security.netapp.com/advisory/ntap-20240415-0002/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZFYW6R64GPLUOXSQBJI3JBUX3HGLAYPP/ (opens in a new tab)