Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2023-52986 on Ubuntu — linux

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener A listening socket linked to a sockmap has its sk_prot overridden. It points to one of the struct proto variants in tcp_bpf_prots. The variant depends on the socket's family and which sockmap programs are attached. A child socket cloned from a TCP listener initially inherits their sk_prot. But before cloning is finished, we restore the child's proto to the listener's original non-tcp_bpf_prots one. This happens in tcp_create_openreq_child -> tcp_bpf_clone. Today, in tcp_bpf_clone we detect if the child's proto should be restored by checking only for the TCP_BPF_BASE proto variant. This is not correct. The sk_prot of listening socket linked to a sockmap can point to to any variant in tcp_bpf_prots. If the listeners sk_prot happens to be not the TCP_BPF_BASE variant, then the child socket unintentionally is left if the inherited sk_prot by tcp_bpf_clone. This leads to issues like infinite recursion on close [1], because the child state is otherwise not set up for use with tcp_bpf_prot operations. Adjust the check in tcp_bpf_clone to detect all of tcp_bpf_prots variants. Note that it wouldn't be sufficient to check the socket state when overriding the sk_prot in tcp_bpf_update_proto in order to always use the TCP_BPF_BASE variant for listening sockets. Since commit b8b8315e39ff ("bpf, sockmap: Remove unhash handler for BPF sockmap usage") it is possible for a socket to transition to TCP_LISTEN state while already linked to a sockmap, e.g. connect() -> insert into map -> connect(AF_UNSPEC) -> listen(). [1]: https://lore.kernel.org/all/[email protected]/

Distribution advisory

This page covers CVE-2023-52986 as tracked by Ubuntu, for the package linux. The fix is available in version 5.15.0-72.79; earlier versions remain affected.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: None.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

UBUNTU-CVE-2023-52986 is recorded against 96 packages.

  • linux (fixed in 5.15.0-72.79)
  • linux-allwinner-5.19
  • linux-aws (fixed in 5.15.0-1036.40)
  • linux-aws-5.0
  • linux-aws-5.11
  • linux-aws-5.13
  • linux-aws-5.15 (fixed in 5.15.0-1036.40~20.04.1)
  • linux-aws-5.19
  • linux-aws-5.3
  • linux-aws-5.8
  • linux-aws-6.2
  • linux-aws-6.5
  • linux-azure (fixed in 5.15.0-1038.45)
  • linux-azure-5.11
  • linux-azure-5.13
  • linux-azure-5.15 (fixed in 5.15.0-1038.45~20.04.1)
  • linux-azure-5.19
  • linux-azure-5.3
  • linux-azure-5.8
  • linux-azure-6.2
  • linux-azure-6.5
  • linux-azure-edge
  • linux-azure-fde
  • linux-azure-fde-5.19
Show the remaining 72 packages
  • linux-azure-fde-6.2
  • linux-bluefield
  • linux-gcp (fixed in 5.15.0-1034.42)
  • linux-gcp-5.11
  • linux-gcp-5.13
  • linux-gcp-5.15 (fixed in 5.15.0-1034.42~20.04.1)
  • linux-gcp-5.19
  • linux-gcp-5.3
  • linux-gcp-5.8
  • linux-gcp-6.2
  • linux-gcp-6.5
  • linux-gke (fixed in 5.15.0-1033.38)
  • linux-gke-4.15
  • linux-gke-5.15
  • linux-gke-5.4
  • linux-gkeop (fixed in 5.15.0-1020.25)
  • linux-gkeop-5.15
  • linux-gkeop-5.4
  • linux-hwe
  • linux-hwe-5.11
  • linux-hwe-5.13
  • linux-hwe-5.15 (fixed in 5.15.0-72.79~20.04.1)
  • linux-hwe-5.19
  • linux-hwe-5.8
  • linux-hwe-6.2
  • linux-hwe-6.5
  • linux-hwe-edge
  • linux-ibm (fixed in 5.15.0-1030.33)
  • linux-intel-5.13
  • linux-intel-iot-realtime (fixed in 5.15.0-1028.33)
  • linux-intel-iotg (fixed in 5.15.0-1030.35)
  • linux-intel-iotg-5.15 (fixed in 5.15.0-1030.35~20.04.1)
  • linux-kvm (fixed in 5.15.0-1033.38)
  • linux-lowlatency (fixed in 5.15.0-72.79)
  • linux-lowlatency-hwe-5.15 (fixed in 5.15.0-72.79~20.04.1)
  • linux-lowlatency-hwe-5.19
  • linux-lowlatency-hwe-6.2
  • linux-lowlatency-hwe-6.5
  • linux-nvidia (fixed in 5.15.0-1025.25)
  • linux-nvidia-6.2
  • linux-nvidia-6.5
  • linux-nvidia-tegra-5.15 (fixed in 5.15.0-1014.14~20.04.1)
  • linux-oem
  • linux-oem-5.10
  • linux-oem-5.13
  • linux-oem-5.14
  • linux-oem-5.17
  • linux-oem-5.6
  • linux-oem-6.0
  • linux-oem-6.1
  • linux-oem-6.5
  • linux-oracle (fixed in 5.15.0-1035.41)
  • linux-oracle-5.0
  • linux-oracle-5.11
  • linux-oracle-5.13
  • linux-oracle-5.15 (fixed in 5.15.0-1035.41~20.04.1)
  • linux-oracle-5.3
  • linux-oracle-5.8
  • linux-oracle-6.5
  • linux-raspi (fixed in 5.15.0-1029.31)
  • linux-raspi-realtime
  • linux-raspi2
  • linux-realtime
  • linux-riscv
  • linux-riscv-5.11
  • linux-riscv-5.15 (fixed in 5.15.0-1033.37~20.04.1)
  • linux-riscv-5.19
  • linux-riscv-5.8
  • linux-riscv-6.5
  • linux-starfive-5.19
  • linux-starfive-6.2
  • linux-starfive-6.5

