Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-90157

bpf: Reject negative optlen in cgroup getsockopt hook

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Reject negative optlen in cgroup getsockopt hook A cgroup getsockopt BPF program can shrink ctx->optlen after the kernel getsockopt handler has run. The kernel-buffer variant, used by TCP_ZEROCOPY_RECEIVE, only rejects values larger than the original length. If BPF writes a negative optlen, that value is accepted and propagated back to the TCP getsockopt code. It can then be passed to copy_to_sockptr() as a size_t and trigger the hardened usercopy bytes > INT_MAX warning. Reject negative ctx.optlen in __cgroup_bpf_run_filter_getsockopt_kern(), matching the lower-bound validation already present in the sockptr-based getsockopt hook.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 08f61a34913558e06576e7b6318bf583f273c1be – < 5b09d984b38b018b123c3a9e02a96bbc6468dbe5
    • affected 9cacf81f8161111db25f98e78a7a0e32ae142b3f – < 554ba7195c4108726450e24480c8449990c2268c
    • affected 9cacf81f8161111db25f98e78a7a0e32ae142b3f – < d02a12b4085ffe41ea750b1007f7a9c7aee2875a
    • affected 9cacf81f8161111db25f98e78a7a0e32ae142b3f – < e6fbf0eba87f50084d67508898f6ad6fc7ff1ba2
    • affected 9cacf81f8161111db25f98e78a7a0e32ae142b3f – < f68671b1a98d426c57864bd457c125fee14ac1a5
    • affected 9cacf81f8161111db25f98e78a7a0e32ae142b3f – < 2bdbe00454200fcb0110f31eeca8d906a3515e74
    • affected 9cacf81f8161111db25f98e78a7a0e32ae142b3f – < 31a89af4f513d750fec196e2bb6195a7d4473e9f
    • affected 9cacf81f8161111db25f98e78a7a0e32ae142b3f – < 1b5aacd5b2419b0790e955e466d389a61c79b4b1
    • affected 5.10.188 – < 5.10.270
  • Linux · Linux

    • affected 5.12
    • unaffected < 5.12
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90157 badge
[![CVE-2026-90157](https://cveledger.app/badge/CVE-2026-90157.svg)](https://cveledger.app/cve/CVE-2026-90157)

Record last updated .