{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98643 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98643 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98643 and fix it if it is affected.\n\nWhat it is: CVE-2026-98643 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98643 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98643/ (Markdown: https://insights.sbomify.com/CVE-2026-98643/index.md)","id":"CVE-2026-98643","markdown":"https://insights.sbomify.com/CVE-2026-98643/index.md","name":"CVE-2026-98643","record":{"aliases":["AZL-109140","BELL-CVE-2026-98643","DEBIAN-CVE-2026-98643","GHSA-xg7q-jpqp-fc7g","UBUNTU-CVE-2026-98643"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker with BPF privileges can read out-of-bounds kernel memory via sock_ops, potentially leaking sensitive kernel pointers.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix out-of-bounds read of rtt_min in sock_ops\n\nA sockops prog reading skops-\u003ertt_min never checks the sk type: on the\ntcp_conn_request() path sock_ops-\u003esk is a request_sock (non-full), and the\nctx rewrite casts it to a tcp_sock (full) and reads rtt_min past the end of\nthe request_sock, returning dirty adjacent memory.\n\n\tSEC(\"sockops\")\n\tint prog(struct bpf_sock_ops *skops)\n\t{\n\t\tswitch (skops-\u003eop) {\n\t\tcase BPF_SOCK_OPS_RWND_INIT:\n\t\t\tleak = skops-\u003ertt_min;   /* reads the request_sock OOB */\n\t\t...\n\t\t}\n\t}\n\nFor instance one such read returned rtt_min=0xffff8881, the high half of a\nleaked kernel pointer.\n\nGuarding that cast is exactly what SOCK_OPS_GET_FIELD() does -- it checks\nis_locked_tcp_sock and returns 0 when sock_ops-\u003esk is not a locked full\nsocket. Every other tcp_sock field in sock_ops goes through it; rtt_min is\nthe only one open-coded, so it skips the check.\n\nRead rtt_min through SOCK_OPS_GET_FIELD() too. rtt_min is a bit special:\nit is a struct minmax and we only want the current min, so pass\nrtt_min.s[0].v. That is equivalent to the old hand-computed offset\n\n\toffsetof(struct tcp_sock, rtt_min) + sizeof_field(struct minmax_sample, t)\n\n(s[0] sits at rtt_min + 0 and .v at + sizeof(.t), i.e. what minmax_get()\nreturns), so the loaded field is unchanged and only the full-sock guard is\nadded. The two BUILD_BUG_ON()s that protected the hand-computed offset\nare no longer needed.\n\nBefore patch:\n\n\t0: r1 = *(u64 *)(r1 +0)      ; r1 = skops-\u003esk\n\t1: r1 = *(u32 *)(r1 +2324)   ; ((tcp_sock *)sk)-\u003ertt_min.s[0].v\n\nAfter patch:\n\n\t0: *(u64 *)(r1 +56) = r9\n\t1: r9 = *(u8 *)(r1 +50)      ; is_locked_tcp_sock\n\t2: if r9 == 0 goto pc+4      ; not a locked full sock -\u003e 0\n\t3: r9 = *(u64 *)(r1 +56)\n\t4: r1 = *(u64 *)(r1 +0)      ; r1 = skops-\u003esk\n\t5: r1 = *(u32 *)(r1 +2324)   ; rtt_min.s[0].v\n\t6: goto pc+2\n\t7: r9 = *(u64 *)(r1 +56)\n\t8: r1 = 0","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"bpf: Fix out-of-bounds read of rtt_min in sock_ops","id":"CVE-2026-98643","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"bpf: Avoid soft lockup in __htab_map_lookup_and_delete_batch()","id":"CVE-2026-98644"},"packages":[],"prev":{"headline":"bpf: Fix UAF due to concurrent consumption of ttrace lists in alloc_bulk","id":"CVE-2026-98642"},"products":["Linux"],"published":"2026-10-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker with BPF privileges can read out-of-bounds kernel memory via sock_ops, potentially leaking sensitive kernel pointers.","url":"https://insights.sbomify.com/CVE-2026-98643/"}