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-90327phonet: pep: do not write beyond optlen in getsockopt

Description

In the Linux kernel, the following vulnerability has been resolved: phonet: pep: do not write beyond optlen in getsockopt pep_getsockopt() clamps the reported length to the caller's buffer with min_t(), but then stores the value with put_user(val, (int __user *) optval), which always writes sizeof(int) bytes. A getsockopt() call with an optlen smaller than sizeof(int) thus reports the clamped length yet writes a full int, one to three bytes past the user buffer. Write the value with copy_to_user() bounded by len, so at most optlen bytes are copied, matching the length reported back to userspace.

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 (13 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 02a47617cdce440f60c71a51f3a93f9f5fcc5a7a – < 6054fed6bad08b6d03973e8ffca7f0c9394d1c30
    • affected 02a47617cdce440f60c71a51f3a93f9f5fcc5a7a – < eac733a0b6fe0a52d91f9f623425735ed50ac6c2
    • affected 02a47617cdce440f60c71a51f3a93f9f5fcc5a7a – < 95e0ed2439dd1792eb454c68ae8d10f30ffe3bff
    • affected 02a47617cdce440f60c71a51f3a93f9f5fcc5a7a – < 056eea1a2068ad2fb7c3093c5f1095268f87d0c7
    • affected 02a47617cdce440f60c71a51f3a93f9f5fcc5a7a – < 1bf499e438da80455e258049bce60ffb3a53f3fa
    • affected 02a47617cdce440f60c71a51f3a93f9f5fcc5a7a – < c4487e4d5309de587479ecc2f5173b49586f46f4
    • affected 02a47617cdce440f60c71a51f3a93f9f5fcc5a7a – < f97022fefe6eb06ee18549d603420440f2959802
    • affected 02a47617cdce440f60c71a51f3a93f9f5fcc5a7a – < 77e5eb0e192aec6710c03ca8144582fd2af36ca4
  • Linux · Linux

    • affected 2.6.28
    • unaffected < 2.6.28
    • 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-90327 badge
[![CVE-2026-90327](https://cveledger.app/badge/CVE-2026-90327.svg)](https://cveledger.app/cve/CVE-2026-90327)

Record last updated .