CVE-2022-21499: Medium severity Oracle Linux vulnerability

Published May 11, 2022
·
Updated

A flaw was found in kernel/debug/debugcore.c in the Linux kernel in the lockdown mode. In this flaw, an attacker with local access could trigger the debugger, bypass lockdown and write anonymously.

In this flaw, KGDB and KDB allow read and write access to kernel memory, and thus should not be allowed during lockdown. An attacker with access to a serial port could trigger the debugger and use it to bypass lockdown.

Reference: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eadb2f47a3ced5c64b23b90fd2a3463f63726066

Other sources

A flaw was found in the kernel/debug/debugcore.c in the Linux kernel in lockdown mode. This flaw allows an attacker with local access to trigger the debugger, bypass lockdown and write anonymously.

KGDB and KDB allow read and write access to kernel memory, and thus should be restricted during lockdown. An attacker with access to a serial port could trigger the debugger so it is important that the debugger respect the lockdown mode when/if it is triggered. CVSS 3.1 Base Score 6.7 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).

Affected Software

10 affected componentsFixes available
redhat/kernel-rt<0:4.18.0-425.3.1.rt7.213.el8
0:4.18.0-425.3.1.rt7.213.el8
redhat/kernel<0:4.18.0-425.3.1.el8
0:4.18.0-425.3.1.el8
redhat/kernel<0:5.14.0-162.6.1.el9_1
0:5.14.0-162.6.1.el9_1
redhat/kernel-rt<0:5.14.0-162.6.1.rt21.168.el9_1
0:5.14.0-162.6.1.rt21.168.el9_1
Oracle Linux=6
Oracle Linux=7
Oracle Linux=8
Debian Debian Linux=11.0
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
redhat/kernel<5.19
5.19

Remediation

Information

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Event History

May 11, 2022
Data Sourced
via Red Hat·03:30 PM
DescriptionSeverityAffected Software
May 24, 2022
CVE Published
05:00 PM
Jun 9, 2022
CVE Published
via MITRE·08:15 PM
Data Sourced
via MITRE·08:15 PM
DescriptionSeverityWeakness
Jan 12, 2024
Data Sourced
via Launchpad·12:07 AM
Description
Apr 28, 2025
Data Sourced
via Ubuntu·04:37 AM
RemedyDescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2022-21499?

CVE-2022-21499 is considered a high severity vulnerability due to its potential to allow local attackers to bypass lockdown mode and write to kernel memory.

2

How do I fix CVE-2022-21499?

To fix CVE-2022-21499, update to the latest kernel versions provided, such as kernel-rt version 0:4.18.0-425.3.1.rt7.213.el8 or kernel version 0:5.14.0-162.6.1.el9_1.

3

What systems are affected by CVE-2022-21499?

CVE-2022-21499 affects various Linux distributions, including Red Hat, Oracle Linux, and Debian, particularly versions under the kernel package.

4

Can CVE-2022-21499 be exploited remotely?

No, CVE-2022-21499 requires local access to the system to exploit, meaning an attacker must have physical or SSH access to the affected machine.

5

What is the impact of CVE-2022-21499 on system security?

The impact of CVE-2022-21499 on system security is significant as it allows an attacker to bypass kernel lockdown protections, potentially leading to unauthorized access and manipulation of kernel memory.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203