CVE-2023-21102: In __efi_rt_asm_wrapper of efi-rt-wrapper.S, there is a possible bypass of shadow stack protection due to a logic error in the code.
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: cbl2 hyperv-daemons 5.15.118.1-1 on CBL Mariner 2.0 5.15.118.1-1.
- Mentioned 3 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to cbl2 hyperv-daemons 5.15.118.1-1 on CBL Mariner 2.0 5.15.118.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In __efi_rt_asm_wrapper of efi-rt-wrapper.S, there is a possible bypass of shadow stack protection due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-260821414References: Upstream kernel
- Published
- May 15, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-754
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| android | cpe:2.3:o:google:android |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (google_android). Independent of NVD's CPE analysis and usually ahead of it.
n/a Android
- Android kernelaffected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- google androidall versions
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | bpftool | before 7.0.0-284.30.1.el9_2 | 7.0.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-core | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
| AlmaLinux:9 | kernel-debug-modules-core | before 5.14.0-284.30.1.el9_2 | 5.14.0-284.30.1.el9_2 |
+96
Same product
google: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-2215A use-after-free in binder.c allows an elevation of privilege from an application to the Linux Kernel.KEV83Now
- CVE-2011-1823The vold volume manager daemon on Android 3.0 and 2.x before 2.3.4 trusts messages that are received from a PF_NETLINK socket, which allows…KEV73This week
- CVE-2015-1538Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android before 5.1.1 LMY48I…70This week
Published before and after this one in the same product
- ← EarlierCVE-2023-20914May 15, 2023 · In onSetRuntimePermissionGrantStateByDeviceAdmin of AdminRestrictedPermissionsUtils.java, there is a possible way for the work profile to…22Monitor
- ← EarlierCVE-2023-20930May 15, 2023 · In pushDynamicShortcut of ShortcutPackage.java, there is a possible way to get the device into a boot loop due to resource exhaustion.22Monitor
- Later →CVE-2023-21103May 15, 2023 · In registerPhoneAccount of PhoneAccountRegistrar.java, uncaught exceptions in parsing persisted user data could lead to local persistent…22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| cbl2 hyperv-daemons 5.15.118.1-1 on CBL Mariner 2.0 | 5.15.118.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:bpftool | 7.0.0-284.30.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel | 5.14.0-284.30.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-284.30.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-284.30.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-284.30.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-284.30.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-284.30.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-284.30.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-284.30.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-284.30.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-284.30.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-284.30.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.8-1 · Debian:12 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 5.14.21-150400.24.69.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:kernel-64kb | 5.14.21-150400.24.69.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:kernel-debug | 5.14.21-150400.24.69.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:kernel-default | 5.14.21-150400.24.69.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:kernel-default-base | 5.14.21-150400.24.69.1.150400.24.31.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:kernel-docs | 5.14.21-150400.24.69.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 5.14.21-150400.24.69.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:kernel-obs-build | 5.14.21-150400.24.69.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:kernel-rt | 5.14.21-150400.15.37.2 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:kernel-rt_debug | 5.14.21-150400.15.37.2 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:kernel-source-rt | 5.14.21-150400.15.37.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:kernel-syms-rt | 5.14.21-150400.15.37.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.0.0-284.30.1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-284.30.1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-284.30.1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-284.30.1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+21
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0391 · Jul 10, 2023(Linux Kernel Güncellemesi)
- TR-23-0271 · May 17, 2023(Linux Kernel Güncellemesi)
- TR-23-0253 · May 2, 2023(Google Android Güvenlik Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-754 · Improper Check for Unusual or Exceptional ConditionsCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →