CVE-2026-90327 — phonet: pep: do not write beyond optlen in getsockopt
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 02a47617cdce440f60c71a51f3a93f9f5fcc5a7a and < 6054fed6bad08b6d03973e8ffca7f0c9394d1c30≥ 02a47617cdce440f60c71a51f3a93f9f5fcc5a7a and < eac733a0b6fe0a52d91f9f623425735ed50ac6c2≥ 02a47617cdce440f60c71a51f3a93f9f5fcc5a7a and < 95e0ed2439dd1792eb454c68ae8d10f30ffe3bff≥ 02a47617cdce440f60c71a51f3a93f9f5fcc5a7a and < 056eea1a2068ad2fb7c3093c5f1095268f87d0c7≥ 02a47617cdce440f60c71a51f3a93f9f5fcc5a7a and < 1bf499e438da80455e258049bce60ffb3a53f3fa≥ 02a47617cdce440f60c71a51f3a93f9f5fcc5a7a and < c4487e4d5309de587479ecc2f5173b49586f46f4≥ 02a47617cdce440f60c71a51f3a93f9f5fcc5a7a and < f97022fefe6eb06ee18549d603420440f2959802≥ 02a47617cdce440f60c71a51f3a93f9f5fcc5a7a and < 77e5eb0e192aec6710c03ca8144582fd2af36ca4 and 1 moreversion 2.6.28 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 18, 2026 · 3 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/eac733a0b6fe0a52d91f9f623425735ed50ac6c2
- git.kernel.org/stable/c/77e5eb0e192aec6710c03ca8144582fd2af36ca4
- git.kernel.org/stable/c/6054fed6bad08b6d03973e8ffca7f0c9394d1c30
- git.kernel.org/stable/c/f97022fefe6eb06ee18549d603420440f2959802
- git.kernel.org/stable/c/c4487e4d5309de587479ecc2f5173b49586f46f4
- git.kernel.org/stable/c/056eea1a2068ad2fb7c3093c5f1095268f87d0c7
- git.kernel.org/stable/c/95e0ed2439dd1792eb454c68ae8d10f30ffe3bff
- git.kernel.org/stable/c/1bf499e438da80455e258049bce60ffb3a53f3fa
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 15h
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 15h
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 15h
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 15h
- Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 15h
- Unknown CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 15h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-90327 is "phonet: pep: do not write beyond optlen in getsockopt", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.