dbcve.org
Linux KernelOperating system · Linux

CVE-2023-1032

MEDIUM · 5.5 CVSS v3.1 Published 2024-01-08
Fix available
A fix is available. Upgrade to 6.3 or later.
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
The Linux kernel io_uring IORING_OP_SOCKET operation contained a double free in function __sys_socket_file() in file net/socket.c. This issue was introduced in da214a475f8bd1d3e9e7a19ddfeb4d1617551bab and fixed in 649c15c7691e9b13cbe9bf6c65c365350e056067.

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

The Linux kernel io_uring IORING_OP_SOCKET operation contains a double-free vulnerability in the __sys_socket_file() function in net/socket.c. This memory corruption issue allows a local attacker to potentially cause denial of service or escalate privileges through repeated exploitation of the double-free condition.

MitigationApply the kernel patch from commit 649c15c7691e9b13cbe9bf6c65c365350e056067 or update to a kernel version containing this fix. Organizations using io_uring with socket operations should prioritize this update given the memory corruption potential.

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
Linux KernelOperating system
Affected:>= 5.19, < 6.3= 6.3
Ubuntu LinuxOperating system
Affected:= 22.04= 22.10

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. Check the running kernel version
    Run 'uname -r' or 'cat /proc/version' to identify the kernel version
    Affected if The version is 5.19.x, 6.0.x, 6.1.x, 6.2.x, or exactly 6.3.x (these fall within >= 5.19 and < 6.3 or equal 6.3)
  2. Verify io_uring is available
    Check for the io_uring interface by looking for /dev/io_uring or run 'lsmod | grep io_uring' to see if the module is loaded
    Affected if io_uring is present and loadable on the system, making the vulnerable code path reachable
  3. Confirm socket support in io_uring
    Check if the kernel was compiled with CONFIG_IO_URING and CONFIG_NET (run 'grep -E "CONFIG_IO_URING|CONFIG_NET" /boot/config-$(uname -r)' or check /proc/config.gz if available)
    Affected if Both CONFIG_IO_URING and CONFIG_NET are enabled, which exposes the __sys_socket_file() function through io_uring syscalls
  4. Monitor for IORING_OP_SOCKET usage
    Review application code or system audit logs for usage of io_uring_setup with IORING_OP_SOCKET, or use 'strace' to trace io_uring_enter calls mentioning socket operations
    Affected if Applications are actively using io_uring to perform socket operations, which directly triggers the vulnerable __sys_socket_file() code path

The system is affected if it runs a kernel version 5.19 through 6.3 inclusive AND has io_uring with socket operations enabled or in use.

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
Upgrade available Upgrade to 6.3 or later
Fixed in 6.3
Interim mitigation

Apply the kernel patch from commit 649c15c7691e9b13cbe9bf6c65c365350e056067 or update to a kernel version containing this fix. Organizations using io_uring with socket operations should prioritize this update given the memory corruption potential.

Recommended fix Moderate confidence

Linux Kernel >= 6.4; Ubuntu 22.04 HWE kernel >= 5.15.0-104; Ubuntu 22.10 kernel >= 5.19.0-50

  1. 1. Identify the current running kernel version using 'uname -r'
  2. 2. For Ubuntu 22.04 (Jammy), upgrade to a kernel version that includes the fix. Ubuntu kernel versions are typically prefixed with '5.15.0-xx' or similar. Check for available kernel updates via 'apt update && apt-cache policy linux-image-generic'
  3. 3. For Ubuntu 22.10 (Kinetic), upgrade to a kernel version that includes the fix. Check available kernels via 'apt update && apt-cache policy linux-image-generic'
  4. 4. Install the updated kernel package: 'sudo apt-get install linux-image-<version>'
  5. 5. Reboot the system to load the new kernel: 'sudo reboot'
  6. 6. Verify the new kernel is running and the vulnerability is addressed by checking the kernel version matches a fixed release (Linux kernel >= 6.4 or Ubuntu kernel with patch applied)
Caveat Kernel upgrades may require system reboot and could have compatibility implications with third-party kernel modules

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

Fix this in Linux Kernel 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 the upgrade done

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-1032 — 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-1032 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