dbcve.org
LinuxOperating system · Oracle

CVE-2023-22024

MEDIUM · 5.5 CVSS v3.1 Published 2023-09-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Unbreakable Enterprise Kernel (UEK), the RDS module in UEK has two setsockopt(2) options, RDS_CONN_RESET and RDS6_CONN_RESET, that are not re-entrant. A malicious local user with CAP_NET_ADMIN can use this to crash the kernel. CVSS 3.1 Base Score 5.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Oracle's Unbreakable Enterprise Kernel (UEK), the RDS (Reliable Datagram Socket) module contains two setsockopt(2) options—RDS_CONN_RESET and RDS6_CONN_RESET—that lack re-entrancy protection. A local user with CAP_NET_ADMIN capability can trigger these options concurrently, causing a race condition that leads to kernel crash (denial of service).

MitigationRestrict CAP_NET_ADMIN capability to trusted users/processes only. Apply Oracle's patches for UEK when available. As a defensive measure, disable the RDS module if not required via kernel module configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LinuxOperating system
Affected:= 6= 7= 8= 9
Vm ServerApplication
Affected:= 3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the operating system product and version
    Run 'cat /etc/oracle-release' for Oracle Linux or 'cat /etc/vmware-release' for Oracle VM Server. Also check 'uname -a' for the UEK kernel version.
    Affected if The system is Oracle Linux versions 6, 7, 8, or 9, or Oracle VM Server version 3.0, running the Unbreakable Enterprise Kernel.
  2. Determine if the RDS kernel module is loaded
    Run 'lsmod | grep rds' to check if the RDS module is currently loaded. Also check /proc/modules for 'rds' entry.
    Affected if The RDS module is loaded into the kernel, making the vulnerable setsockopt options (RDS_CONN_RESET, RDS6_CONN_RESET) accessible.
  3. Check which users or processes hold CAP_NET_ADMIN capability
    Run 'capsh --print' or check /proc/<pid>/status for capability sets. Review 'getcap -r /' output and audit logs for CAP_NET_ADMIN assignment.
    Affected if Untrusted local users or processes have CAP_NET_ADMIN capability, enabling them to trigger the vulnerable setsockopt options.
  4. Inspect for kernel crash logs related to RDS race conditions
    Check 'dmesg', /var/log/messages, /var/log/kern.log, or 'journalctl -k' for kernel oops, panic, or crash entries mentioning 'RDS', 'rds', 'conn_reset', or 'race condition'.
    Affected if Kernel crashes or oops messages involving RDS are present, indicating possible exploitation of the CVE.

You are affected if you are running Oracle Linux 6/7/8/9 or Oracle VM Server 3.0 with the RDS module loaded and untrusted users have CAP_NET_ADMIN capability, or if you observe RDS-related kernel crashes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict CAP_NET_ADMIN capability to trusted users/processes only. Apply Oracle's patches for UEK when available. As a defensive measure, disable the RDS module if not required via kernel module configuration.

Recommended fix Moderate confidence

Oracle Unbreakable Enterprise Kernel (UEK) version that includes the fix for CVE-2023-22024 - consult Oracle Linux errata for specific version

  1. Check the current running kernel version with 'uname -r'
  2. Update the Oracle Linux system with 'yum update' or 'dnf update' to receive the latest UEK kernel packages
  3. Reboot the system to boot into the updated kernel using 'reboot'
  4. Verify the fix is applied by checking the kernel version and confirming the RDS module no longer has the race condition (uname -r should show a kernel version that includes the security fix)
Caveat Kernel updates may require system reboot and could potentially introduce compatibility issues with third-party kernel modules

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22024 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-22024 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data