Review reviewHigh

CVE-2026-53078

Linux Linux, linux kernel

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...

CVSS
7.8
EPSS
0.11%
1.61% percentile
CISA KEV
Not listed
Published
2026.06.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.11%
Technical severityCVSS 7.8

Vulnerability overview

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...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= fd09af010788a884de1c39537c288830c3d305db < 2a2c98141e0a75f2d4a7d78b0316c88b3da784ac, >= fd09af010788a884de1c39537c288830c3d305db < 22400725de070b787cd6d806c5795370ab46d269, >= fd09af010788a884de1c39537c288830c3d305db < 18e3ffde1822f0b48b1753bf34aa97ce839df1d8, >= fd09af010788a884de1c39537c288830c3d305db < 10f86a2a5c91fc4c4d001960f1c21abe52545ef6, >= 48be3df15aa19c04eadf156c9129293c9a10389f, >= cd4644d904e1d153d516e73e2e127e7a2fe687e1, >= 6e0bc946cbeec538322820786b5fb5200a2216ab, >= a7e52f7f675046d9ffc5692d815fa67c82fcdbf5, >= db7f8c57dbdd31f7e59f8dc8d1e1b38607a320ef, >= 5.7.18 < 5.8, >= 5.8.4 < 5.9, >= 5.4.61 < 5.5, >= 5.9, >= 5.9.1 < 7.0.10, 5.9
Fixed versions
5.5, 5.8, 5.9, 7.0.10

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-125