Vulnerability · Published May 2, 2025 · Assigned by Linux

CVE-2023-53136af_unix: fix struct pid leaks in OOB support

High 7.1

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 9% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)7.1High
Exploit odds (30 days)0.2%top 90.8% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: af_unix: fix struct pid leaks in OOB support syzbot reported struct pid leak [1]. Issue is that queue_oob() calls maybe_add_creds() which potentially holds a reference on a pid. But skb->destructor is not set (either directly or by calling unix_scm_to_skb()) This means that subsequent kfree_skb() or consume_skb() would leak this reference. In this fix, I chose to fully support scm even for the OOB message. [1] BUG: memory leak unreferenced object 0xffff8881053e7f80 (size 128): comm "syz-executor242", pid 5066, jiffies 4294946079 (age 13.220s) hex dump (first 32 bytes): 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffff812ae26a>] alloc_pid+0x6a/0x560 kernel/pid.c:180 [<ffffffff812718df>] copy_process+0x169f/0x26c0 kernel/fork.c:2285 [<ffffffff81272b37>] kernel_clone+0xf7/0x610 kernel/fork.c:2684 [<ffffffff812730cc>] __do_sys_clone+0x7c/0xb0 kernel/fork.c:2825 [<ffffffff849ad699>] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [<ffffffff849ad699>] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 [<ffffffff84a0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.20-1DEBIAN-CVE-2023-53136
Debian:13linux6.1.20-1DEBIAN-CVE-2023-53136
Debian:14linux6.1.20-1DEBIAN-CVE-2023-53136
Ubuntu:22.04:LTSlinux5.15.0-79.86UBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-aws5.15.0-1042.47UBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-azure5.15.0-1045.52UBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1045.52.1UBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-gcp5.15.0-1039.47UBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-gke5.15.0-1039.44UBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1025.30UBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-ibm5.15.0-1035.38UBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1037.42UBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-kvm5.15.0-1039.44UBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-79.88UBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1030.30UBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1016.16UBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1002.2UBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-oracle5.15.0-1040.46UBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-raspi5.15.0-1035.38UBUNTU-CVE-2023-53136
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-53136
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2023-53136
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1025.29UBUNTU-CVE-2023-53136

Affected products (as reported)

VendorProductVersions
Linux Linux 314001f0bf927015e459c9d387d62a231fe93af3 – before f3969427fb06a2c3cd6efd7faab63505cfa76e76314001f0bf927015e459c9d387d62a231fe93af3 – before ac1968ac399205fda9ee3b18f7de7416cb3a5d0d314001f0bf927015e459c9d387d62a231fe93af3 – before a59d6306263c38e5c0592ea4451ca26a0778c947314001f0bf927015e459c9d387d62a231fe93af3 – before 2aab4b96900272885bc157f8b236abf1cdc02e08
Linux Linux 5.15

References