Skip to main content
VulnerabilityPublished

CVE-2026-98643: Linux kernel · bpf: Fix out-of-bounds read of rtt_min in sock_ops

Source GCVE Database

0
Authoritative record:CVE-2026-98643· High

Not known to be exploited · fixed in fd6bf2721933d8c90bc4ce57f3e204c9295e7e3f : patch Linux kernel soon.

Data as of 26 Oct 2026, 17:16 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in fd6bf2721933d8c90bc4ce57f3e204c9295e7e3f, fc9d0e6e9d86fbefe7b8fe6ee49f4cf102add79d, cba54d142c43ec96d8c4d566f66439e8c0afded7 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 44f0e43037d3a17b043843ba67610ac7c7e37db6, < fd6bf2721933d8c90bc4ce57f3e204c9295e7e3f
Fixed in
  • fd6bf2721933d8c90bc4ce57f3e204c9295e7e3f
LinuxLinuxAffected
  • ≥ 44f0e43037d3a17b043843ba67610ac7c7e37db6, < fc9d0e6e9d86fbefe7b8fe6ee49f4cf102add79d
Fixed in
  • fc9d0e6e9d86fbefe7b8fe6ee49f4cf102add79d
LinuxLinuxAffected
  • ≥ 44f0e43037d3a17b043843ba67610ac7c7e37db6, < cba54d142c43ec96d8c4d566f66439e8c0afded7
Fixed in
  • cba54d142c43ec96d8c4d566f66439e8c0afded7
LinuxLinuxAffected
  • ≥ 44f0e43037d3a17b043843ba67610ac7c7e37db6, < a8a9becbac93a9f54f4d565f1f3005eb08a7912f
Fixed in
  • a8a9becbac93a9f54f4d565f1f3005eb08a7912f
LinuxLinuxAffected
  • ≥ 44f0e43037d3a17b043843ba67610ac7c7e37db6, < 6785313d4fac96afb21ef193610c1fa88b1a9e64
Fixed in
  • 6785313d4fac96afb21ef193610c1fa88b1a9e64
LinuxLinuxAffected
  • ≥ 44f0e43037d3a17b043843ba67610ac7c7e37db6, < 75f8cf22463d82bb1fb0239a3d485fc8f4c8ef03
Fixed in
  • 75f8cf22463d82bb1fb0239a3d485fc8f4c8ef03

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available that adds proper type checking before reading the rtt_min field in sock_ops programs. Users should apply the official Linux kernel patch that replaces the direct read with a guarded read via SOCK_OPS_GET_FIELD(). No additional mitigation is required beyond applying this patch.

Description

A vulnerability in the Linux kernel's BPF sock_ops program allowed an out-of-bounds read of the rtt_min field due to improper type checking. This flaw caused the program to read beyond the end of a request_sock structure by casting it incorrectly to a tcp_sock, potentially leaking kernel memory. The issue was fixed by adding proper checks to ensure the socket is a full tcp_sock before reading rtt_min.

References

Community reviews

Loading reviews…