Timeline and source

Published on 27 March 2025 and last revised on 17 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

ubuntu.com (Report)
www.cve.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)

Other advisories for this package

linux has other advisories on record. If you are patching this one, these are worth checking on the same host:

CVE-2023-52986 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2025-03-27
Updated 2026-08-20
Modified 2026-08-17
Fix URL N/A

Affected Packages

Software From version Fixed in
linux — 5.15.0-72.79
linux-allwinner-5.19 — —
linux-aws — 5.15.0-1036.40
linux-aws-5.0 — —
linux-aws-5.11 — —
linux-aws-5.13 — —
linux-aws-5.15 — 5.15.0-1036.40~20.04.1
linux-aws-5.19 — —
linux-aws-5.3 — —
linux-aws-5.8 — —
linux-aws-6.2 — —
linux-aws-6.5 — —
linux-azure — 5.15.0-1038.45
linux-azure-5.11 — —
linux-azure-5.13 — —
linux-azure-5.15 — 5.15.0-1038.45~20.04.1
linux-azure-5.19 — —
linux-azure-5.3 — —
linux-azure-5.8 — —
linux-azure-6.2 — —
linux-azure-6.5 — —
linux-azure-edge — —
linux-azure-fde — —
linux-azure-fde-5.19 — —
linux-azure-fde-6.2 — —
linux-bluefield — —
linux-gcp — 5.15.0-1034.42
linux-gcp-5.11 — —
linux-gcp-5.13 — —
linux-gcp-5.15 — 5.15.0-1034.42~20.04.1
linux-gcp-5.19 — —
linux-gcp-5.3 — —
linux-gcp-5.8 — —
linux-gcp-6.2 — —
linux-gcp-6.5 — —
linux-gke — 5.15.0-1033.38
linux-gke-4.15 — —
linux-gke-5.15 — —
linux-gke-5.4 — —
linux-gkeop — 5.15.0-1020.25
linux-gkeop-5.15 — —
linux-gkeop-5.4 — —
linux-hwe — —
linux-hwe-5.11 — —
linux-hwe-5.13 — —
linux-hwe-5.15 — 5.15.0-72.79~20.04.1
linux-hwe-5.19 — —
linux-hwe-5.8 — —
linux-hwe-6.2 — —
linux-hwe-6.5 — —
linux-hwe-edge — —
linux-ibm — 5.15.0-1030.33
linux-intel-5.13 — —
linux-intel-iot-realtime — 5.15.0-1028.33
linux-intel-iotg — 5.15.0-1030.35
linux-intel-iotg-5.15 — 5.15.0-1030.35~20.04.1
linux-kvm — 5.15.0-1033.38
linux-lowlatency — 5.15.0-72.79
linux-lowlatency-hwe-5.15 — 5.15.0-72.79~20.04.1
linux-lowlatency-hwe-5.19 — —
linux-lowlatency-hwe-6.2 — —
linux-lowlatency-hwe-6.5 — —
linux-nvidia — 5.15.0-1025.25
linux-nvidia-6.2 — —
linux-nvidia-6.5 — —
linux-nvidia-tegra-5.15 — 5.15.0-1014.14~20.04.1
linux-oem — —
linux-oem-5.10 — —
linux-oem-5.13 — —
linux-oem-5.14 — —
linux-oem-5.17 — —
linux-oem-5.6 — —
linux-oem-6.0 — —
linux-oem-6.1 — —
linux-oem-6.5 — —
linux-oracle — 5.15.0-1035.41
linux-oracle-5.0 — —
linux-oracle-5.11 — —
linux-oracle-5.13 — —
linux-oracle-5.15 — 5.15.0-1035.41~20.04.1
linux-oracle-5.3 — —
linux-oracle-5.8 — —
linux-oracle-6.5 — —
linux-raspi — 5.15.0-1029.31
linux-raspi-realtime — —
linux-raspi2 — —
linux-realtime — —
linux-riscv — —
linux-riscv-5.11 — —
linux-riscv-5.15 — 5.15.0-1033.37~20.04.1
linux-riscv-5.19 — —
linux-riscv-5.8 — —
linux-riscv-6.5 — —
linux-starfive-5.19 — —
linux-starfive-6.2 — —
linux-starfive-6.5 — —

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in linux

UBUNTU-CVE-2023-52986 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesUbuntuUbuntu 2023
✓