Read the docs
TI-2026-38165 Aliases CVE-2026-53078GHSA-pwr6-cvf5-35f3

bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops

Priority LOW 35CWE-125Published · Updated

Key facts

Attack vector
Local
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
High · High · High
Fix status
Partial Red Hat: 4 without a fix

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat.

Summary

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00121 1st percentileScored 2026-11-07
Fix Partial Linux (Linux): 5.8, 5.9, 5.5 +8Red Hat: 4 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
LinuxLinux5.7.18 to before 5.8; 5.8.4 to before 5.9; 5.4.61 to before 5.55.8, 5.9, 5.5Patch availableCNA
LinuxLinux5.9 and later5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.101, 6.18.42, 7.0.10, 7.1Patch availableCNA
  • Linux VendorLinux Affected 5.7.18 to before 5.8; 5.8.4 to before 5.9; 5.4.61 to before 5.5 Fixed in 5.8, 5.9, 5.5 Patch available CNA
  • Linux VendorLinux Affected 5.9 and later Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.101, 6.18.42, 7.0.10, 7.1 Patch available CNA

CPE configurations NVD · 9

CPEVersionsRoleVendor
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*5.4.61 to before 5.5; 5.7.18 to before 5.8; 5.8.4 to before 5.9; 5.9.1 to before 7.0.10VulnerableLinux
cpe:2.3:o:linux:linux_kernel:5.9:-:*:*:*:*:*:*5.9VulnerableLinux
cpe:2.3:o:linux:linux_kernel:5.9:rc2:*:*:*:*:*:*5.9 rc2VulnerableLinux
cpe:2.3:o:linux:linux_kernel:5.9:rc3:*:*:*:*:*:*5.9 rc3VulnerableLinux
cpe:2.3:o:linux:linux_kernel:5.9:rc4:*:*:*:*:*:*5.9 rc4VulnerableLinux
cpe:2.3:o:linux:linux_kernel:5.9:rc5:*:*:*:*:*:*5.9 rc5VulnerableLinux
cpe:2.3:o:linux:linux_kernel:5.9:rc6:*:*:*:*:*:*5.9 rc6VulnerableLinux
cpe:2.3:o:linux:linux_kernel:5.9:rc7:*:*:*:*:*:*5.9 rc7VulnerableLinux
cpe:2.3:o:linux:linux_kernel:5.9:rc8:*:*:*:*:*:*5.9 rc8VulnerableLinux
  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* Versions 5.4.61 to before 5.5; 5.7.18 to before 5.8; 5.8.4 to before 5.9; 5.9.1 to before 7.0.10 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:5.9:-:*:*:*:*:*:* Versions 5.9 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:5.9:rc2:*:*:*:*:*:* Versions 5.9 rc2 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:5.9:rc3:*:*:*:*:*:* Versions 5.9 rc3 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:5.9:rc4:*:*:*:*:*:* Versions 5.9 rc4 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:5.9:rc5:*:*:*:*:*:* Versions 5.9 rc5 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:5.9:rc6:*:*:*:*:*:* Versions 5.9 rc6 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:5.9:rc7:*:*:*:*:*:* Versions 5.9 rc7 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:5.9:rc8:*:*:*:*:*:* Versions 5.9 rc8 Vulnerable ·Linux

Remediation

  • Fix · CNA Linux (Linux) Fixed in 5.8, 5.9, 5.5
  • Fix · CNA Linux (Linux) Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.101, 6.18.42, 7.0.10, 7.1

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Enterprise Linux 10AffectedNo fix yet
Red Hat Enterprise Linux 6AffectedNo fix planned: Out of support scope
Red Hat Enterprise Linux 8AffectedNo fix yet
Red Hat Enterprise Linux 9AffectedNo fix yet
Not affected: 1 product
  • Red Hat Enterprise Linux 7

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-53078
  2. 2026-10-03 Alias added: GHSA-pwr6-cvf5-35f3
  3. 2026-10-16 CISA SSVC decision points changed
  4. 2026-10-19 Weakness changed · CISA ADP
  5. 2026-11-06 CVSS score changed · Red Hat

References

Patch 2

Other 6

  • TI-2025-26358 tls: fix handling of zero-length records on the rx_list KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-38352 netfilter: bridge: make ebt_snat ARP rewrite writable KEVCVSS 3.1HIGH 8.8
  • TI-2013-05264 The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the… KEVCVSS 3.1HIGH 8.8
  • TI-2022-00125 Integer overflow in kernel KEVCVSS 3.1HIGH 8.4
  • TI-2013-01864 The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9… KEVCVSS 3.1HIGH 8.4
  • TI-2021-05514 Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACE KEVCVSS 3.1HIGH 8.3
See all 15278 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences