Home/CVE/Incorrect verifier pruning in BPF in Linux Kernel >=5.4 leads to unsafe
code paths being incorrectly marked as safe,
CVE
CVE-2023-2163
Incorrect verifier pruning in BPF in Linux Kernel >=5.4 leads to unsafe
code paths being incorrectly marked as safe,
Incorrect verifier pruning in BPF in Linux Kernel >=5.4 leads to unsafe code paths being incorrectly marked as safe, resulting in arbitrary read/write in kernel memory, lateral privilege escalation, and container escape.
CRITICAL · CVSS 10
EPSS 0.002
Act now
- Public exploit or PoC is available
- SSVC automatable: yes - attacks can be scripted at scale
- CVSS base score ≥ 7.0
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2023-2163, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
2Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
2Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
⬡
Weakness Classification
CWE-682Incorrect Calculation
CWE-682Incorrect Calculation
▤
Affected Products & Versions
5linux kernel>= 5.3 and < 5.4.242
linux kernel>= 5.5 and < 5.10.179
linux kernel>= 5.11 and < 5.15.109
linux kernel>= 5.16 and < 6.1.26
linux kernel>= 6.2 and < 6.2.13
▤
Affected Packages
33Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
Ubuntu:14.04:LTS
linux
fixed in 3.11.0-12.19
Ubuntu:14.04:LTS
linux-aws
fixed in 4.4.0-1002.2
Ubuntu:14.04:LTS
linux-azure
fixed in 4.15.0-1023.24~14.04.1
Ubuntu:14.04:LTS
linux-lts-xenial
fixed in 4.4.0-13.29~14.04.1
Ubuntu:16.04:LTS
linux
fixed in 4.4.0-2.16
Ubuntu:16.04:LTS
linux-aws
fixed in 4.4.0-1001.10
Ubuntu:16.04:LTS
linux-aws-hwe
fixed in 4.15.0-1030.31~16.04.1
Ubuntu:16.04:LTS
linux-azure
fixed in 4.11.0-1009.9
Ubuntu:16.04:LTS
linux-gcp
fixed in 4.10.0-1004.4
Ubuntu:16.04:LTS
linux-hwe
fixed in 4.8.0-39.42~16.04.1
Ubuntu:16.04:LTS
linux-kvm
fixed in 4.4.0-1004.9
Ubuntu:16.04:LTS
linux-oracle
fixed in 4.15.0-1007.9~16.04.1
Ubuntu:18.04:LTS
linux
fixed in 4.13.0-16.19
Ubuntu:18.04:LTS
linux-aws
fixed in 4.15.0-1001.1
Ubuntu:18.04:LTS
linux-azure-4.15
fixed in 4.15.0-1082.92
Ubuntu:18.04:LTS
linux-gcp-4.15
fixed in 4.15.0-1071.81
Ubuntu:18.04:LTS
linux-kvm
fixed in 4.15.0-1002.2
Ubuntu:18.04:LTS
linux-oem-osp1
fixed in 5.0.0-1010.11
Ubuntu:18.04:LTS
linux-oracle
fixed in 4.15.0-1007.9
Ubuntu:20.04:LTS
linux
fixed in 5.4.0-162.179
Ubuntu:20.04:LTS
linux-aws
fixed in 5.4.0-1109.118
Ubuntu:20.04:LTS
linux-aws-5.11
Ubuntu:20.04:LTS
linux-aws-5.13
Ubuntu:20.04:LTS
linux-aws-5.15
fixed in 5.15.0-1041.46~20.04.1
Ubuntu:20.04:LTS
linux-aws-5.8
Ubuntu:20.04:LTS
linux-azure
fixed in 5.4.0-1115.122
Ubuntu:20.04:LTS
linux-azure-5.11
Ubuntu:20.04:LTS
linux-azure-5.13
Ubuntu:20.04:LTS
linux-azure-5.15
fixed in 5.15.0-1045.52~20.04.1
Ubuntu:20.04:LTS
linux-azure-5.8
Ubuntu:20.04:LTS
linux-azure-fde
Ubuntu:20.04:LTS
linux-azure-fde-5.15
fixed in 5.15.0-1043.50~20.04.1.1
Ubuntu:20.04:LTS
linux-bluefield
fixed in 5.4.0-1070.76
⚠
Public Exploits & PoCs
15These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted.
📦
Fixed versions by distribution
80The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
oracle allbpftool open
oracle allkernel open
oracle allkernel-abi-stablelists open
oracle allkernel-core fixed in 0:4.18.0-513.9.1.el8_9
oracle allkernel-cross-headers fixed in 0:4.18.0-513.9.1.el8_9
oracle allkernel-debug fixed in 0:4.18.0-513.9.1.el8_9
oracle allkernel-debug-core open
oracle allkernel-debug-devel fixed in 0:4.18.0-513.9.1.el8_9
oracle allkernel-debug-modules open
oracle allkernel-debug-modules-extra fixed in 0:4.18.0-513.9.1.el8_9
oracle allkernel-devel open
oracle allkernel-headers open
oracle allkernel-modules fixed in 0:4.18.0-513.9.1.el8_9
oracle allkernel-modules-extra fixed in 0:4.18.0-513.9.1.el8_9
oracle allkernel-tools open
oracle allkernel-tools-libs fixed in 0:4.18.0-513.9.1.el8_9
oracle allkernel-tools-libs-devel fixed in 0:4.18.0-513.9.1.el8_9
oracle allperf fixed in 0:4.18.0-513.9.1.el8_9
oracle allpython3-perf fixed in 0:4.18.0-513.9.1.el8_9
rhel 8bpftool fixed in 0:4.18.0-513.9.1.el8_9
rhel 8kernel open
rhel 8kernel-abi-stablelists open
rhel 8kernel-core fixed in 0:4.18.0-513.9.1.el8_9
rhel 8kernel-debug open
rhel 8kernel-debug-core open
rhel 8kernel-debug-devel fixed in 0:4.18.0-513.9.1.el8_9
rhel 8kernel-debug-modules fixed in 0:4.18.0-513.9.1.el8_9
rhel 8kernel-debug-modules-extra fixed in 0:4.18.0-513.9.1.el8_9
rhel 8kernel-devel fixed in 0:4.18.0-513.9.1.el8_9
rhel 8kernel-modules fixed in 0:4.18.0-513.9.1.el8_9
rhel 8kernel-modules-extra fixed in 0:4.18.0-513.9.1.el8_9
rhel 8kernel-rt open
rhel 8kernel-rt-core open
rhel 8kernel-rt-debug fixed in 0:4.18.0-513.9.1.rt7.311.el8_9
rhel 8kernel-rt-debug-core open
rhel 8kernel-rt-debug-devel fixed in 0:4.18.0-513.9.1.rt7.311.el8_9
rhel 8kernel-rt-debug-kvm open
rhel 8kernel-rt-debug-modules fixed in 0:4.18.0-513.9.1.rt7.311.el8_9
rhel 8kernel-rt-debug-modules-extra fixed in 0:4.18.0-513.9.1.rt7.311.el8_9
rhel 8kernel-rt-devel fixed in 0:4.18.0-513.9.1.rt7.311.el8_9
rhel 8kernel-rt-kvm fixed in 0:4.18.0-513.9.1.rt7.311.el8_9
rhel 8kernel-rt-modules fixed in 0:4.18.0-513.9.1.rt7.311.el8_9
rhel 8kernel-rt-modules-extra fixed in 0:4.18.0-513.9.1.rt7.311.el8_9
rhel 8kernel-tools open
rhel 8kernel-tools-libs fixed in 0:4.18.0-513.9.1.el8_9
rhel 8kernel-tools-libs-devel fixed in 0:4.18.0-513.9.1.el8_9
rhel 8kernel-zfcpdump open
rhel 8kernel-zfcpdump-core fixed in 0:4.18.0-513.9.1.el8_9
rhel 8kernel-zfcpdump-devel open
rhel 8kernel-zfcpdump-modules open
rhel 8kernel-zfcpdump-modules-extra open
rhel 8kpatch-patch-4_18_0-513_5_1 fixed in 0:1-1.el8_9
rhel 8perf open
rhel 8python3-perf fixed in 0:4.18.0-513.9.1.el8_9
suse sle15cluster-md-kmp-rt fixed in 0:5.14.21-150500.13.24.1
suse sle15dlm-kmp-rt fixed in 0:5.14.21-150500.13.24.1
suse sle15gfs2-kmp-rt fixed in 0:5.14.21-150500.13.24.1
suse sle15kernel-64kb fixed in 0:5.14.21-150500.55.36.1
suse sle15kernel-azure fixed in 0:5.14.21-150400.14.72.1
suse sle15kernel-default fixed in 0:5.14.21-150400.24.28.1
suse sle15kernel-default-base fixed in 0:5.3.18-150300.59.141.2.150300.18.82.2
suse sle15kernel-default-devel open
suse sle15kernel-default-extra fixed in 0:5.14.21-150500.55.36.1
suse sle15kernel-default-livepatch fixed in 0:5.14.21-150400.24.97.1
suse sle15kernel-default-man open
suse sle15kernel-devel open
suse sle15kernel-docs fixed in 0:5.3.18-150200.24.169.1
suse sle15kernel-livepatch-5_14_21-150400_15_11-rt fixed in 0:10-150400.2.2-0
suse sle15kernel-livepatch-5_14_21-150400_15_18-rt fixed in 0:9-150400.2.1
suse sle15kernel-livepatch-5_14_21-150400_15_23-rt fixed in 0:8-150400.2.1
suse sle15kernel-livepatch-5_14_21-150400_15_28-rt fixed in 0:8-150400.2.1
suse sle15kernel-livepatch-5_14_21-150400_15_37-rt fixed in 0:5-150400.2.1
suse sle15kernel-livepatch-5_14_21-150400_15_40-rt fixed in 0:5-150400.2.1
suse sle15kernel-livepatch-5_14_21-150400_15_46-rt fixed in 0:4-150400.2.1
suse sle15kernel-livepatch-5_14_21-150400_15_5-rt fixed in 0:12-150400.2.2
suse sle15kernel-livepatch-5_14_21-150400_15_53-rt fixed in 0:3-150400.2.1
suse sle15kernel-livepatch-5_14_21-150400_15_56-rt fixed in 0:2-150400.2.1
suse sle15kernel-livepatch-5_14_21-150400_15_59-rt fixed in 0:1-150400.1.3.1
suse sle15kernel-livepatch-5_14_21-150400_15_8-rt fixed in 0:11-150400.2.2
suse sle15kernel-livepatch-5_14_21-150400_24_28-default fixed in 0:14-150400.2.2-0
▣
Scoring & Timeline
10
CRITICAL · CVSS v3.1 · [email protected]
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Technical impact
total
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
⚑
Vendor Advisories
30🔗
References & Sources
2Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.