What is CVE-2023-6536?A high-severity flaw in Linux kernel, explained.
CVE-2023-6536 is a high-severity flaw (CVSS 7.5) in Linux kernel, published on 7 February 2024. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 1.5%. If you run an affected version, plan in the vendor’s fix.
Published 7 February 2024. Record last updated 17 June 2026. We keep this page's data up to date.
What is CVE-2023-6536? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline.
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, causing kernel panic and a denial of service.
What kind of flaw is it?
- CWE-476NULL Pointer Dereference
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan take it offline
Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Is CVE-2023-6536 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.5%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2023-6536 scores 47. Action: Plan remediation.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2023-6536 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2023-6536? 17 products.
The published record lists 17 products from 3 vendors. Versions are shown as published: "5.0 to before 5.4.268" means from 5.0 up to, but not including, 5.4.268. If you run one of these, check your version, then go to the fix below.
- Operating system
Linux kernel
by Linux
Affected versions5.0 to before 5.4.2685.5 to before 5.10.2095.11 to before 5.15.1485.16 to before 6.1.756.2 to before 6.6.146.7 to before 6.7.2 - Application
Codeready Linux Builder Eus
by Red Hat
Affected versions8.69.2 - Application
Codeready Linux Builder Eus for Power Little Endian Eus
by Red Hat
Affected versions8.6_ppc64le9.2_ppc64le - Application
Codeready Linux Builder for Arm64 Eus
by Red Hat
Affected versions8.6_aarch649.2_aarch64 - Operating system
Enterprise Linux
by Red Hat
Affected versions8.09.0 - Operating system
Enterprise Linux Eus
by Red Hat
Affected versions8.69.2 - Operating system
Enterprise Linux for Arm 64 Eus
by Red Hat
Affected versions8.6_aarch649.2_aarch64 - Operating system
Enterprise Linux for Ibm Z Systems Eus
by Red Hat
Affected versions8.6_s390x9.2_s390x - Operating system
Enterprise Linux for Power Little Endian Eus
by Red Hat
Affected versions8.6_ppc64le9.2_ppc64le
How do I fix CVE-2023-6536? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the latest update from the vendor. The references list where the vendor has published details.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2023-6536 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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 ...
- Matched to
- Linux kernel on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2023-6536 is a high-severity flaw in Linux kernel, published on 7 February 2024. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline.
It scores 7.5 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2023-6536 is 47 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.5%. That can change at any time, which is why we keep watching.
For Linux kernel: 5.0 to before 5.4.268, 5.5 to before 5.10.209, 5.11 to before 5.15.148, 5.16 to before 6.1.75, 6.2 to before 6.6.14, 6.7 to before 6.7.2. The record lists 17 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.