CVE-2026-53078
What it is
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops When a BPF sock_ops program accesses ctx fields with dst_reg == src_reg, the SOCK_OPS_GET_SK() and SOCK_OPS_GET_FIELD() macros fail to zero the destination register in the !fullsock / !locked_tcp_sock path. Both macros borrow a temporary register to check is_fullsock / is_locked_tcp_sock when dst_reg == src_reg, because dst_reg holds the ctx pointer. When the check is false (e.g., TCP_NEW_SYN_RECV state with a request_sock), dst_reg should be zeroed but is not, leaving the stale ctx pointer: - SOCK_OPS_GET_SK: dst_reg retains the ctx pointer, passes NULL checks as PTR_TO_SOCKET_OR_NULL, and can be used as a bogus socket pointer, leading to stack-out-of-bounds access in helpers like bpf_skc_to_tcp6_sock(). - SOCK_OPS_GET_FIELD: dst_reg retains the ctx pointer which the verifier believes is a SCALAR_VALUE, leaking a kernel pointer. Fix both macros by: - Changing JMP_A(1) to JMP_A(2) in the fullsock path to skip the added instruction. - Adding BPF_MOV64_IMM(si->dst_reg, 0) after the temp register restore in the !fullsock path, placed after the restore because dst_reg == src_reg means we need src_reg intact to read ctx->temp.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-125 · Out-of-bounds read
- Record status
- Modified
Affected
- Linux Kernel < 5.5
- Linux Kernel < 5.8
- Linux Kernel < 5.9
- Linux Kernel < 7.0.10
- Linux Kernel 5.9
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-53078.md and follow it. Check whether this project is affected by CVE-2026-53078. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/10f86a2a5c91fc4c4d001960f1c21abe52545ef6
- https://git.kernel.org/stable/c/18e3ffde1822f0b48b1753bf34aa97ce839df1d8
References
- https://git.kernel.org/stable/c/0e6b30657bbc771f38025c828d722b6162428508
- https://git.kernel.org/stable/c/10f86a2a5c91fc4c4d001960f1c21abe52545ef6
- https://git.kernel.org/stable/c/18e3ffde1822f0b48b1753bf34aa97ce839df1d8
- https://git.kernel.org/stable/c/22400725de070b787cd6d806c5795370ab46d269
- https://git.kernel.org/stable/c/2a2c98141e0a75f2d4a7d78b0316c88b3da784ac
- https://git.kernel.org/stable/c/4c1c5efd9d1d74743d41ce4e1600501b4feb6827
- https://git.kernel.org/stable/c/64eaf4ecda007140ddcdb28e00c48c9c69aaba39
- https://git.kernel.org/stable/c/db1200ec2c3ddf119d4d9ba67982063df06bbacb