cve.bz

CVE-2023-53836 linux linux

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix skb refcnt race after locking changes There is a race where skb's from the sk_psock_backlog can be referenced after userspace side has already skb_consumed() the sk_buff and its refcnt dropped to zer0 causing use after free. The flow is the following: while ((skb = skb_peek(&psock->ingress_skb)) sk_psock_handle_Skb(psock, skb, ..., ingress) if (!ingress) ... sk_psock_skb_ingress sk_psock_skb_ingress_enqueue(skb) msg->skb = skb sk_psock_queue_msg(psock, msg) skb_dequeue(&psock->ingress_skb) The sk_psock_queue_msg() puts the msg on the ingress_msg queue. This is what the application reads when recvmsg() is called. An application can read this anytime after the msg is placed on the queue. The recvmsg hook will also read msg->skb and then after user space reads the msg will call consume_skb(skb) on it effectively free'ing it. But, the race is in above where backlog queue still has a reference to the skb and calls skb_dequeue(). If the skb_dequeue happens after the user reads and free's the skb we have a use after free. The !ingress case does not suffer from this problem because it uses sendmsg_*(sk, msg) which does not pass the sk_buff further down the stack. The following splat was observed with 'test_progs -t sockmap_listen': [ 1022.710250][ T2556] general protection fault, ... [...] [ 1022.712830][ T2556] Workqueue: events sk_psock_backlog [ 1022.713262][ T2556] RIP: 0010:skb_dequeue+0x4c/0x80 [ 1022.713653][ T2556] Code: ... [...] [ 1022.720699][ T2556] Call Trace: [ 1022.720984][ T2556] <TASK> [ 1022.721254][ T2556] ? die_addr+0x32/0x80^M [ 1022.721589][ T2556] ? exc_general_protection+0x25a/0x4b0 [ 1022.722026][ T2556] ? asm_exc_general_protection+0x22/0x30 [ 1022.722489][ T2556] ? skb_dequeue+0x4c/0x80 [ 1022.722854][ T2556] sk_psock_backlog+0x27a/0x300 [ 1022.723243][ T2556] process_one_work+0x2a7/0x5b0 [ 1022.723633][ T2556] worker_thread+0x4f/0x3a0 [ 1022.723998][ T2556] ? __pfx_worker_thread+0x10/0x10 [ 1022.724386][ T2556] kthread+0xfd/0x130 [ 1022.724709][ T2556] ? __pfx_kthread+0x10/0x10 [ 1022.725066][ T2556] ret_from_fork+0x2d/0x50 [ 1022.725409][ T2556] ? __pfx_kthread+0x10/0x10 [ 1022.725799][ T2556] ret_from_fork_asm+0x1b/0x30 [ 1022.726201][ T2556] </TASK> To fix we add an skb_get() before passing the skb to be enqueued in the engress queue. This bumps the skb->users refcnt so that consume_skb() and kfree_skb will not immediately free the sk_buff. With this we can be sure the skb is still around when we do the dequeue. Then we just need to decrement the refcnt or free the skb in the backlog case which we do by calling kfree_skb() on the ingress case as well as the sendmsg case. Before locking change from fixes tag we had the sock locked so we couldn't race with user and there was no issue here.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 10th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.15.189
  • Linux Linux: fixed in 6.1.54
  • Linux Linux: fixed in 6.5.4
  • Linux Linux: fixed in 6.6
  • Debian, Ubuntu, SUSE, openSUSE, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2023-53836 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-53836?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-53836?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-53836 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2023-53836

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2023-53836](https://cve.bz/cve/badge/CVE-2023-53836.svg)](https://cve.bz/cve/CVE-2023-53836)

HTML:

<a href="https://cve.bz/cve/CVE-2023-53836"><img src="https://cve.bz/cve/badge/CVE-2023-53836.svg" alt="CVE-2023-53836"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.13 and later

Fixed in

ProductRelease lineFixed in
Linux5.155.15.189
Linux6.16.1.54
Linux6.56.5.4
Linuxlater releases6.6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.55-1DEBIAN-CVE-2023-53836
Debian13, 14linux6.5.6-1DEBIAN-CVE-2023-53836
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2023-53836
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2023-53836
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2023-53836
Ubuntu22.04:LTSlinux, linux-lowlatency5.15.0-156.166UBUNTU-CVE-2023-53836
Ubuntu22.04:LTSlinux-aws5.15.0-1092.99UBUNTU-CVE-2023-53836
Ubuntu22.04:LTSlinux-azure5.15.0-1096.105UBUNTU-CVE-2023-53836
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1096.105.1UBUNTU-CVE-2023-53836
Ubuntu22.04:LTSlinux-gcp5.15.0-1092.101UBUNTU-CVE-2023-53836
Ubuntu22.04:LTSlinux-gke5.15.0-1089.95UBUNTU-CVE-2023-53836
Ubuntu22.04:LTSlinux-gkeop5.15.0-1075.83UBUNTU-CVE-2023-53836
Ubuntu22.04:LTSlinux-ibm, linux-raspi5.15.0-1086.89UBUNTU-CVE-2023-53836
Ubuntu22.04:LTSlinux-intel-iotg5.15.0-1087.93UBUNTU-CVE-2023-53836
25 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP6, Linux Enterprise Live Patching 15 SP6kernel-default6.4.0-150600.23.84.1SUSE-SU-2026:0293-1
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.28.1SUSE-SU-2026:0315-1
SUSELinux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_191-150600.13.3.1SUSE-SU-2026:0293-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_81-150700.1.3.1SUSE-SU-2026:0278-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_81-150700.15.3.1SUSE-SU-2026:0315-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-64kb, kernel-source, kernel-default and 1 more6.4.0-150700.53.28.1SUSE-SU-2026:0315-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-default-base6.4.0-150700.53.28.1.150700.17.19.1SUSE-SU-2026:0315-1
SUSELinux Enterprise Module for Development Tools 15 SP7kernel-docs, kernel-syms, kernel-source and 1 more6.4.0-150700.53.28.1SUSE-SU-2026:0315-1
SUSELinux Enterprise Module for Public Cloud 15 SP7kernel-azure, kernel-syms-azure, kernel-source-azure6.4.0-150700.20.24.1SUSE-SU-2026:0281-1
SUSELinux Enterprise Server 15 SP6-LTSSkernel-64kb, kernel-docs, kernel-syms and 4 more6.4.0-150600.23.84.1SUSE-SU-2026:0293-1
SUSELinux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6kernel-default-base6.4.0-150600.23.84.1.150600.12.38.1SUSE-SU-2026:0293-1
SUSELinux Enterprise Server for SAP Applications 15 SP6kernel-docs, kernel-syms, kernel-source and 2 more6.4.0-150600.23.84.1SUSE-SU-2026:0293-1
7 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 15.6dtb-aarch64, kernel-64kb, kernel-docs and 8 more6.4.0-150600.23.84.1SUSE-SU-2026:0293-1
openSUSELeap 15.6kernel-default-base6.4.0-150600.23.84.1.150600.12.38.1SUSE-SU-2026:0293-1
Alpaquita23linux-lts6.1.54-r0BELL-CVE-2023-53836
Alpaquitastreamlinux-lts6.6.58-r0BELL-CVE-2023-53836

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

This is a use-after-free vulnerability in the BPF sockmap subsystem that can cause kernel crashes. The vulnerability requires the use of BPF sockmap programs and specific socket configurations.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-53836.

References

Check your stackJSON