CVE-2023-52676
Linux kernel: integer overflow
- Risk score
- 51/100
- CVSS
- 5.5 v3.1
- Exploit chance (30 days)
- 0.2%
- Published
- 17 May 2024
Open in the live forecast Today's forecast
What to know
- What it is
- In the Linux kernel, the following vulnerability has been resolved: bpf: Guard stack limits against 32bit overflow This patch promotes the arithmetic around checking stack bounds to be done in the 64-bit domain, instead of the current 32bit. The arithmetic implies adding together a 64-bit register with a int offset. T…
- Affected
- Linux kernel
- Fix
- Apply the vendor's security update; see the linked advisory.
- Exploitation
- No known exploitation
Story map
At a glance
Linux kernel: Amber, patch this week. In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: restore network header before routing and forwarding ipv6_srh_rcv() runs with skb->data at the Segment Routing Header (SRH) while skb_network_header() points at the IPv6 header. When segments_left > 0, ipv6_srh_rcv() previously restored the …
The flaws
- CVE-2023-52676: Integer overflow (CVSS 5.5 · EPSS 0%)
- CVE-2026-98096: Out-of-bounds write (CVSS 7.4 · EPSS 1%)
- CVE-2026-98115: Race condition (CVSS 8.8 · EPSS 0%)
- CVE-2026-98117: Use-after-free (CVSS 7.8 · EPSS 0%)
The fix
Fix: Apply the vendor's security update; see the linked advisory.
Who is exposed: Linux kernel
Where it stands
- No known exploitation
How it unfolded
- 3 Nov, Ubuntu security notices (official): USN-8962-1: Linux kernel (Azure CVM) vulnerabilities
- 3 Nov, Ubuntu security notices (official): USN-8963-1: Linux kernel (NVIDIA Tegra) vulnerabilities
- 3 Nov, Ubuntu security notices (official): USN-8961-1: Linux kernel vulnerabilities
Connects to
- Same weakness: Integer overflow (CWE-190). 158 other warnings in 30 days
- Same product: Earlier Linux kernel warnings. 105 in the last 90 days
Why it is Yellow
- CVSS 5.5 medium
- On your watchlist: linux kernel
- Named in a government or vendor bulletin
Government and vendor bulletins
References
- https://ubuntu.com/security/notices/USN-8961-1
- https://ubuntu.com/security/notices/USN-8963-1
- https://ubuntu.com/security/notices/USN-8962-1
- https://git.kernel.org/stable/c/1d38a9ee81570c4bd61f557832dead4d6f816760
- https://git.kernel.org/stable/c/4ba97610399e83d29d1086a0827d33172539b49b
- https://git.kernel.org/stable/c/ad140fc856f0b1d5e2215bcb6d0cc247a86805a2
- https://git.kernel.org/stable/c/ad1754f86a87fe74912fb542b23ff24ada4e3307
- https://git.kernel.org/stable/c/e160b2ed94a20fa940369ebd914277f88005e70d
- https://git.kernel.org/stable/c/e5ad9ecb84405637df82732ee02ad741a5f782a6
- https://git.kernel.org/stable/c/1d38a9ee81570c4bd61f557832dead4d6f816760
Original description
In the Linux kernel, the following vulnerability has been resolved: bpf: Guard stack limits against 32bit overflow This patch promotes the arithmetic around checking stack bounds to be done in the 64-bit domain, instead of the current 32bit. The arithmetic implies adding together a 64-bit register with a int offset. The register was checked to be below 1<<29 when it was variable, but not when it was fixed. The offset either comes from an instruction (in which case it is 16 bit), from another register (in which case the caller checked it to be below 1<<29 [1]), or from the size of an argument to a kfunc (in which case it can be a u32 [2]). Between the register being inconsistently checked to be below 1<<29, and the offset being up to an u32, it appears that we were open to overflowing the `int`s which were currently used for arithmetic. [1] https://github.com/torvalds/linux/blob/815fb87b753055df2d9e50f6cd80eb10235fe3e9/kernel/bpf/verifier.c#L7494-L7498 [2] https://github.com/torvalds/linux/blob/815fb87b753055df2d9e50f6cd80eb10235fe3e9/kernel/bpf/verifier.c#L11904
Last activity 3 Nov 2026. Patch Forecast updates every hour.